From: Michał Kępień <michal@isc.org>
Date: Wed, 5 Aug 2020 14:02:38 +0000 (+0200)
Subject: Reorder release notes
X-Git-Tag: v9.17.4~5^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8980d219c7e9e1482986ad9e8afb9f40eb223874;p=thirdparty%2Fbind9.git

Reorder release notes
---

diff --git a/doc/notes/notes-9.17.4.rst b/doc/notes/notes-9.17.4.rst
index e57813e7a66..0571babf092 100644
--- a/doc/notes/notes-9.17.4.rst
+++ b/doc/notes/notes-9.17.4.rst
@@ -56,6 +56,9 @@ Security Fixes
 New Features
 ~~~~~~~~~~~~
 
+- A new configuration option ``stale-cache-enable`` has been introduced
+  to enable or disable keeping stale answers in cache. [GL #1712]
+
 - ``rndc`` has been updated to use the new BIND network manager API.
   This change had the side effect of altering the TCP timeout for RNDC
   connections from 60 seconds to the ``tcp-idle-timeout`` value, which
@@ -68,9 +71,6 @@ New Features
 - Statistics channels have also been updated to use the new BIND network
   manager API. [GL #2022]
 
-- A new configuration option ``stale-cache-enable`` has been introduced
-  to enable or disable keeping stale answers in cache. [GL #1712]
-
 Feature Changes
 ~~~~~~~~~~~~~~~
 
@@ -94,20 +94,6 @@ Bug Fixes
   rules that were loaded from RPZ zones which appeared later in the
   ``response-policy`` statement. This has been fixed. [GL #1619]
 
-- Addressed an error in recursive clients stats reporting which could
-  cause underflow, and even negative statistics. There were occasions
-  when an incoming query could trigger a prefetch for some eligible
-  RRset, and if the prefetch code were executed before recursion, no
-  increment in recursive clients stats would take place. Conversely,
-  when processing the answers, if the recursion code were executed
-  before the prefetch, the same counter would be decremented without a
-  matching increment. [GL #1719]
-
-- The introduction of KASP support inadvertently caused the second field
-  of ``sig-validity-interval`` to always be calculated in hours, even in
-  cases when it should have been calculated in days. This has been
-  fixed. (Thanks to Tony Finch.) [GL !3735]
-
 - The IPv6 Duplicate Address Detection (DAD) mechanism could
   inadvertently prevent ``named`` from binding to new IPv6 interfaces,
   by causing multiple route socket messages to be sent for each IPv6
@@ -123,5 +109,19 @@ Bug Fixes
   to ``bind()`` to each IPv6 address again if the first ``bind()`` call
   for that address failed with ``EADDRNOTAVAIL``. [GL #2038]
 
+- Addressed an error in recursive clients stats reporting which could
+  cause underflow, and even negative statistics. There were occasions
+  when an incoming query could trigger a prefetch for some eligible
+  RRset, and if the prefetch code were executed before recursion, no
+  increment in recursive clients stats would take place. Conversely,
+  when processing the answers, if the recursion code were executed
+  before the prefetch, the same counter would be decremented without a
+  matching increment. [GL #1719]
+
+- The introduction of KASP support inadvertently caused the second field
+  of ``sig-validity-interval`` to always be calculated in hours, even in
+  cases when it should have been calculated in days. This has been
+  fixed. (Thanks to Tony Finch.) [GL !3735]
+
 - LMDB locking code was revised to make ``rndc reconfig`` work properly
   on FreeBSD and with LMDB >= 0.9.26. [GL #1976]