On Sunday, February 19 2023, Sebastian Ramacher wrote: > On 2023-02-18 19:03:17 -0500, Sergio Durigan Junior wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian....@packages.debian.org >> Usertags: unblock >> >> Hi there, >> >> I decided to file this request even though this is *not* going to >> involve any transition nor anything big. Please let me know if you >> prefer to be contacted via other channels. >> >> [ Reason ] >> >> poke has recently released version 3.0. Unfortunately, due to personal >> reasons, I was unable to work on updating our package until this >> weekend. I believe it is in the best interest of our users to have poke >> 3.0 shipped in bookworm, not only because of the several bugs that are >> being fixed, but also because other GNU/Linux distributions are already >> shipping the latest version to their users. >> >> [ Impact ] >> >> Shipping the current version of poke in testing (2.4) will make the >> bookworm release already outdated when compared to other distributions. > > Note that there is no automatic blocking of new upstream releases. From > https://release.debian.org/bookworm/freeze_policy.html > > "Starting 2023-02-12, only small, targeted fixes are appropriate for > bookworm. We want maintainers to focus on small, targeted fixes. This is > mainly at the maintainers discretion, there will be no hard rule that > will be enforced."
Thank you for the reply. I understand that there's no real enforcement, but I decided to file this bug out of courtesy for the release team's work. > In any case, if you want us to judge if the update to 3.0 would be > acceptable under this rule, we need more info. What's new in the > release? Is this a small update or a major update? etc. There are many new features and bugfixes in this release. It is a major update, but doesn't introduce new binary packages nor changes that affect other Debian packages. You can see a summary of new changes here: https://sources.debian.org/src/poke/3.0%2Bdfsg-1/NEWS/#L10 >From lines 10 to 313. I understand that it is a lot to read and digest, and you probably have more important things to do, so I'm not expecting an in-depth analysis here. Thank you, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible https://sergiodj.net/