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-Nov-27]Bits from the Stable Release Managers
[2017-Jun-18]Bits from the Release Team: this critter needs help!
[2017-May-26]Planned release of stretch on 2017-06-17 and the last weeks up to the release
[2017-Apr-27]Bits from the Release Team: release update
[2017-Apr-17]Updates to testing migration schedules
[2017-Apr-15]Status on the stretch release
[2017-Feb-05]Bits from the Release Team: stretch is frozen
[2017-Jan-07]Release update: Soft freeze for stretch
[2016-Dec-09]Release update: Mandatory 10 day delay for migrations and other upcoming events
[2016-Nov-05]Release update: Transition freeze and other upcoming events
[2016-Oct-31]Release Architectures for Debian 9 'Stretch'
Next point releases
stable (9.2)Not yet planned (possibly mid-late September)
oldstable (8.10)Not yet planned
Key release datesNo key dates have been planned yet for the Buster release cycle.
- 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.