Release standards (RC bugs)What they are for packages
What they are for architectures
Which of them aren't being met
Recent release updates
[2016-Jul-06]Bits from the release team: Winter is Coming (but not to South Africa)
[2016-Mar-03]Bits from the Release Team: A Slightly Moveable Feast
[2015-Apr-26]The Jessie release got a bit Stretch'ed
[2015-Mar-31]Jessie Release Date: 2015-04-25
[2015-Mar-08]Status on the Jessie release
[2015-Feb-04]Permanent removals from testing for Jessie
[2014-Nov-25]Jessie Release Progress and a stricter freeze policy
[2014-Nov-09]Release Team Sprint Results
[2014-Nov-05]Bits from the release team: Jessie Freeze
[2014-Oct-05]Increasing the testing migration delay
Next point releases
stable (8.6)Being planned; likely September
Key release dates
[2016-Dec-05]Mandatory 10-day migrations
[2017-Jan-05]Soft freeze (no new packages, no re-entry, 10-day migrations)
As always, Debian 9 "Stretch" will be released "when it's ready".
- Frozen packages
- removal and entering hints
- list of candidates for automatic removal from testing
- 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
- NEW queue summary for oldstable-proposed-updates
- 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 twice daily 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.