Prepare release notes for BIND 9.16.49

diff --git a/doc/arm/notes.rst b/doc/arm/notes.rst
index 1fecc7758626295814343161f258d9394cde9528..620271a41c239a6b5e803ba36a0b941d97c3f42f 100644 (file)
--- a/doc/arm/notes.rst
+++ b/doc/arm/notes.rst
@@ -46,6 +46,7 @@ for Microsoft Windows operating systems.
 
 .. include:: ../notes/notes-known-issues.rst
 
+.. include:: ../notes/notes-9.16.49.rst
 .. include:: ../notes/notes-9.16.48.rst
 .. include:: ../notes/notes-9.16.47.rst
 .. include:: ../notes/notes-9.16.46.rst

diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-9.16.49.rst
similarity index 64%
rename from doc/notes/notes-current.rst
rename to doc/notes/notes-9.16.49.rst
index 7129ac64f77e2d792f69c96d037df1f16331e801..259d30ab80a70fd2aa90cd14d0f6b45beed88a1f 100644 (file)
--- a/doc/notes/notes-current.rst
+++ b/doc/notes/notes-9.16.49.rst
@@ -12,44 +12,29 @@
 Notes for BIND 9.16.49
 ----------------------
 
-Security Fixes
-~~~~~~~~~~~~~~
-
-- None.
-
-New Features
-~~~~~~~~~~~~
-
-- None.
-
-Removed Features
-~~~~~~~~~~~~~~~~
-
-- None.
-
-Feature Changes
-~~~~~~~~~~~~~~~
-
-- None.
-
 Bug Fixes
 ~~~~~~~~~
 
 - A regression in cache-cleaning code enabled memory use to grow
   significantly more quickly than before, until the configured
-  ``max-cache-size`` limit was reached. This has been fixed. :gl:`#4596`
+  ``max-cache-size`` limit was reached. This has been fixed.
+  :gl:`#4596`
 
-- Using :option:`rndc flush` inadvertently caused cache cleaning to
+- Using ``rndc flush`` inadvertently caused cache cleaning to
   become less effective. This could ultimately lead to the configured
   ``max-cache-size`` limit being exceeded and has now been fixed.
   :gl:`#4621`
 
-- A use-after-free assertion might get triggered when the overmem cache
-  cleaning triggers. :gl:`#4595`
+- The logic for cleaning up expired cached DNS records was
+  tweaked to be more aggressive. This change helps with enforcing
+  ``max-cache-ttl`` and ``max-ncache-ttl`` in a timely manner.
+  :gl:`#4591`
 
-  ISC would like to thank to Jinmei Tatuya from Infoblox for bringing
-  this issue to our attention.
+- It was possible to trigger a use-after-free assertion when the overmem cache
+  cleaning was initiated. This has been fixed. :gl:`#4595`
 
+  ISC would like to thank Jinmei Tatuya of Infoblox for bringing
+  this issue to our attention.
 
 Known Issues
 ~~~~~~~~~~~~