On Thursday, December 02 2021, Athos Ribeiro wrote: > As per [1], bind 9.17 (Debian unstable) is a development version, while > 9.16 is an extended support one. Since jammy is LTS, we should refrain > from releasing with bind 9.17. > > ISC schedule says 9.18 will be out on Q1, 2022. > > I am wondering if we should > > a) merge 9.16.22 (which never landed in unstable, but is in debian > stable) or 9.16.23 (which is only available in salsa); > > b) do (a) for now and wait to see if 9.18 lands before the jammy feature > freeze. If it lands, we can perform a second merge; or > > c) Push this merge to January or February. If 9.18 does not land until > then, merge 9.16.2x
Thanks for the thoughtful comment, Athos. We've discussed this in private, so you know that my preference is (c). Although you could merge 9.16.2x right now, this would mean going "ahead" of Debian (in the sense that we'd be releasing a version that is not and has never been present in unstable), which requires a bit more work than a regular merge, and then maybe throwing this away if/when upstream releases 9.18 and Debian picks it up (assuming they both do this before our Feature Freeze). So yeah, I think we should postpone this merge to the beginning of February and reassess the situation when we get there. If there's no 9.18 by then, you can merge 9.16.2x and be done with it. Thanks, -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946833 Title: Merge bind9 from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1946833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
