diff options
Diffstat (limited to 'README.versions')
| -rw-r--r-- | README.versions | 28 |
1 files changed, 10 insertions, 18 deletions
diff --git a/README.versions b/README.versions index 550925015c25..018d59d69bad 100644 --- a/README.versions +++ b/README.versions @@ -1,35 +1,27 @@ NTP uses A.B.C - style release numbers. -The third (C) part of the version number can be: - - 0-69 for patches/bugfixes to the A.B.C series. - 70-79 for alpha releases of the A.B+1.0 series. - 80+ for beta releases of the A.B+1.0 series. - At the moment: A is 4, for ntp V4. - B is the minor release number. - C is the patch/bugfix number, and may have extra cruft in it. + B is the major release number. + C is the minor release number. Even numbers are 'stable' releases and + odd numbers are "development" releases. -Any extra cruft in the C portion of the number indicates an "interim" release. +Following the release number may be the letter 'p' followed by a number. +This indicates a point (or patch) release. -Interim releases almost always have a C portion consisting of a number -followed by an increasing letter, optionally followed by -rcX, where X -is an increasing number. The -rcX indicates a "release candidate". +Release candidates have -RC in the release number. Here are some recent versions numbers as an example: - 4.1.0 A production release (from the ntp-stable repository) - 4.1.0b-rc1 A release candidate for 4.1.1 (from the ntp-stable repo) - 4.1.71 An alpha release of 4.2.0, from the ntp-dev repo + 4.2.2 A production release (from the ntp-stable repository) + 4.2.2p2 A production release (from the ntp-stable repository) + 4.2.3p12 A development release + 4.2.3p15-rc1 A release candidate for 4.2.4 Note that after the ntp-dev repo produces a production release it will be copied into the ntp-stable and the cycle will repeat. -The goal of this scheme is to produce version numbers that collate -"properly" with the output of the "ls" command. - Feel free to suggest improvements... |