Fosdem 2007
Luk Claes <luk@debian.org>

• Packages are usually uploaded to unstable
• They enter testing after some rough testing
• Testing is declared stable from time to time (release)
• Experimental for packages not suitable for next release

• Ensure testing meets the release targets
• Ensure testing is not broken
• Keep the strings together (base packages, kernel, toolchain, ftp scripts, installer, ...)
• Collect and distribute information

• Release Managers: Steve Langsak (vorlon), Andi Barth (aba)
• Release Assistents: Marc Brockschmidt (he), Luk Claes (luk), etc.
• "Role Account": debian-release@lists.debian.org
• http://release.debian.org/

• Packages are considered first after 2, 5 or 10 days
• Packages must be in sync on all release archs
• Packages must have not more release critical bugs
• Packages must not break any packages currently in testing, unless a newer version that doesn't break is going in at the same time

• Packages need to be approved
• Packages must not break any packages currently in testing, unless a newer version that doesn't break is going in at the same time

• Remove packages (from testing)
• (un)block packages
• Force packages
• Allow packages with cyclic dependencies to enter testing
• change urgency

• No critical or grave bugs (makes the package or system unusable, or introduces a security hole)
• Releaseable from the maintainer point of view
• Canonical list of further issues at release.debian.org (autobuildable, ...)

• Make sure all release critical issues are handled prior to release
• Any changes in testing must not push us back
• Tackle the release blockers

• Sometimes, packages stuck together for testing migration
• Extremly bad in combination with buildd issues and library shlib bumps
• Lagging buildds create new dependencies on newer libs - longer waiting time

• Strategy: Discoverthe issues soon, use all tools to avoid it, in worst case do binary-only NMUs - and coordinate in time with buildd maintainers and ftp-masters
• Never upload a package into unstable that's not meant for next release!
• Maintainer should look at their package migration status before another upload

• Upload of final kernel
• About 100 Release Critical bugs: needs help - anyone can help
• We are heading for release - support us!