Debian bookworm in soft freeze

Other Distributions/OS
1

https://lists.debian.org/debian-devel-announce/2023/02/msg00003.html

Dear all,

Soft Freeze

Following our release calendar, we have frozen bookworm a bit
[1]. That means that from this week on we expect all uploads to be
small, targeted fixes and no new source packages are allowed into
bookworm. Source packages must also no longer add or drop binary
packages. All packages will have to age at least 10 days in unstable
before they are eligible for migration (including those having
autopkgtests). Quoting from the policy:

“”"
Starting 2023-02-12, only small, targeted fixes are appropriate for
bookworm. We want maintainers to focus on small, targeted fixes.

[…]

Please note that new transitions, new versions of packages that are
part of (build-)essential or large/disruptive changes remain
inappropriate.

[…]

Packages that are not in testing will not be allowed to migrate to
testing. This applies to new packages as well as to packages that were
removed from testing (either manually or by auto-removals).

[…]

Dropping or adding binary packages to a source package, moving
binaries between source packages or renaming source or binary packages
is no longer allowed. Packages with these changes will not be allowed
to migrate to testing. These changes are also no longer appropriate in
unstable.

Please note that packages that are in bookworm at the start of the
soft freeze can still be removed if they are buggy. This can happen
manually or by the auto-removals. Once packages are removed, they will
not be allowed to come back.

[…]

Don’t upload changes to unstable that are not targeted for
bookworm. Having changes in unstable that are not targeted/appropriate
for bookworm could complicate fixes for your package and related
packages (like dependencies and reverse dependencies).
“”"

State of bookworm

The state of bookworm is pretty good. We ask everybody to keep working
on fixing the remaining RC bugs (and please find and file those that
are currently unreported). [2] has the list we should drive down to
zero together. Please try out upgrading your bullseye systems to
bookworm now and report issue you encounter.

General

As always, talk to us, preferably via the bts, if you experience
issues that we need to be aware of or where you need help. Please be
aware it’s now a very busy time for us, so bear with us.

Our freeze policy is at [1].

On behalf of the release team,
Paul

3 Likes
2

Thx for sharing @chroot

1 Like
3

Yep, the bookworm installer actually works now.

2 Likes
4

In hard freeze now.

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

4 Likes
5

Thx for sharing @chroot