<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi John,<div class=""><br class=""><div><blockquote type="cite" class=""><div class=""><div class=""><br class="">That document was last updated on Jan 5, 2022, so this news is at least three weeks old. I don't recall seeing anything on the "Announce" mailing list regarding the change in ESV designation. </div></div></blockquote><div><br class=""></div>…..<br class=""><blockquote type="cite" class=""><div class=""><div class="">Nor do I see any difference in the COPR packages:<br class=""><br class=""><a href="https://copr.fedorainfracloud.org/coprs/isc/bind-esv/" class="">https://copr.fedorainfracloud.org/coprs/isc/bind-esv/</a><br class=""><br class="">which continue to offer 9.11.<br class=""><br class="">A) Where was the ESV-switch announced? (I though I had my bases covered by subscribing to 'announce' and 'user' mailing lists. I need to find and plug this communication hole.)<br class=""></div></div></blockquote><div><br class=""></div>This is my fault. I am sorry. </div><div><br class=""></div><div>I posted a blog last June, in which we declared 9.16 ESV (and started marking it that way on the downloads page and in the release notes). <a href="https://www.isc.org/blogs/bind-update-summer2021/" class="">https://www.isc.org/blogs/bind-update-summer2021/</a></div><div><br class=""></div><div>We do try to keep the matrix showing EOL dates current here: <a href="https://kb.isc.org/docs/aa-00896" class="">https://kb.isc.org/docs/aa-00896</a>, and that hasn’t been changed since last summer, when we finally declared 9.16 ESV, 6 months after the point at which we would normally have done so. </div><div><br class=""></div><div>Normally, we would also send some reminders to the list(s) when we are at T-3 months from EOL. 2021 was a difficult year in more ways than one, and apparently, we didn’t do this. My only excuse, which is a weak one, is that I was reluctant to pull the plug on 9.11 until we were more confident that 9.16 was really solid, so I put it off. However, even though we failed to remind the list, we haven’t changed the 9.11 EOL date, it has been set for ages. </div><div><br class=""></div><div>I will send a note to bind-announce pointing out that it is time to move off of 9.11.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class=""><br class="">B) What are the plans for the 'bind-esv' COPR? (Will it soon start serving 9.16? Do I need to manually switch from 'bind-esv' to 'bind'? Is COPR dead?)<br class=""></div></div></blockquote><br class=""></div><div>Good question. This is admittedly confusing. </div><div><br class=""></div><div>We already have 3 BIND versions in our packages, bind, bind-dev and bind-esv. We have just a brief overlap here between 9.11 and 9.18, but we don’t want to create yet another repo. Because we are still patching 9.11, and we haven’t yet issued a new dev branch, we are putting 9.18.0 into the bind-dev repo, for now.</div><div><br class=""></div><div>In April, we plan to do a version rollover:</div><div>- bind-esv will go from 9.11 to 9.16</div><div>- bind will go from 9.16 to 9.18</div><div>- bind-dev will go from 9.18.1 to 9.19.0</div><div><br class=""></div><div>I hope this helps.</div><div><br class=""></div><div>Regards,</div><div><br class=""></div><div>Vicky Risk</div><div><br class=""></div></div></body></html>