bookworm release planned on 2023-06-10 and the last weeks up to the release
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Release date
============
We plan to release on 2023-06-10.
If you want to celebrate it, please consider attending a Debian
release party, or hosting your own! See
https://wiki.debian.org/ReleasePartyBookworm for more information.
(Note: the release process typically takes the whole day and the
release isn't done until the early hours of Sunday UTC.)
Full Freeze date
================
With the release date set, it's time to announce the Full Freeze [1]
date: Wednesday 2023-05-24. This means that from that moment on, every
package requires a manual unblock [2] by the release team if it needs
to migrate to bookworm. Please note that, as with all freezes, the new
rules apply for all packages that haven't migrated to testing yet (not
only for uploads after the freeze).
For all uploads, please review the Freeze Policy [1] once again to
make sure you know what is appropriate at this phase of the release.
The final weeks up to the release
=================================
In the last week prior to the freeze, testing will be completely
frozen and only emergency bug fixes will be considered in this period.
Please consider Sunday 2023-05-28 at 12:00 UTC the absolute last
moment for submitting unblock requests for bookworm.
Changes that are not ready to migrate [3] to testing at that time will
not be included in bookworm for the initial release. However, you can
still fix bugs in bookworm via point releases if the changeset follows
the rules for updates in stable.
Upgrade testing
===============
If you are in a position to carry out upgrade testing from bullseye to
bookworm in the field, now is the time to do so and send your feedback
as a bug report against the "upgrade-reports" pseudo-package.
Release notes
=============
Please ensure that any information about your packages which should
form part of the release notes is prepared in plenty of time to allow
for review and translations. Release notes coordination happens in the
BTS in bugs filed against the "release-notes" pseudo-package and in
merge requests on salsa [4].
For the release team,
Paul
[1] https://release.debian.org/testing/freeze_policy.html#full
[2] please use $(reportbug release.debian.org) to get the tags and
template right
[3] The testing migration excuses must not mention *blocked* (due to
dependency issues, CI or piuparts failures or other reasons). It is
acceptable if the required age has not been reached at this time.
[4] https://salsa.debian.org/ddp-team/release-notes/
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmRKt74ACgkQnFyZ6wW9
dQp4hAgAxkDQU5lXXfooSFm1rHYJLDRYSW14xv9GjnnykHguQeE+f2/xW6gAFy6D
tmlPk1T49T724yL/R9XVMgtQzxAGGp+nUVq9ZeBwArSSWqX4YsEkwQZxlz6/I6al
jSvrlAzfIrXXFIvPAkqFqXyHCkjW4iF4eOG4klJdzLL6wi4+6nrOs58EQ1h20WsW
eUKnM1aSfARyGuURz9PBHkTq+YMmdM0/eRmatnRRYh4LimOYjFkJrjiAFPgEoxdG
idyISweH1jHr7FQhRNj1iDnrmvdZMTvOIKIzBpfaaT8e+/TIYTJSxeWBuXeaRT7d
dTIhEv/WEEyw7on0obioXV+L340w/A==
=KXaJ
-----END PGP SIGNATURE-----
Reply to: