This is a RM's TODO list, which might not be authoritative or complete. The following things need to be done for a 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 request@bugs.debian.org:# {{{ user release.debian.org@packages.debian.org usercategory bookworm-sort * bookworm [tag=] + Blockers for bookworm [bookworm-is-blocker] + Planned for removal [bookworm-will-remove] + Ignored for bookworm [bookworm-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=bookworm-can-defer;tag=bookworm-will-remove;tag=bookworm-is-blocker;ordering=bookworm-sort]] Useful references about this feature are: * [[DebianBug:424427|#424427: [bts] should support usercategory]] * [[Devscripts/bugs]] Another very useful view on the RC bugs is via [[https://udd.debian.org/dev/cgi-bin/rcblog7.cgi|this udd view]]. == Before freeze == * (./) Decide on a code name for ''bookworm+2'': [[https://lists.debian.org/debian-devel-announce/2022/10/msg00004.html|forky]] * (./) Get that included in BTS tags: * (./) @gTags in /srv/bugs.debian.org/etc/config on bugs-master.debian.org (DebianBug:1029978) * (./) 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 forky: DebianReleases DebianForky DebianTrixie [[Glossary]] * (./) Add deb.li pages for bookworm+2: [[https://deb.li/forky|forky]] [[https://deb.li/getforky|getforky]] * (./) Edit/create wiki pages for bookworm: ReleaseParty ReleasePartyBookworm DebianBookworm NewInBookworm * (./) Update deb.li pages to use bookworm: [[https://deb.li/relparty|relparty]] * (./) Theme (artwork) design should be finalised and decided [[https://lists.debian.org/debian-desktop/2022/12/msg00000.html|announcement]] * (./) Prepare the website changes * (./) Ensure that the following pages exist on https://debian.org/releases/bookworm * (./) index * (./) credits * (./) errata * (./) installmanual (requires installmanual is being built for bookworm as well) * (./) releasenotes (requires releasenotes is being built for bookworm as well) * (./) reportingbugs * (./) There should also be a page for debian.org/releases/trixie as there are some links to it. * (./) The pages should say they are beta versions/not released etc. at this point * (./) 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 <>] * (./) 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 (see DebianBug:1029215 + DebianBug:1029214) * (./) SRMs generate one (technically, RMs can generate it too, but SRMs will need it post release) * (./) "reportbug ftp.debian.org" to get it added to https://ftp-master.debian.org/keys.html (see DebianBug:1034259) * (./) FTP-masters generate several ([[https://lists.debian.org/debian-devel-announce/2023/03/msg00001.html|announcement]]) * (./) Have FTP masters create security + backports archive for upcoming release * [ ] Re Announcements: Remember to clarify that -backports is read-only for the sake of assisting with upgrades. * [ ] Remember to add the ACL to the bookworm-backports and bullseye-backports-sloppy suites * (./) Coordinate with security team to do a test upload to -security to check if it builds correctly everywhere ([[https://lists.debian.org/debian-release/2023/03/msg00151.html|summary]]) * (./) also do an upload of a package that needs signing * [ ] Coordinate with backports team to do a test upload to -backports to check if it builds correctly everywhere ([[https://lists.debian.org/msgid-search/11452f02-a71b-5acd-b38f-d9b4100e9c79@debian.org|email sent 2023-04-11]]) * [ ] also do an upload of a package that needs signing * [ ] this will probably need NEW processing by backports admins * [ ] Have DSA upgrade a non-critical machine ([[https://lists.debian.org/msgid-search/492a9245-7c38-073d-0ba7-fa48da5e1a12@debian.org|request]]) * [ ] Suggestions include: * [ ] Have DSA upgrade a buildd for each architecture ([[https://lists.debian.org/msgid-search/492a9245-7c38-073d-0ba7-fa48da5e1a12@debian.org|request]]) * [ ] 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 bookworm release ([[https://lists.debian.org/debian-services-admin/2023/04/msg00000.html|e-mail]]) * [ ] 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@ <> * (./) Ensure that www/testing/freeze-and-release-dates.yaml is up-to-date == 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 * (./) Make sure that reportbug contains the right stable to suite name tables. See: https://salsa.debian.org/reportbug-team/reportbug/-/commit/0bf36604535e0c4bf8c39a27d0d3901095ea57ae for details. (DebianBug:1034260) * [ ] ReleaseNotes need to be updated: * (./) Check with [[Teams/DebianKernel|Linux kernel team]] for specials with the Kernel * [ ] 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 bookworm's d-i area) * (./) Check with [[Teams/Security|Security Team]] for lower supported packages * (./) Install & upgrade tests should reveal no undocumented (release notes, install guide) surprises * (./) Coordinate a release date at least 3 weeks before - involved teams/roles: ([[https://lists.debian.org/debian-release/2023/04/msg00977.html|e-mail]]) * (./) 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 ([[https://lists.debian.org/debian-devel-announce/2023/04/msg00007.html|e-mail]]) * (./) 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. * (./) Ensure that www/freeze-and-release-dates.yaml is up-to-date * (./) Website: * (./) Have a patch ready for template/debian/release_info.wml to update ([[https://salsa.debian.org/webmaster-team/webwml/-/commit/f961a81|f961a81]]) * (./) 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 * (./) Decron trille for the week before the release to avoid daily emails with the same stale contents * (./) Prepare [[Teams/Publicity/Announcements|press release]] (done by Publicity Team) * [ ] 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 copied to trixie * (./) new win32-loader? * [ ] cleanup of bookworm-proposed-updates and bookworm-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/bookworm/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 * (./) 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 bookworm) * (./) Ask publicity team to publish Release Announcement in website news area * (./) Ask www team to force website update * (./) Check after the website update to make sure that it refers to bookworm in [[http://www.debian.org/releases/|release pages]] * [ ] Update Wiki: * [ ] Update these wiki pages (coordinated with ReleaseNotes's editor): (./) FrontPage (./) DebianReleases (./) ReleaseRecertification StableUpdates StableProposedUpdates [[Backports]] [[Welcome/Users]] [[Glossary]] [[DebianBookworm]] [[DebianBullseye]] [[DebianTrixie]] ReleaseParty [[ReleasePartyBookworm]] [[DebianArt/Themes]] [[DebianDesktop/Artwork]] [[DebianDesktop/Artwork/Trixie]] [[Teams/DebianCD/ReleaseTesting]] [[Teams/Dpkg/FAQ]] SourcesList * [ ] Ping the wiki team to run /srv/wiki.debian.org/bin/get-debian-suite-info early (cron runs @daily) * (./) Watch mailing-lists for abnormalities * (./) Backup/flush hint files. * (./) Update release.debian.org/{oldoldstable,oldstable,stable,testing} symlinks; create trixie for testing as a copy of bookworm and edit == After the release == * (./) Notify Distrowatch; send a mail to distro@distrowatch.com * (./) Notify [[https://lwn.net/op/FAQ.lwn#contact|LWN]] * [ ] Notify [[http://slashdot.org/submission|slashdot]], [[https://news.ycombinator.com/|Hacker News]], [[http://www.reddit.com/r/debian|Reddit]], [[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 * (./) 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/ * [ ] Notify the web team that they should ping [[https://www.debian.org/users/|Debian users]] after a few months to check if they are still using Debian and to update their testimonials * (./) Add a tag for trixie to all bugs tagged 'sid' * (./) Remove -ignore tags from bugs in bookworm that are candidates for fixing in point releases * (./) Check with udd maintainers that the hardcoded values are updated (see [[SuitesAndReposExtension#udd]]) * [ ] Check with buildd team that buildds know about trixie. (see [[SuitesAndReposExtension#wanna-build]]) * [ ] Check with other service/package maintainers that all the other [[SuitesAndReposExtension#Existing_hardcoding|hardcoded]] suite names or codenames are updated == 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 other data sources give information about trixie * (./) Ensure dinstall run smoothly * (./) Ensure trille is cron-ed if it was disabled for the week before the release * [ ] ...