Release standards (RC bugs)What they are for packages
What they are for architectures
Which of them aren't being met
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
[2021-03-20]Bits from the Release Team: frozen hard to get hot
[2021-02-13]Bits from the Release Team: bullseye froze softly
[2021-01-13]Bits from the Release Team: bullseye freeze started and its architectures + erratum
[2020-11-08]Bits from the Release Team: winter^Wfreeze is coming
[2020-03-12]Updated freeze policy for bullseye and (tentative) freeze dates
[2020-02-15]Bits: new policy on out-of-sync and Release Team composition
[2019-07-07]Bits from the Release Team: ride like the wind, Bullseye!
[2019-06-11]Planned release of buster on 2019-07-06 and the last weeks up to the release
[2019-04-14]Bits from the Release Team: buster freeze update
[2019-03-12]Bits from the Release Team: Debian 10 'buster' is frozen; let's get it in shape
Next point releases
stable (10.10)Not yet planned
Key release dates
[2021-01-12]Transition and (build-)essential Freeze
[2021-03-12]Hard Freeze - for key packages and packages without autopkgtests
[ TBA ]Full Freeze
- Frozen packages
- Removal and entering hints
- 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
- 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.
- 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.
- 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.
- 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.