This is a RM's TODO list for the Buster release, which might not be authorative or complete. The following things need to be done for the Buster release: == Tagging RC Bugs == At some point, we will have to tag the remaining RC bugs to filter what should be removed/deferred/fixed. It's possible to define our own sorting criteria by sending the following request to control@bugs.debian.org: {{{ user release.debian.org@packages.debian.org usercategory buster-sort * Codename [tag=] + Blockers for Codename [buster-is-blocker] + Planned for removal [buster-will-remove] + Ignored for Codename [buster-can-defer] }}} Then, usertagged bugs will be listed on: [[https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=release.debian.org@packages.debian.org;tag=buster-can-defer;tag=buster-will-remove;tag=buster-is-blocker;ordering=buster-sort]] Useful references about this feature are: * [[https://bugs.debian.org/424427|#424427: [bts] should support usercategory]] * [[Devscripts/bugs]] == Before freeze == * (./) Decide on a code name for ''+2'': bookworm * (./) Get that included in BTS tags (Filed as #917538): * (./) @gTags in /srv/bugs.debian.org/etc/config on bugs-master.debian.org * (./) bts_release_tags and bts_release_ignore_tags [[https://salsa.debian.org/webmaster-team/webwml/blob/master/english/Bugs/pkgreport-opts.inc|in webwml]] * (./) Edit wiki pages to add the new release: ReleaseParty DebianReleases DebianBuster DebianStretch NewInBuster Glossary * (./) Edit/add deb.li pages to add the new release: relparty get * (./) Theme (artwork) design should be finalised and decided * [ ] Prepare the website changes * (./) Ensure that the following pages exist on debian.org/releases/buster * (./) index * (./) credits * (./) errata * (./) installmanual (requires installmanual is being built for RELEASE as well) * (./) releasenotes (requires releasenotes is being built for RELEASE as well) * (./) reportingbugs * (./) There should also be a page for debian.org/releases/ as there are some links to it. * [ ] The pages should say they are beta versions/not released etc. at this point [elbrus git pushed] * (./) Assert the architecture list is up to date (release.data), new ports should be available on https://debian.org/ports (ports/index.wml) * (./) Ensure that updates to the installation-guide appear on the website (d-i) [To avoid a repeat of <>] [elbrus: on 2019-04-05 the latest version is from 24 March] * (./) Ensure that updates to the release-notes appear on the website * (./) Decide on Release Architectures * [ ] Ensure image builds work for all release architectures * [ ] Generate and add release keys to debian-archive-keyring (filed as #917535 and #917536) * SRMs generate one (technically, RMs can generate it too, but SRMs will need it post release) * FTP-masters generate several (see <>) * (./) Have FTP masters create security + backports archive for upcoming release( (filed as #917537) * Re Announcements: Remember to clarify that -backports is a read-only to the sake of assisting with upgrades. * [ ] Check with security team and backports team that it is possible to build uploads for -security and -backports * (./) Have DSA upgrade a non-critical machine (requested in RT #7718) * Suggestions include: lindsay.debian.org (the host doing the lintian archive-wide run) * (./) Have DSA upgrade a buildd for each architecture (requested in RT #7720) * Do a checklist for each architecture/buildd machine * (./) Have DSA contact DebianList:debian-services-admin to ask service maintainers to prepare their services for the new release ([[https://lists.debian.org/msgid-search/acfb03f289f11cc472e2ea4ac1a939c37ade4498.camel@debian.org|mail]]) (requested in RT #7719) * and include [[how-can-i-help]] output for the package list from each debian.org machine * (./) Coordinate plan for English review + translators of the release-notes, so everyone has time to do their work. * Some chapters can freeze before others (Notably, the "Issues" will want to stay open as long as possible) * Mail: debian-l10n-english@, debian-i18n@, debian-doc@. debian-release@ * [elbrus, 2019-04-05] first mails send. == Before a Release == * [ ] binNMU everything that has a Built-Using header and is using old versions to remove old source packages from the release. * (./) d-i should have (beta or even better rc) releases * (./) Do at least one DVD making dry run with the right installer, to ensure that everything fits properly. * (./) Install Guide should be up-to-date [[https://lists.debian.org/20190425081109.6ad2d0b226cf3d1c9fb3e523@mailbox.org]] * (./) ReleaseNotes need to be updated: * (./) Check with [[Teams/DebianKernel|Linux kernel team]] for specials with the Kernel * [elbrus, 2019-04-06 sent e-mail + reminder on 2019-04-24] * (./) Check with d-i team for specials with this update (check esp. if old versions of d-i should be purged if new versions enter $suite's d-i area) * (./) Check with [[Teams/Security|Security Team]] for lower supported packages: [[https://lists.debian.org/20190420210734.GA22183@pisco.westfalen.local]] * (./) Remove the draft flag * (./) Install & upgrade tests should reveal no undocumented (release notes, install guide) surprises * (./) Coordinate a release date at least 3 weeks before - involved teams/roles: * Required * FTP-masters * SRMs (need to sign the Release file for "stable" that becomes "oldstable") * Image team / Install media team * Press (media coverage + sending the press announcement) * Optional or/and Vetoers: * d-i (optional for the day itself, but can veto the day - if d-i doesn't work, we cannot release) * DSA (optional, but good to have in case of issues) * (./) Announce the release date on d-d-a, preferably coordinated with press@ / #d-publicity so they can do micronews * (./) Ensure that the planned release date is added to debian.org/releases * (./) Ensure that release.debian.org mentions the release date under "Key release dates" * Add release dates and relevant deadlines to the release calendar. * (./) Website: * Have a patch ready for template/debian/release_info.wml to update (https://salsa.debian.org/webmaster-team/webwml/merge_requests/172) * (./) Notify the [[Teams/Security|Security Team]] of an upcoming Release * (./) Notify the [[Teams/DebianCd|Debian CD]] team of an upcoming Release * [ ] Notify the DebianLive Team of an upcoming Release * [ ] Notify the Mirror team of an upcoming Release * (./) Notify the [[Teams/Publicity|publicity]] team of an upcoming Release * (./) Prepare [[Teams/Publicity/Announcements|press release]] * coordinate with d-i team for text for d-i changes * [ ] Prepare the wiki changes == While Releasing == Mention things that are happening on IRC so the [[Teams/Publicity|publicity]] team can [[Teams/Publicity/Release|relay]] to social media * (./) Check with the FTP-Masters * d-i needs to be moved * new win32-loader? * cleanup of $codename-proposed-updates and $codename-security * stable-updates needs its suite name hack updated to oldstable-updates * debtags need to be copied from unstable * (./) Check /srv/ftp-master.debian.org/ftp/dists/$codename/ChangeLog * (./) Check if /srv/ftp.debian.org/ftp/README was updated. * (./) Sign the release file * (./) Check that everything that should be released really was released * (./) Ask ftp-masters for an early mirror pulse to casulana and pettersson * (./) Notify [[mailto:debian-security@lists.debian.org|debian-security]] as people tend to cry occasionally * (./) Notify the Publicity Team, that Release is done (tell them when the Release will be pushed out) * (./) Notify the [[Teams/DebianCd|Debian CD]] Team that the Release is done * (./) Notify the DebianLive Team that the Release is done * (./) Update the website * Publish the ReleaseNotes * (./) Notify the Debian WWW team that the Release is done and is time to update the website * Ask www team to update english/releases/ * Ask service owner to update packages.debian.org search interface (default to new stable release) * Ask publicity team to publish Release Announcement in website news area * Ask www team to force website update * Check after update the website to make sure that it refers to new stable in [[http://www.debian.org/releases/|release pages]] * (./) Update Wiki: * Update these wiki pages (coordinated with ReleaseNotes's editor): FrontPage DebianReleases DebianReleases/PointReleases DebianTesting DebianStable DebianOldStable [[Status/Stable]] StableUpdates StableProposedUpdates [[Backports]] [[Welcome/Users]] [[Glossary]] [[DebianBuster]] [[DebianStretch]] [[DebianBullseye]] ReleaseParty [[ReleasePartyBuster]] [[ReleasePartyBullseye]] [[DebianArt/Themes]] [[DebianDesktop/Artwork]] [[DebianDesktop/Artwork/Bullseye]] [[ArchiveQualification/Bullseye]] [[Teams/DebianCD/ReleaseTesting]] [[Teams/Dpkg/FAQ]] * (./) Ping the wiki team to run /srv/wiki.debian.org/bin/get-debian-suite-info * [ ] Watch mailing-lists for abnormalities * [ ] Backup/flush hint files. * (./) Update release.debian.org/{oldoldstable,oldstable,stable,testing} symlinks; create the new suite for testing as a copy of stable and edit == After the release == * (./) Notify Distrowatch; send a mail to distro@distrowatch.com * (./) Notify [[https://lwn.net/op/FAQ.lwn#contact|LWN]], [[https://news.ycombinator.com/|Hacker News]], [[http://www.reddit.com/r/debian|Reddit]], [[http://slashdot.org/submission|slashdot]] (they noticed) * [ ] Notify [[https://freshcode.club/|fresh(code)]] * (./) [[Teams/Publicity/micronews|Propose]] a micronews item on the [[irc://irc.debian.org/debian-publicity|#debian-publicity]] [[IRC]] channel * [ ] Blog about release team experiences * (./) Bits from the release team mail * (./) Update the [[Teams/Publicity/Timeline|Debian timeline]] * [ ] Update the [[https://www.debian.org/doc/misc-manuals#history|Project History]] document and upload to stable-p-u * (./) Notify [[Derivatives/CensusQA#release|derivatives]] about the release * [ ] Update all the places that [[SuitesAndReposExtension#Existing_hardcoding|hardcode]] suite names or codenames * (./) Notify owner@bugs.debian.org that the codename to suite mapping needs to be updated on the RC bugs pages: https://bugs.debian.org/release-critical/debian/ * [ ] Before enabling Britney and removing freeze hints: * Ensure that the BTS knows that testing has changed (to stop RC bugs regressions from migrating to testing) * Ensure dinstall run smoothly * ...