Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition

[Ondřej Surý]

The repository labels are best approximation that allow you to stay on a single repository and get the upgrades when needed. The other option was to have repositories named bind-9.16, bind-9.18 and so on, but that would require manual intervention every time there’s a version bump. The BIND 9.16 EOL means there will be no further updates, it doesn’t mean that the version is broken the moment we mark it as EOL. It is difficult to explain to leadership why something was marked as EOL, but is still active in the pipeline. I don’t understand. Are you saying that you can’t upgrade to BIND 9.18 because of how the repositories are structured or named? The repositories are provided for the convenience and you can still build your own binaries or packages if those are not convenient for you. Ondrej -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. On 17. 6. 2024, at 20:24, Robert Wagner <rwag...@tesla.net> wrote:  If 9.16 was EOL at the end of April: https://kb.isc.org/docs/bind-9-end-of-life-dates  Help me understand why ESV wasn't rolled to 9.18 at that time or before in 2023 when it was marked as ESV? It is difficult to explain to leadership why something was marked as EOL, but is still active in the pipeline. The rollover plan and the graphic ISC's Software Support Policy and Version Numbering do not seem to match. Robert Wagner From: bind-users <bind-users-boun...@lists.isc.org> on behalf of John Thurston <john.thurs...@alaska.gov> Sent: Monday, June 17, 2024 11:19 AM To: bind-users@lists.isc.org <bind-users@lists.isc.org> Subject: Re: Question about ISC BIND COPR repositories for 9.16->9.18 ESV transition   This email originated from outside of TESLA Do not click links or open attachments unless you recognize the sender and know the content is safe. Have you considered scheduling the change in version published in each COPR repository so it doe not coincide with the release of a new version of BIND? 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.  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. -- Do things because you should, not just because you can. John Thurston 907-465-8591 john.thurs...@alaska.gov Department of Administration State of Alaska On 6/17/2024 2:32 AM, Michał Kępień wrote: 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. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users