Release standards (RC bugs)
What they are for packagesWhat they are for architectures
Which of them aren't being met
Architecture status
Freeze policy
Unblock requests FAQ
Recent stable release updates
[2019-08-04]Bits from the Stable Release Managers[2018-04-16]Bits from the Stable Release Managers
Recent release updates
[2023-12-16]Bits from the Release Team: Cambridge sprint update[2023-06-10]Bits from the Release Team: a trixie customer[2023-06-04]Bits from the Release Team: bookworm nearly ready for release[2023-04-27]bookworm release planned on 2023-06-10 and the last weeks up to the release[2023-03-16]Bits from the Release Team: bookworm in hard freeze[2023-02-17]Bits from the Release Team: bookworm in soft freeze[2023-01-19]Bits from the release team: bookworm freeze started[2022-10-13]Bits from the Release Team: are you ready to skate yet?[2022-07-16]Bits from the Release Team: on merged-/usr and the bookworm release[2022-03-14]Bits from the Release Team: bookworm freeze dates (preliminary)
Next point releases
stable (12.8)9 November 2024stable (12.9)11 January 2025
Key release dates
[TBA]Transition and Toolchain Freeze[TBA]Soft Freeze[TBA]Hard Freeze - for key packages and packages without autopkgtests[TBA]Full Freeze[TBA]Deadline for unblock requests
The release date for Debian 13 "trixie" hasn't been decided yet.
Useful links
- Frozen packages
- Removal and entering hints
- On the topic of key packages and autoremoval
- List of candidates for automatic removal from testing
- List of key packages
- Packages blocked from uploads to unstable due to transitions
- Transition tracker
- Documentation on requesting binNMUs and other wanna-build actions
- NEW queue summary for stable-proposed-updates
- Autopkgtest pseudo excuses for experimental
- Our wiki site
- Our tools
Suite update policy
- stable
- Fast response for security updates. Minor updates include security and other important fixes only. Major updates are sourced from testing, and are infrequent, but large.
- testing
- Security updates are irregular and unreliable. Release standards are almost continually met. Updates are automatically sourced from unstable, happen four times each day and are usually small.
- unstable
- Security updates are made by the maintainer; they may not be effective on all architectures, and may be delayed. Packages uploaded may not meet release standards, but any breakage is expected to be fixed promptly. Updates are made by maintainers.
- experimental
- Packages that are not suitable for widespread use yet. They may or may not meet release standards, as it is commonly used as a staging area for uploads to unstable. Updates are made by maintainers.