Changed to using 'rc' instead of 'pre'

git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@18214 a592a061-630c-0410-9148-cb99ea01b6c8
This commit is contained in:
Christian Ridderström 2007-05-06 19:10:15 +00:00
parent 05ba23093e
commit 54d2810b01

41
README
View File

@ -37,25 +37,34 @@ What do I need to run LyX?
How does the LyX version scheme work? How does the LyX version scheme work?
LyX uses a contiguous numbering scheme for versions, where a LyX uses a contiguous numbering scheme for versions, where a
number "1.x.y" indicates a stable release '1.x', fix level 'y'. number "1.x.y" indicates a stable release '1.x', maintenance
Prereleases are denoted with the suffix "pre" and there are release 'y'. In other words, LyX 1.4.0 was the first stable
therefore three possible types of file names: release in the 1.4-series of LyX. At the time of writing, the
latest maintenance release in the 1.4-series was LyX 1.4.4.
lyx-1.5.0.tar.gz -- stable release Please note that maintenance releases are designed primarily to
fix bugs, and that the file format will _never_ change due to a
maintenance release.
In addition to the stable releases and maintenance releases, some
users may want to give a ''release candidate'' a try. This is a
release that should be stable enough for daily work, but yet may
be potentially unstable. If no major bugs are found, the release
candiate is soon released as the first stable release in a a new
series. To summarize, there are three possible types of file names
that are of interest to normal users:
lyx-1.5.0.tar.gz -- stable release, first in the 1.5-series
lyx-1.5.5.tar.gz -- fifth maintenance release of LyX 1.5 lyx-1.5.5.tar.gz -- fifth maintenance release of LyX 1.5
lyx-1.5.0pre1.tar.gz -- potentially unstable test release lyx-1.5.0rc1.tar.gz -- potentially unstable release candidate
The maintenance releases are designed primarily to fix bugs, Note that the goal is not parallel development as for the linux
and the file format will _never_ change due to a maintenance kernel --the team is too small to afford that-- but rather to
release! include all the simple and safe bug fixes. This is so that the
maintenance burden on us is not too high, and so that system
The goal here is not to have parallel development as for the administrators can install new releases without fear. Experience
linux kernel (the team is too small to afford that), but rather shows that these releases will contain a few new features, and
to include all the simple (so that the maintenance burden on us that the bulk of the patches will be documentation updates.
is not too high) and safe (so that system administrators can
install them without fear) bug fixes. Experience shows that
these releases will contain a few new features, and that the
bulk of the patches will be documentation updates.
If you get the source from Subversion, the version string will If you get the source from Subversion, the version string will
look like one of: look like one of: