2
NTP uses A.B.C - style release numbers.
4
The third (C) part of the version number can be:
6
0-69 for patches/bugfixes to the A.B.C series.
7
70-79 for alpha releases of the A.B+1.0 series.
8
80+ for beta releases of the A.B+1.0 series.
13
B is the minor release number.
14
C is the patch/bugfix number, and may have extra cruft in it.
16
Any extra cruft in the C portion of the number indicates an "interim" release.
18
Interim releases almost always have a C portion consisting of a number
19
followed by an increasing letter, optionally followed by -rcX, where X
20
is an increasing number. The -rcX indicates a "release candidate".
22
Here are some recent versions numbers as an example:
24
4.1.0 A production release (from the ntp-stable repository)
25
4.1.0b-rc1 A release candidate for 4.1.1 (from the ntp-stable repo)
26
4.1.71 An alpha release of 4.2.0, from the ntp-dev repo
28
Note that after the ntp-dev repo produces a production release it will
29
be copied into the ntp-stable and the cycle will repeat.
31
The goal of this scheme is to produce version numbers that collate
32
"properly" with the output of the "ls" command.
34
Feel free to suggest improvements...
added
removed
README.versions
