Set up release notes for BIND 9.19.14

doc/notes/notes-current.rst

@@ -9,7 +9,7 @@
 .. See the COPYRIGHT file distributed with this work for additional
 .. information regarding copyright ownership.
 
-Notes for BIND 9.19.13
+Notes for BIND 9.19.14
 ----------------------
 
 Security Fixes
@@ -20,8 +20,7 @@ Security Fixes
 New Features
 ~~~~~~~~~~~~
 
-- ``dnstap-read`` can now print long timestamps with millisecond precision.
-  :gl:`#2360`
+- None.
 
 Removed Features
 ~~~~~~~~~~~~~~~~
@@ -36,29 +35,7 @@ Feature Changes
 Bug Fixes
 ~~~~~~~~~
 
-- When the same ``notify-source`` address and port number was configured for
-  multiple destinations and zones, an unresponsive server could tie up the
-  socket until it timed out; in the meantime, NOTIFY messages for other servers
-  silently failed.``named`` will now retry these failing messages over TCP.
-  NOTIFY failures are now logged at level INFO. :gl:`#4001` :gl:`#4002`
-
-- When ISC_R_INVALIDPROTO (ENOPROTOOPT, EPROTONOSUPPORT) is returned from
-  libuv, treat it as a network failure, mark the server as broken and don't
-  try again. :gl:`#4005`
-
-- The :any:`max-transfer-time-in` and :any:`max-transfer-idle-in` options
-  were not implemented when the BIND 9 networking stack was refactored
-  in 9.16. The missing functionality has been re-implemented and
-  incoming zone transfers now time out properly when not progressing.
-  :gl:`#4004`
-
-- Log file rotation did not clean up older versions of log files when the
-  logging :any:`channel` configured an absolute path as ``file`` destination.
-  This has now been fixed. :gl:`#3991`.
-
-- The read timeout in ``rndc`` is now 60 seconds, matching the behavior
-  in BIND 9.16 and earlier. It had previously been lowered to 30 seconds
-  by mistake. :gl:`#4046`
+- None.
 
 Known Issues
 ~~~~~~~~~~~~