Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[News] bookworm's freeze has started :)

User discussion about Debian Development, Debian Project News and Announcements. Not for support questions.
Post Reply
Message
Author
User avatar
wizard10000
Global Moderator
Global Moderator
Posts: 551
Joined: 2019-04-16 23:15
Location: southeastern us
Has thanked: 75 times
Been thanked: 85 times

[News] bookworm's freeze has started :)

#1 Post by wizard10000 »

Got rid of my Liquorix kernels this morning so I can file legit bug reports without rebooting first :)

https://lists.debian.org/debian-devel-a ... 00004.html
we see things not as they are, but as we are.
-- anais nin

User avatar
donald
Debian Developer, Site Admin
Debian Developer, Site Admin
Posts: 1041
Joined: 2021-03-30 20:08
Has thanked: 185 times
Been thanked: 240 times

Re: [News] bookworm's freeze has started :)

#2 Post by donald »

Bits from the Release Team: bookworm in hard freeze

https://lists.debian.org/debian-devel-a ... 00004.html

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/fre ... .html#hard
[2] https://release.debian.org/key-packages.html
[3] https://qa.debian.org/excuses.php
[4] https://lists.debian.org/debian-devel/2 ... 00335.html
[5] https://udd.debian.org/bugs.cgi?release ... ml#results
[6] https://salsa.debian.org/ddp-team/release-notes/
Typo perfectionish.


"The advice given above is all good, and just because a new message has appeared it does not mean that a problem has arisen, just that a new gremlin hiding in the hardware has been exposed." - FreewheelinFrank

User avatar
BBQdave
df -h | participant
df -h | participant
Posts: 152
Joined: 2011-09-25 03:38
Location: North Carolina
Has thanked: 9 times
Been thanked: 14 times

Re: [News] bookworm's freeze has started :)

#3 Post by BBQdave »

@donald Thanks for the update!

I've been watching and reading daily throughout the Debian site for updates on Bookworm. Of course the first place I see updated information about hard freeze is here :) And I am happy it is going well :)
On quest for blue smoke and red rings!
Debian 12 Toshiba Satellite C655 | i3 2.3Ghz | Intel HD Graphics 3000 | 8GB RAM | 65GB SSD

User avatar
donald
Debian Developer, Site Admin
Debian Developer, Site Admin
Posts: 1041
Joined: 2021-03-30 20:08
Has thanked: 185 times
Been thanked: 240 times

Re: [News] bookworm's freeze has started :)

#4 Post by donald »

bookworm release planned on 2023-06-10 and the last weeks up to the release

https://lists.debian.org/debian-devel-a ... 00007.html
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/free ... .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/
Typo perfectionish.


"The advice given above is all good, and just because a new message has appeared it does not mean that a problem has arisen, just that a new gremlin hiding in the hardware has been exposed." - FreewheelinFrank

User avatar
None1975
df -h | participant
df -h | participant
Posts: 1387
Joined: 2015-11-29 18:23
Location: Russia, Kaliningrad
Has thanked: 45 times
Been thanked: 64 times

Re: [News] bookworm's freeze has started :)

#5 Post by None1975 »

Thank you for the info, donald.
OS: Debian 12.4 Bookworm / DE: Enlightenment
Debian Wiki | DontBreakDebian, My config files on github

User avatar
donald
Debian Developer, Site Admin
Debian Developer, Site Admin
Posts: 1041
Joined: 2021-03-30 20:08
Has thanked: 185 times
Been thanked: 240 times

Bits from the Release Team: bookworm nearly ready for release

#6 Post by donald »

https://lists.debian.org/debian-devel-a ... 00000.html


Dear all,

Quiet period
============

According to plan [1], we entered the quiet period leading up to the
release of bookworm on 2023-06-10. We have even managed unblock
requests filled well beyond the deadline and even unblocked a couple
of packages with RC bugs fixed but without a request to make bookworm
the best we can have.


Future bug fixes
================

There are still about 100 known RC bugs affecting bookworm, but we
have accepted to release having them included. Most of them will be
mentioned in the Release Notes. No doubt, more issues will be found
after the release when more systems will be running bookworm. As on
previous occasions, we anticipate that the first point release for
bookworm will occur approximately one month after the release.

Please co-ordinate fixes which you would like to see included in the
point release with the Stable Release Managers (SRMs) via a "pu" bug
against the release.debian.org pseudopackage, including a debdiff of
the current and proposed source packages. Remember to use reportbug
unless you enjoy crafting the metadata by hand.

For uploads fixing security issues, please coordinate with the
Security Team.


Release Notes
=============

Contrary to what many seem to perceive, the Release Notes keep being
updated as issues against it are reported. So, if you encounter issues
(or new features) that warrant to be mentioned, please propose it for
inclusion. Preferable with a proposed text as a merge request [2],
alternatively as a plain bug in the BTS against the release-notes
package.

Paul

[1] https://lists.debian.org/debian-devel-a ... 00007.html
[2] https://salsa.debian.org/ddp-team/relea ... e_requests
Typo perfectionish.


"The advice given above is all good, and just because a new message has appeared it does not mean that a problem has arisen, just that a new gremlin hiding in the hardware has been exposed." - FreewheelinFrank

Post Reply