summaryrefslogtreecommitdiff
path: root/README.versions
diff options
context:
space:
mode:
authorLorry Tar Creator <lorry-tar-importer@baserock.org>2014-12-02 09:01:21 +0000
committer <>2014-12-04 16:11:25 +0000
commitbdab5265fcbf3f472545073a23f8999749a9f2b9 (patch)
treec6018dd03dea906f8f1fb5f105f05b71a7dc250a /README.versions
downloadntp-bdab5265fcbf3f472545073a23f8999749a9f2b9.tar.gz
Imported from /home/lorry/working-area/delta_ntp/ntp-dev-4.2.7p482.tar.gz.ntp-dev-4.2.7p482
Diffstat (limited to 'README.versions')
-rw-r--r--README.versions27
1 files changed, 27 insertions, 0 deletions
diff --git a/README.versions b/README.versions
new file mode 100644
index 0000000..018d59d
--- /dev/null
+++ b/README.versions
@@ -0,0 +1,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...
+