File: README.versions

package info (click to toggle)
ntp 1%3A4.2.8p15%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 32,776 kB
  • sloc: ansic: 242,968; sh: 6,859; makefile: 3,419; perl: 2,765; yacc: 1,524; python: 1,486; ruby: 817; awk: 417; sed: 47; asm: 37
file content (27 lines) | stat: -rw-r--r-- 817 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

NTP uses A.B.C - style release numbers.

At the moment:

 A is 4, for ntp V4.
 B is the major release number.
 C is the minor release number.  Even numbers are 'stable' releases and
 odd numbers are "development" releases.

Following the release number may be the letter 'p' followed by a number.
This indicates a point (or patch) release.

Release candidates have -RC in the release number.

Here are some recent versions numbers as an example:

 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.

Feel free to suggest improvements...