T0@st
News Editor
- Joined
- Mar 7, 2023
- Messages
- 2,077 (3.14/day)
- Location
- South East, UK
A press release (dated April 27) states: "We plan to release Debian 12.0 "Bookworm" on June 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. 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 date: Wednesday May 24. This means that from that moment on, every package requires a manual unblock by the release team if it needs to migrate to bookworm. Please note that, as with all freezes, the newrules 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 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 May 28 at 12:00 UTC the absolute last moment for submitting unblock requests for bookworm. Changes that are not ready to migrate 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.
View at TechPowerUp Main Site | Source
Full Freeze Date
With the release date set, it's time to announce the Full Freeze date: Wednesday May 24. This means that from that moment on, every package requires a manual unblock by the release team if it needs to migrate to bookworm. Please note that, as with all freezes, the newrules 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 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 May 28 at 12:00 UTC the absolute last moment for submitting unblock requests for bookworm. Changes that are not ready to migrate 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.
View at TechPowerUp Main Site | Source