1 2NTP uses A.B.C - style release numbers. 3 4The third (C) part of the version number can be: 5 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. 9 10At the moment: 11 12 A is 4, for ntp V4. 13 B is the minor release number. 14 C is the patch/bugfix number, and may have extra cruft in it. 15 16Any extra cruft in the C portion of the number indicates an "interim" release. 17 18Interim releases almost always have a C portion consisting of a number 19followed by an increasing letter, optionally followed by -rcX, where X 20is an increasing number. The -rcX indicates a "release candidate". 21 22Here are some recent versions numbers as an example: 23 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 27 28Note that after the ntp-dev repo produces a production release it will 29be copied into the ntp-stable and the cycle will repeat. 30 31The goal of this scheme is to produce version numbers that collate 32"properly" with the output of the "ls" command. 33 34Feel free to suggest improvements... 35 36