Bits from the Release Team: bookworm in hard freeze
Hi all,
According to schedule, we have frozen bookworm a bit more (2023-03-12). This means that we are one step closer to the release of bookworm. Like mentioned before we expect everyone to follow the freeze policy [1]. This means that from now on key packages [2] and packages without significant autopkgtest coverage need to be unblocked by the release team to be able to migrate from unstable to testing. If you need to request an unblock, check that your request is in line with the freeze policy and use $(reportbug release.debian.org) in order to get the meta data correct and get the template that helps us get the right information.
Note that packages that are not on the key-packages list, with non-superficial autopkgtests that succeed on all architectures and don't cause regressions will migrate without an unblock after 20 days. If you're unsure about the current migration status of your package, you can check it at [3].
Now is a good time to help testing installations [4] and upgrades to find as many issues as possible. There's still a bunch of RC bugs [5], so fixing those helps a lot too.
Please also remember to file bugs against the release-notes pseudo package if you know of issues that deserve being mentioned in the release notes. We welcome reports that include a proposed text or merge requests on salsa [6], but even if you can only point us at issues that's already appreciated.
On behalf of the Release Team,
Paul
[1] https://release.debian.org/bookworm/freeze_policy.html#hard
[2] https://release.debian.org/key-packages.html
[3] https://qa.debian.org/excuses.php
[4] https://lists.debian.org/debian-devel/2023/02/msg00335.html
[5] https://udd.debian.org/bugs.cgi?release=bookworm&merged=ign&rtbookworm-will-remove=ign&...
[6] https://salsa.debian.org/ddp-team/release-notes/
Debian 12 Bookworm is now in "hard freeze," according to Paul Gevers' announcement, which means that in order to move from unstable to testing, important packages and packages with little autopkgtest coverage must now be unblocked by the release team.
