Bits from the Release Team: frozen hard to get hot
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all,
According to schedule, we froze bullseye a bit more last week
(12-03-2021). This means that we are one step closer to the release of
bullseye and we expect everyone to follow the freeze policy [1]. This
means that from now on key packages 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 and upgrades to find as
many issues as possible and fix rc bugs [4]. Please be aware of bug
984533 (libc6), 974552 (libcrypt1) and 953562 (libcrypt1) when you
do. Add information to those bug if you can help them forward.
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. Ideally with proposed text, or even via a merge request
on salsa [2], 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/bullseye/freeze_policy.html#hard
[2] https://salsa.debian.org/ddp-team/release-notes/
[3] https://qa.debian.org/excuses.php
[4] https://deb.li/rcbugs
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmBVAloACgkQnFyZ6wW9
dQrslwf/RzIt3dlbBBGbDZe/K/VSxaTY+/BQS6sJaG1fu0oH0wCGKRuKX3RhQjMz
IKHwCtApO2YXF2eNGhS7lPUjAdp7uF/edPM2fTZks5MPKfSKmdO062w3cXGRBrV3
T0qYmBHgGpQnzPWVdqnHxVbWBNhZn+lDM0TvS62te220NUmLhS+PtvnsqGDr2a5J
ES2ODi2X+hOkUbHkA6LpthEHHQGV3zfezLXbUzz73N36Yi3VFSDbMOiL7ruUaTuF
/jZvq31sV/05SLpWk4fMrtJ6D7+F6YkBF/XeaDHzEQz1V3Zq6en8Z5Xlnl+NC8hO
JcOnNNgZquj2Zd4XevwAXm4h38vXZQ==
=CSHG
-----END PGP SIGNATURE-----
Reply to: