Bits from the Debian Release Team: hard frozen trixie

Posted by bob on May 19, 2025 7:55 AM CST
Debian release team; By Paul Gevers
Mail this story
Print this story

Two days behind schedule, we have frozen trixie a bit more on 2025-05-17. This means that we are one step closer to the release of trixie.

Hard Freeze started

Two days behind schedule, we have frozen trixie a bit more on 2025-05-17. This means that we are one step closer to the release of trixie. 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 qa [3] or tracker [4].

Two quotes from the freeze policy [1]:

Please note that packages that are in trixie 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 trixie. Having changes in unstable that are not targeted/appropriate for trixie could complicate fixes for your package and related packages (like dependencies and reverse dependencies).

Help needed

Now is a good time to help testing installations [5] and upgrades to find as many issues as possible. There's still a bunch of RC bugs ([6] lists those in key packages), so fixing those helps a lot too.

Release notes

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 [7], but even if you can only point us at issues that's already appreciated.

mips64el and riscv64

The Release Team has decided to drop mips64el as a release architecture and to add riscv64.

Full Story

  Nav
» Read more about: Story Type: Announcements; Groups: Debian

« Return to the newswire homepage

This topic does not have any threads posted yet!

You cannot post until you login.