- LyX uses a continuous numbering scheme in which odd or
- even numbering is not significant. Instead a number '1.x.y'
- indicates stable release '1.x', fix level 'y'. Prereleases
- are labeled with a "pre" suffix. Thus there are three possible
- file names:
-
- lyx-1.4.0.tar.gz -- stable release
- lyx-1.4.5.tar.gz -- fifth maintenance release of the
- 1.4 stable release
- lyx-1.4.0pre1.tar.gz -- potentially unstable test release
-
- The maintenance releases are designed primarily to fix bugs. The
- goal here is not to have parallel development as for the linux
- kernel (the team is too small to afford that), but rather to
- include all the simple (so that the maintenance burden on us
- 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 cvs, the version string will look like
- one of:
-
- 1.4.1cvs -- this is the stable branch on which maintenance
- release 1.4.1 will eventually be tagged.
- 1.5.0cvs -- this is the main branch on which stable
- release 1.5.0 will eventually be tagged.
+ LyX uses a continuous numbering scheme in which odd or
+ even numbering is not significant. Instead a number '1.x.y'
+ indicates stable release '1.x', fix level 'y'. Prereleases
+ are labeled with a "pre" suffix. Thus there are three possible
+ file names:
+
+ lyx-1.4.0.tar.gz -- stable release
+ lyx-1.4.5.tar.gz -- fifth maintenance release of the
+ 1.4 stable release
+ lyx-1.4.0pre1.tar.gz -- potentially unstable test release
+
+ The maintenance releases are designed primarily to fix bugs. The
+ goal here is not to have parallel development as for the linux
+ kernel (the team is too small to afford that), but rather to
+ include all the simple (so that the maintenance burden on us
+ 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
+ look like one of:
+
+ 1.4.1svn -- this is the stable branch on which maintenance
+ release 1.4.1 will eventually be tagged.
+ 1.5.0svn -- this is the main branch on which stable
+ release 1.5.0 will eventually be tagged.