Debian Release Management

Release standards (RC bugs)

Lenny	Squeeze	Wheezy
What they are for packages What they are for architectures Which of them aren't being met Architecture status Release goals	What they are for packages What they are for architectures Which of them aren't being met Architecture status Release goals	What they are for packages What they are for architectures Which of them aren't being met Architecture status Release goals

[2012-May-13] Bits from the Release Team: Freeze approaching!
[2012-Jan-25] Bits from the Release Team
[2011-Aug-01] Release Update: Goals, Arches, Rolling, Removals
[2011-Jun-28] Bits from the Release Team - minutes (pt 1), retrospective, time based freezes and more!
[2011-Mar-29] Bits from the Release Team - Kicking off Wheezy
[2011-Feb-06] squeeezy - wheezy ready for development
[2011-Jan-18] Release Update: timings, status and awesomeness
[2010-Dec-13] Release Update: deep freeze, remaining bugs, schedule, themes and Wheezy
[2010-Nov-14] Release Update - Upgrades, deep freeze info, BSPs
[2010-Oct-05] Release Team meeting minutes (and release update)

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 twice daily 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.