[Git][NTPsec/ntpsec][master] version 1.1.0

[Mark Atwood]

Mark Atwood pushed to branch master at NTPsec / ntpsec


Commits:
0b2beb1f by Mark Atwood at 2018-03-15T04:11:41Z
version 1.1.0

Signed-off-by: Mark Atwood <mark.atwood at ntpsec.org>

- - - - -


3 changed files:

- NEWS
- VERSION
- devel/hacking.txt


Changes:

=====================================
NEWS
=====================================
--- a/NEWS
+++ b/NEWS
@@ -10,11 +10,19 @@ Much of the traditional function of a news file is now better addressed
 by browsing the comments in the revision history.  This file will focus
 on user-visible changes.
 
-== Repository head ==
+== 2018-03-14: 1.1.0 ==
+
+RIP Stephen William Hawking, CH CBE FRS FRSA. 1942-01-08 - 2018-03-14
+You gave us a Brief History of Time.  We will just count it.
+
+Enough user visible changes have been made that this is the 1.1.0 release
+instead of a 1.0.1.
+
+The code size is now 55KLOC in C, 15KLOC in Python.
 
 Digests longer then 20 bytes will be truncated.
 
-We have merged Classic's fix for CVE-2018-7182.
+We have merged NTP Classic's fix for CVE-2018-7182.
 
 The following NTP Classic CVEs announced in February 2018 do not affect NTPsec:
 
@@ -24,7 +32,10 @@ The following NTP Classic CVEs announced in February 2018 do not affect NTPsec:
 * CVE-2018-7185: Unauthenticated packet can reset authenticated interleaved association
 * CVE-2018-7183: ntpq:decodearr() can write beyond its buffer limit
 
-We have dropped support for Broadcast servers.
+We have dropped support for Broadcast servers.  We had kept it for
+older desktop operating systems listening on the local network
+broadcast domain, a use case that is now no longer in use at sane
+enviroments, and no longer necessary for modern desktop OSs.
 
 It is now possible to unpeer refclocks using a type/unit specification
 rather than a magic IP address.  This was the last obligatory use of


=====================================
VERSION
=====================================
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-1.0.1
+1.1.0


=====================================
devel/hacking.txt
=====================================
--- a/devel/hacking.txt
+++ b/devel/hacking.txt
@@ -389,23 +389,17 @@ Z is the "revision" number.
 Each release will result in an incremented version number, and the
 version number string will be tagged into the git repository.
 
-When the minor number is even, it refers to a "stable" release, and
-when the minor number is odd, it refers to a "development" release.
-New releases on "stable" are generally bugfixes that are backported
-from it's matching "development".
+We have dropped even/odd minor version number stable/development
+release semantics.  Development on NTPsec has been carefully
+incremental with a strong emphasis on stabilty and correctness, such
+that it turned out to be unneeded.
 
-When a new stable release happens, that also results in the creation
-of a new development release.  For example, the currently hypothetical
-future release of "1.14.0" will also cause the release of an identical
-"1.15.0".
-
-The first public release is version 0.9.0, and will drive to 1.0.0.
-When 1.0.0 is released, that will also create an identical 1.1.0.
+The first public release was version 0.9.0.
+The first production and distribution ready release was 1.0.0.
 
 We currently have no formal policies for the criteria for releases,
-for the schedule of releases, and no formal policies for how far back
-bugfixes will be backported into stable releases.  Feel free to
-discuss it with project management.
+for the schedule of releases, and no formal policies for backporting
+bugfixes.  Feel free to discuss it with project management.
 
 Note that this is a different numbering system from NTP Classic. In
 their A.B.C numbers, A was the protocol version, B was the major, and



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/0b2beb1ffbebed5bd6d9ef615aac905df7e2f220

---
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/0b2beb1ffbebed5bd6d9ef615aac905df7e2f220
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20180315/e47f9f68/attachment.html>