Set up release notes for BIND 9.16.20

diff --git a/doc/arm/notes.rst b/doc/arm/notes.rst
index d590458b0c5990a06f929511aec545e1a93865ea..2fe3b4ec5a7c9e455c78da345ccddaff951925f4 100644 (file)
--- a/doc/arm/notes.rst
+++ b/doc/arm/notes.rst
@@ -59,6 +59,7 @@ https://www.isc.org/download/. There you will find additional
 information about each release, source code, and pre-compiled versions
 for Microsoft Windows operating systems.
 
+.. include:: ../notes/notes-current.rst
 .. include:: ../notes/notes-9.16.19.rst
 .. include:: ../notes/notes-9.16.18.rst
 .. include:: ../notes/notes-9.16.17.rst

diff --git a/doc/notes/notes-9.16.19.rst b/doc/notes/notes-9.16.19.rst
index 135d556c5b86ec958d163fe2aae5cc635cba3e56..bfcd74bd5a6baffcf185a7a7e33a663fb6c17c16 100644 (file)
--- a/doc/notes/notes-9.16.19.rst
+++ b/doc/notes/notes-9.16.19.rst
@@ -11,15 +11,6 @@
 Notes for BIND 9.16.19
 ----------------------
 
-Security Fixes
-~~~~~~~~~~~~~~
-
-- Named failed to check the opcode of responses when performing refresh,
-  stub updates, and UPDATE forwarding.  This could lead to an assertion
-  failure under particular conditions.  This has been addressed by checking
-  the opcode of those responses and rejecting the messages if they don't
-  match the expected value. :gl:`#2762`
-
 New Features
 ~~~~~~~~~~~~
 
@@ -37,12 +28,6 @@ Feature Changes
   (TrunCated) bit set, which forces DNS clients to fall back to TCP.
   :gl:`#2790`
 
-- CDS and CDNSKEY records may now be published in a zone without the
-  requirement that they exactly match an existing DNSKEY record, so long
-  the zone is signed with an algorithm represented in the CDS or CDNSKEY
-  record.  This allows a clean rollover from one DNS provider to another
-  when using a multiple-signer DNSSEC configuration. :gl:`#2710`
-
 Bug Fixes
 ~~~~~~~~~
 
@@ -73,12 +58,3 @@ Bug Fixes
 - A race condition could occur where two threads were competing for the
   same set of key file locks, leading to a deadlock. This has been
   fixed. :gl:`#2786`
-
-- Testing revealed that setting the thread affinity on both the netmgr
-  and netthread threads led to inconsistent recursive performance, as
-  sometimes the netmgr and netthread threads competed over a single
-  resource.
-
-  When the affinity is not set, tests show a slight dip in the authoritative
-  performance of around 5% (ranging from 3.8% to 7.8%), but
-  the recursive performance is now consistently improved. :gl:`#2822`

diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst
new file mode 100644 (file)
index 0000000..7544bff
--- /dev/null
+++ b/doc/notes/notes-current.rst
@@ -0,0 +1,57 @@
+.. 
+   Copyright (C) Internet Systems Consortium, Inc. ("ISC")
+   
+   This Source Code Form is subject to the terms of the Mozilla Public
+   License, v. 2.0. If a copy of the MPL was not distributed with this
+   file, you can obtain one at https://mozilla.org/MPL/2.0/.
+   
+   See the COPYRIGHT file distributed with this work for additional
+   information regarding copyright ownership.
+
+Notes for BIND 9.16.20
+----------------------
+
+Security Fixes
+~~~~~~~~~~~~~~
+
+- Named failed to check the opcode of responses when performing refresh,
+  stub updates, and UPDATE forwarding.  This could lead to an assertion
+  failure under particular conditions.  This has been addressed by checking
+  the opcode of those responses and rejecting the messages if they don't
+  match the expected value. :gl:`#2762`
+
+Known Issues
+~~~~~~~~~~~~
+
+- None.
+
+New Features
+~~~~~~~~~~~~
+
+- None.
+
+Removed Features
+~~~~~~~~~~~~~~~~
+
+- None.
+
+Feature Changes
+~~~~~~~~~~~~~~~
+
+- CDS and CDNSKEY records may now be published in a zone without the
+  requirement that they exactly match an existing DNSKEY record, so long
+  the zone is signed with an algorithm represented in the CDS or CDNSKEY
+  record.  This allows a clean rollover from one DNS provider to another
+  when using a multiple-signer DNSSEC configuration. :gl:`#2710`
+
+Bug Fixes
+~~~~~~~~~
+
+- Testing revealed that setting the thread affinity on both the netmgr
+  and netthread threads led to inconsistent recursive performance, as
+  sometimes the netmgr and netthread threads competed over a single
+  resource.
+
+  When the affinity is not set, tests show a slight dip in the authoritative
+  performance of around 5% (ranging from 3.8% to 7.8%), but
+  the recursive performance is now consistently improved. :gl:`#2822`