EditWYSIWYGAttachPrintable
r13 - 2013-08-05 - 05:17:19 - HarlanStennYou are here: NTP >  Main Web > DocumentationIndex > ReleaseNumberingScheme
NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.

ntp-4.2.8p10 was released on 21 March 2017. It addresses 6 medium- and 5 low-severity security issues, 4 informational security topics, 15 bugfixes, and contains other improvements over 4.2.8p9.

Please see the NTP Security Notice for vulnerability and mitigation details.

Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.

Release Numbering Scheme

Related Topics: EmbeddedVersionStringContent, ReleaseNumberingSchemeDiscussion

ntp4-5.0.0 (new)

Once ntp-4.2.8 has been released we will be changing to a new numbering system, one that is much closer to the one used before ntp-4.2.2.

Discussion on the release numbering scheme should be done at ReleaseNumberingSchemeDiscussion.

Initial Releases after 4.2.8:

  • The first development release will be ntp4-4.9.0
  • The first stable release will be ntp4-5.0.0

The first development release tarball will be named something like ntp-dev-4.9.0.tar.gz or ntp4-dev-4.9.0.tar.gz .

The first stable release tarball will be named something like ntp4-5.0.0.tar.gz .

The first development release tarball after ntp4-5.0.0 will be named something like ntp-dev-5.1.0.tar.gz or ntp4-dev-5.1.0.tar.gz.

Syntax

Protocol_Version-Major_Version.Minor_Version.Point_Version[Release_Tags]

Point Version

An increasing number indicates a Point (i.e. incremental) Release.

The -stable release series point releases are used for bug fixes.

The -dev (development) release series point releases are incremental snapshot releases which checkpoint the development process.

Release Tags

[Special][Status]

Special

Tags not described here may be used for internal projects.

Status

For -stable, one of:

  • -beta followed by an increasing number indicates a Beta release
  • -RC followed by an increasing number indicates a Release Candidate

For -dev:

  • -RC indicating a Release Candidate

Stable vs Development Releases

  • Stable releases have an even Minor Release number
  • Development releases have an odd Minor Release number

Examples

ntp4-5.1.142  NTP Protocol 4 v5.1.142 (development snapshot release)
ntp4-5.2.0    NTP Protocol 4 v5.2.0   (stable release, version 5.2 with no patches)
ntp4-5.2.2    NTP Protocol 4 v5.2.2   (stable release, version 5.2 with 2 patches)

ntp-4.2.2 thru ntp-4.2.8 (current)

The following release numbering scheme was implemented with the release of ntp-4.2.2 on June 6, 2006.

Syntax

Protocol_Version.Major_Version.Minor_Version[Release_Tags]

Release Tags

[Point][Special][Release Candidate]

Point

The letter p followed by an increasing number indicates a Point (i.e. incremental) Release.

The -stable release series point releases are used for bug fixes.

The -dev (development) release series point releases are incremental snapshot releases which checkpoint the development process.

Special

Tags not described here may be used for internal projects.

Release Candidate

The string -RC followed by an increasing number indicates a Release Candidate.

Stable vs Development Releases

  • Stable releases have an even Minor Release number
  • Development releases have an odd Minor Release number

Examples

4.2.7p142  NTP Protocol 4 v2.7.142 (developement snapshot release)
4.2.6p3    NTP Protocol 4 v2.6.3   (stable release)
4.2.2      NTP Protocol 4 v2.2     (stable release)

Prior to 06-Jun-2006

Syntax

Protocol_Version.Minor_Version.Release_Tag

Release Tags

The tag is optional an is the patch / bug fix number.

   0-69 for releases on 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.

Additional following this number indicates that this is an interim 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 Tag examples:

   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 repository.
   4.1.71     An alpha release of 4.20 from the ntp-dev repository.

The goal of this scheme is to produce version numbers that collate properly with the output of the ls command.

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r15 < r14 < r13 < r12 < r11 | More topic actions...
Main.ReleaseNumberingScheme moved from Main.NTPreleaseNumberingScheme on 2004-01-22 - 16:45 by SteveKostecke - put it back
 
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback