Recent Changes - Search:

Learn More

Support

Contribute

Development Status

Languages:   English   Japanese   Magyar   Español   Francaise   Deutsch   Русский

Web /

Versioning system

Web.VersioningSystem History

Hide minor edits - Show changes to output

Changed line 39 from:
After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code - "trunk" (or "master") and "branch". The "trunk" is the main development branch, this is where new major features are introduced. This branch usually becomes the next major release (e.g. LyX 2.1 after LyX 2.0). The "branch" (e.g. "2.0.x" for LyX 2.0) is the stable development branch where bugs are fixed. Maintenance releases like LyX 2.0.1, LyX 2.0.2 and so on will be built out of this branch. The intention is that this branch will always be stable.
to:
After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code - "master" and "branch". The "master" is the main development branch, this is where new major features are introduced. This branch usually becomes the next major release (e.g. LyX 2.1 after LyX 2.0). The "branch" (e.g. "2.0.x" for LyX 2.0) is the stable development branch where bugs are fixed. Maintenance releases like LyX 2.0.1, LyX 2.0.2 and so on will be built out of this branch. The intention is that this branch will always be stable.
Changed line 60 from:
A standard user, or one using LyX for an important business project, say, would download 1.5.2, and update it later to 1.5.3 if this is released. An experienced user might download the latest 1.6.0rc1 version, to get a new neat feature. A developer would continue development through Subversion.
to:
A standard user, or one using LyX for an important business project, say, would download 1.5.2, and update it later to 1.5.3 if this is released. An experienced user might download the latest 1.6.0rc1 version, to get a new neat feature. A developer would continue development through Git.
Changed lines 55-56 from:
Pre-releases are made available in the [[ftp://ftp.devel.lyx.org/pub/lyx/devel/ | "devel"]] directory of the FTP site.[[<<]]
And for the curious, there is always the [[HowToUseSVN | Subversion repository]]!
to:
Pre-releases are made available in the [[ftp://ftp.lyx.org/pub/lyx/devel/ | "devel"]] directory of the FTP site.[[<<]]
And for the curious, there is always the [[HowToUseGIT | Git repository]]!
Changed lines 37-43 from:
!!! SVN builds

After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code - "trunk" and "branch". The "trunk" is the main development branch, this is where new major features are introduced. This branch usually becomes the next major release (e.g. LyX 1.6 after LyX 1.5). The "branch" (e.g. BRANCH_1_6_X for LyX 1.6) is the stable development branch where bugs are fixed. Maintenance releases like LyX 1.6.1, LyX 1.6.2 and so on will be built out of this branch. The intention is that this branch will always be stable.

Versions of LyX build from the Subversion (SVN) repository have the suffix 'svn' (e.g. 1.6.0svn or 1.5.1svn). These versions are never packaged on LyX's FTP site.

Instructions how to use SVN can be found [[HowToUseSVN | here]].
to:
!!! Git builds

After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code - "trunk" (or "master") and "branch". The "trunk" is the main development branch, this is where new major features are introduced. This branch usually becomes the next major release (e.g. LyX 2.1 after LyX 2.0). The "branch" (e.g. "2.0.x" for LyX 2.0) is the stable development branch where bugs are fixed. Maintenance releases like LyX 2.0.1, LyX 2.0.2 and so on will be built out of this branch. The intention is that this branch will always be stable.

Versions of LyX build from the Git repository have the suffix 'svn' (e.g. 1.6.0svn or 1.5.1svn). These versions are never packaged on LyX's FTP site.

Instructions how to use GIT can be found [[HowToUseGIT | here]].
Changed line 27 from:
An alpha release (e.g. lyx-1.5.0alpha1.tar.bz2) is a release of the LyX software from the development source code at a point when only a few new features were added without being fully tested. Alpha versions are therefore often unstable and should only be used by testers and developers.
to:
An alpha release (e.g. lyx-1.5.0alpha1.tar.bz2) is a release of the LyX software from the development source code at a point when only a few new features were added without being fully tested. Alpha versions are therefore often unstable and should only be used by testers and developers. Announcements are released to limited audience only.
Changed lines 16-17 from:
The LyX file format is never changed by a maintenance release.
to:
The LyX file format is never changed by a maintenance release, so for example, a LyX file created by LyX 1.5.3 will always be readable by LyX 1.5.1 and vice versa.
Changed line 40 from:
After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code. The "trunk" is the main development branch, this is where new major features are introduced. This branch usually becomes the next major release (e.g. LyX 1.6 after LyX 1.5). The "branch" (e.g. BRANCH_1_6_X for LyX 1.6) is the stable development branch where bugs are fixed. Maintenance releases like LyX 1.6.1, LyX 1.6.2 and so on will be built out of this branch. The intention is that this branch will always be stable.
to:
After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code - "trunk" and "branch". The "trunk" is the main development branch, this is where new major features are introduced. This branch usually becomes the next major release (e.g. LyX 1.6 after LyX 1.5). The "branch" (e.g. BRANCH_1_6_X for LyX 1.6) is the stable development branch where bugs are fixed. Maintenance releases like LyX 1.6.1, LyX 1.6.2 and so on will be built out of this branch. The intention is that this branch will always be stable.
May 28, 2009, at 09:32 PM by Uwe Stöhr -
Changed line 42 from:
Versions of LyX build from the Subversion (SVN) repository will have the 'svn' suffix (e.g. 1.7.0svn or 1.6.1svn). These versions are never packaged on the ftp site.
to:
Versions of LyX build from the Subversion (SVN) repository have the suffix 'svn' (e.g. 1.6.0svn or 1.5.1svn). These versions are never packaged on LyX's FTP site.
May 28, 2009, at 09:29 PM by Uwe Stöhr -
Changed lines 42-45 from:
Versions of LyX build from the Subversion repository will have the `svn' suffix (e.g. 1.7.0svn or 1.6.1svn). These versions are never packaged on the ftp site.

Instructions for SVN builds can be found [[HowToUseSVN | here]]
to:
Versions of LyX build from the Subversion (SVN) repository will have the 'svn' suffix (e.g. 1.7.0svn or 1.6.1svn). These versions are never packaged on the ftp site.

Instructions how to use SVN can be found [[HowToUseSVN | here]].
May 28, 2009, at 09:28 PM by Uwe Stöhr -
Changed line 40 from:
After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code. The "trunk" is the main development branch, this is where new major features are introduced. This branch eventually becomes the next major release (e.g. LyX 1.6 after LyX 1.5). For each major release, the source code is forked off into a separate stable branch (BRANCH_1_6_X for LyX 1.6) where bug fixes are implemented. This branch eventually results in minor releases such as LyX 1.6.1, LyX 1.6.2 and so on. The intention is that this branch will always be stable.
to:
After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code. The "trunk" is the main development branch, this is where new major features are introduced. This branch usually becomes the next major release (e.g. LyX 1.6 after LyX 1.5). The "branch" (e.g. BRANCH_1_6_X for LyX 1.6) is the stable development branch where bugs are fixed. Maintenance releases like LyX 1.6.1, LyX 1.6.2 and so on will be built out of this branch. The intention is that this branch will always be stable.
May 28, 2009, at 09:13 PM by Uwe Stöhr -
Changed lines 26-27 from:
!!!! Alpha release
to:
!!!! Alpha releases
Changed lines 30-36 from:
!!!! Beta release

A beta release (e.g. lyx-1.5.0beta1.tar.bz2) is similar to an alpha release, with the difference that only small changes will be made until the stable version. This version therefore contains all major new functions of the next stable release and is used to test them out intensively. Beta versions are not stable enough to edit important documents!

!!!! Release candidate (prerelease)

After
the release candidate (rc) is released (e.g. lyx-1.5.0rc1.tar.bz2), only bug fixes are allowed. The criteria to change from beta to rc is that there are no known data loss bugs.
to:
!!!! Beta releases

A beta release (e.g. lyx-1.5.0beta1.tar.bz2) is similar to an alpha release, with the difference that only small changes will be made until the stable version. This version therefore contains all major new functions of the next stable release and is used to test them out intensively.[[<<]]Beta versions are not stable enough to edit important documents!

!!!! Release candidates

After
the first release candidate (rc) is released (e.g. lyx-1.5.0rc1.tar.bz2), only bugs will be fixed. The criteria to publish the first release candidate is that there are no known data loss bugs.
May 28, 2009, at 09:05 PM by Uwe Stöhr - clarifications
Changed lines 32-33 from:
A beta release (e.g. lyx-1.5.0beta1.tar.bz2) is a release of the LyX software from the development source code at a point when very few (and minor) new features are expected to be added before the first stable release.
to:
A beta release (e.g. lyx-1.5.0beta1.tar.bz2) is similar to an alpha release, with the difference that only small changes will be made until the stable version. This version therefore contains all major new functions of the next stable release and is used to test them out intensively. Beta versions are not stable enough to edit important documents!
Changed lines 36-37 from:
After the release candidate (lyx-1.5.0rc1.tar.bz2) is released only bug fixes are allowed. The criteria to change from beta to rc is the inexistence
of data loss
bugs.
to:
After the release candidate (rc) is released (e.g. lyx-1.5.0rc1.tar.bz2), only bug fixes are allowed. The criteria to change from beta to rc is that there are no known data loss bugs.
May 28, 2009, at 08:28 PM by Uwe Stöhr - corrections
Changed line 28 from:
An alpha release (e.g. lyx-1.5.0alpha1.tar.bz2) is a release of the LyX software from the development source code at a point when only a few, if any, new major features are expected to be added before the first stable release.
to:
An alpha release (e.g. lyx-1.5.0alpha1.tar.bz2) is a release of the LyX software from the development source code at a point when only a few new features were added without being fully tested. Alpha versions are therefore often unstable and should only be used by testers and developers.
May 22, 2009, at 09:29 PM by Uwe Stöhr -
Changed lines 56-59 from:
Stable versions and patches will be found in the [[ftp://ftp.lyx.org/pub/lyx/stable/ | "stable"]] directory of the LyX FTP site.

Pre-releases are made available in the [[ftp://ftp.devel.lyx.org/pub/lyx/devel/ | "devel"]] directory of the FTP site.
to:
Stable versions and patches will be found in the [[ftp://ftp.lyx.org/pub/lyx/stable/ | "stable"]] directory of the LyX FTP site.[[<<]]
Pre-releases are made available in the [[ftp://ftp.devel.lyx.org/pub/lyx/devel/ | "devel"]] directory of the FTP site.[[<<]]
May 22, 2009, at 09:27 PM by Uwe Stöhr -
Changed line 58 from:
Pre-releases are made available in the [[ftp://ftp.devel.lyx.org/pub/lyx/devel/ | "devel"]] directory of the ftp site.
to:
Pre-releases are made available in the [[ftp://ftp.devel.lyx.org/pub/lyx/devel/ | "devel"]] directory of the FTP site.
May 22, 2009, at 09:25 PM by Uwe Stöhr - typo
Changed line 56 from:
Stable versions and patches will be found in the [[ftp://ftp.lyx.org/pub/lyx/stable/ | "stable"]] directory of LyX ftp site.
to:
Stable versions and patches will be found in the [[ftp://ftp.lyx.org/pub/lyx/stable/ | "stable"]] directory of the LyX FTP site.
May 16, 2009, at 04:21 AM by Uwe Stöhr -
Changed line 4 from:
(:page_type:web:)(:description: To be added.. :)
to:
(:page_type:web:)(:description: LyX's versioning system :)
May 16, 2009, at 04:21 AM by Uwe Stöhr - fix format
Changed line 12 from:
Version numbers increment numerically. Version 1.x.0 is usually the result of at least one year of development and can be expected to have both exciting new features and bugs. Versions 1.x.y with y>0 are maintenance releases, in which we try to fix bugs and avoid new functionality, although some new things always slip through the cracks.
to:
Version numbers increment numerically. Version 1.x.0 is usually the result of at least one year of development and can be expected to have both exciting new features and bugs. Versions 1.x.y with y&nbsp;>&nbsp;0 are maintenance releases, in which we try to fix bugs and avoid new functionality, although some new things always slip through the cracks.
May 16, 2009, at 04:06 AM by Uwe Stöhr - corrections
Changed line 40 from:
After a major release (e.g. LyX 1.6.0 etc), work typically continues in two separate branches of source code. The "trunk" is the main development branch, this is where new major features are introduced. This branch eventually becomes the next major release (e.g. LyX 1.7 after LyX 1.6). For each major release, the source code is forked off into a separate stable branch (BRANCH_1_6_X for LyX 1.6) where bug fixes are implemented. This branch eventually results in minor releases such as LyX 1.6.1, LyX 1.6.2 and so on. The intention is that this branch will always be stable.
to:
After a major release (e.g. LyX 1.5.0 etc), work typically continues in two separate branches of source code. The "trunk" is the main development branch, this is where new major features are introduced. This branch eventually becomes the next major release (e.g. LyX 1.6 after LyX 1.5). For each major release, the source code is forked off into a separate stable branch (BRANCH_1_6_X for LyX 1.6) where bug fixes are implemented. This branch eventually results in minor releases such as LyX 1.6.1, LyX 1.6.2 and so on. The intention is that this branch will always be stable.
Added line 1:
(:title Versioning system:)
Added lines 5-8:
Description of LyX version numbers and the principles behind them.

Most users want to get the latest stable release of LyX.
Changed lines 39-43 from:
Versions of LyX build from the Subversion repository will have the `svn' suffix (e.g. 1.5.0svn or 1.4.1svn). These versions are never packaged on the ftp site.
to:
After a major release (e.g. LyX 1.6.0 etc), work typically continues in two separate branches of source code. The "trunk" is the main development branch, this is where new major features are introduced. This branch eventually becomes the next major release (e.g. LyX 1.7 after LyX 1.6). For each major release, the source code is forked off into a separate stable branch (BRANCH_1_6_X for LyX 1.6) where bug fixes are implemented. This branch eventually results in minor releases such as LyX 1.6.1, LyX 1.6.2 and so on. The intention is that this branch will always be stable.

Versions of LyX build from the Subversion repository will have the `svn' suffix (e.g. 1.7.0svn or 1.6.1svn). These versions are never packaged on the ftp site.

Instructions for SVN builds can be found [[HowToUseSVN | here]]
Changed lines 31-32 from:
After the release candidate (lyx-1.5.0rc1.tar.bz2) is released only bug fixes are allowed.
to:
After the release candidate (lyx-1.5.0rc1.tar.bz2) is released only bug fixes are allowed. The criteria to change from beta to rc is the inexistence
of data loss bugs.
Added lines 2-3:

(:page_type:web:)(:description: To be added.. :)
Deleted lines 0-1:
Version Numbers
Changed lines 1-3 from:
! Version Numbers
to:
Version Numbers

(:toc:)
Changed line 49 from:
And for the curious, there is always the [[http://www.lyx.org/../devel/cvs.php | Subversion repository]]!
to:
And for the curious, there is always the [[HowToUseSVN | Subversion repository]]!
Changed lines 51-53 from:
!!! Huh?

Still not sure? Perhaps an example would help.
to:
!!! Example
Deleted lines 1-2:

!!! Which version of LyX should you download?
March 25, 2008, at 10:58 PM by 140.247.181.69 -
Added lines 1-57:
! Version Numbers

!!! Which version of LyX should you download?

!!! Stable versions

Version numbers increment numerically. Version 1.x.0 is usually the result of at least one year of development and can be expected to have both exciting new features and bugs. Versions 1.x.y with y>0 are maintenance releases, in which we try to fix bugs and avoid new functionality, although some new things always slip through the cracks.

For example, the current stable version could be 1.5.2, and the ones before that were 1.5.1 and 1.5.0. Those versions are all part of the 1.5.x stable series, and it can be expected that upgrading to a version with higher minor version number is safe.

The LyX file format is never changed by a maintenance release.

!!! Patches

Patches are not made available between initial stable releases (e.g. between 1.5.0 and 1.6.0) because they would be too large. There are nevertheless patches available for maintenance releases (which often seem to be large, but the bulk of their content is documentation of interface l10n updates). Those patches should be applied incrementally (one after the other).

!!! Pre-releases

Pre-releases introduce additional functionality over preceding stable releases. Consequently, lyx-1.5.0alpha/beta/rc1 indicates the pre-release of version 1.5.0. However, pre-releases should be considered as test releases of the next release, and treated with suitable caution. There are no pre-releases of maintenance releases, since we try to keep the burden of producing these to a minimum

!!!! Alpha release

An alpha release (e.g. lyx-1.5.0alpha1.tar.bz2) is a release of the LyX software from the development source code at a point when only a few, if any, new major features are expected to be added before the first stable release.

!!!! Beta release

A beta release (e.g. lyx-1.5.0beta1.tar.bz2) is a release of the LyX software from the development source code at a point when very few (and minor) new features are expected to be added before the first stable release.

!!!! Release candidate (prerelease)

After the release candidate (lyx-1.5.0rc1.tar.bz2) is released only bug fixes are allowed.

!!! SVN builds

Versions of LyX build from the Subversion repository will have the `svn' suffix (e.g. 1.5.0svn or 1.4.1svn). These versions are never packaged on the ftp site.

!!! Summing up

So, there are four possible file name formats:

||
||@@lyx-1.5.0.tar.gz@@ ||an initial stable release. ||
||@@lyx-1.5.2.tar.gz@@ ||the second maintenance release to LyX 1.5.0. ||
||@@patch-1.5.2.gz@@ ||the patch to update the source code of LyX 1.5.1 to 1.5.2. ||
||@@lyx-1.6.0alpha/beta/rc1.tar.gz@@ ||a potentially unstable test release of the next release. ||

Stable versions and patches will be found in the [[ftp://ftp.lyx.org/pub/lyx/stable/ | "stable"]] directory of LyX ftp site.

Pre-releases are made available in the [[ftp://ftp.devel.lyx.org/pub/lyx/devel/ | "devel"]] directory of the ftp site.

And for the curious, there is always the [[http://www.lyx.org/../devel/cvs.php | Subversion repository]]!

!!! Huh?

Still not sure? Perhaps an example would help.

A standard user, or one using LyX for an important business project, say, would download 1.5.2, and update it later to 1.5.3 if this is released. An experienced user might download the latest 1.6.0rc1 version, to get a new neat feature. A developer would continue development through Subversion.
Edit - History - Print - Recent Changes - Search
Page last modified on July 31, 2017, at 09:20 PM