<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
If 9.16 was EOL at the end of April: <a href="https://kb.isc.org/docs/bind-9-end-of-life-dates" target="_blank" id="OWA8c431854-0bae-0fb3-eba7-42dfc4f42737" class="OWAAutoLink" rel="noopener noreferrer" data-auth="NotApplicable" data-linkindex="0" style="margin: 0px;">
https://kb.isc.org/docs/bind-9-end-of-life-dates</a> Help me understand why ESV wasn't rolled to 9.18 at that time or before in 2023 when it was marked as ESV?</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
It is difficult to explain to leadership why something was marked as EOL, but is still active in the pipeline.</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
The rollover plan and the graphic <a href="https://kb.isc.org/v1/docs/aa-00896" target="_blank" id="OWAc576561c-442a-2258-c267-479870d3582d" class="OWAAutoLink" rel="noopener noreferrer" data-auth="NotApplicable" data-linkindex="1" style="margin: 0px;">
ISC's Software Support Policy and Version Numbering</a> do not seem to match.</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
Robert Wagner</div>
<div class="elementToProof" style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="appendonsend"></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div id="divRplyFwdMsg" dir="ltr"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> bind-users <bind-users-bounces@lists.isc.org> on behalf of John Thurston <john.thurston@alaska.gov><br>
<b>Sent:</b> Monday, June 17, 2024 11:19 AM<br>
<b>To:</b> bind-users@lists.isc.org <bind-users@lists.isc.org><br>
<b>Subject:</b> Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition</span>
<div> </div>
</div>
<div style="background-color: rgb(213, 234, 255); padding: 0.8em; border-width: 1px; border-style: dotted; border-color: rgb(0, 51, 51);">
<span style="font-family: Cambria, "times new roman", garamond, serif; font-size: 10pt; color: rgb(255, 0, 0);">This email originated from outside of TESLA</span><span style="font-family: Calibri, sans-serif; font-size: 9pt;"><br>
</span>
<p style="line-height: 10pt; font-family: Cambria, "times roman", serif; font-size: 8pt;">
Do not click links or open attachments unless you recognize the sender and know the content is safe.</p>
</div>
<p>Have you considered scheduling the change in version published in each COPR repository so it doe
<i>not</i> coincide with the release of a new version of BIND?</p>
<p>I have some hosts tied to the COPR for BIND-ESV, and some tied to BIND. I hit a stumbling block during the last "roll over" event, and it took me a a bit to figure out if it was due to the switch of BIND-ESV from 9.11 - > 9.16 in the repository, or the switch
from 9.16.x -> 9.16.y in the code-release. </p>
<p>If we could have the version published in the BIND-ESV repository advance to the same version which was most recently published in BIND repository (i.e. ship 9.18.x in BIND, a couple of weeks later roll BIND-ESV to 9.18.x and BIND to 9.20.x, and a couple
of weeks later release 9.18.y and 9.20.y), then problems with the COPR "roll over" would be a little more obvious.</p>
<pre><div>--
Do things because you should, not just because you can.
John Thurston 907-465-8591
<a href="mailto:John.Thurston@alaska.gov" id="OWAb5d9c272-3a15-90fb-b1cb-2c1144b12d82" class="x_moz-txt-link-abbreviated OWAAutoLink">John.Thurston@alaska.gov</a>
Department of Administration
State of Alaska</div></pre>
<div>On 6/17/2024 2:32 AM, Michał Kępień wrote:</div>
<blockquote>
<pre><div>While I don't have a specific date for you, we plan to do such a
"rollover" again when BIND 9.20.1 or 9.20.2 gets released, i.e. in about
2-3 months from now. We will definitely roll all three repositories at
the same time, i.e.:
- "bind-esv" will move from 9.16 to 9.18,
- "bind" will move from 9.18 to 9.20,
- "bind-dev" will move from 9.19/9.20 to 9.21.</div></pre>
</blockquote>
</body>
</html>