Differences between revisions 29 and 30
Revision 29 as of 2015-05-10 07:49:56
Size: 5261
Editor: PaulWise
Comment: hardcoding
Revision 30 as of 2015-05-19 01:12:36
Size: 5387
Editor: PaulWise
Comment: Built-Using
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
 * binNMU everything that has a Built-Using header and is using old versions to remove old source packages from the release.

<!> This is a RM's TODO list, which might not be authorative 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 ?control@bugs.debian.org:

user release.debian.org@packages.debian.org
usercategory codename-sort
  * Codename [tag=]
    + Blockers for Codename [codename-is-blocker]
    + Planned for removal [codename-will-remove]
    + Ignored for Codename [codename-can-defer]

Then, usertagged bugs will be listed on:


Useful references about this feature are:

Before a Release

  • binNMU everything that has a Built-Using header and is using old versions to remove old source packages from the release.
  • Theme (artwork) design should be finalised and decided
  • d-i should have (beta or even better rc) releases
  • Do at least one CD making dry run with the right installer, to ensure that everything fits properly.
  • Install Guide should be up-to-date
  • ReleaseNotes need to be updated:

    • Check with ?KernelTeam 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 $suite's d-i area)
    • Check with Security Team for lower supported packages

    • Coordinate with translators
  • Install & upgrade tests should reveal no undocumented (release notes, install guide) surprises

  • Coordinate date with the FTP-Team
    • Have an FTP-master ready/notified/available 3 weeks before the Release
  • Send the preparation mail.
    • Send a mail to the Press team
  • Notify the Security Team of an upcoming Release

  • Notify the ?PressTeam of an upcoming Release

  • Notify the 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 publicity team of an upcoming Release

  • Prepare ?PressAnnouncement

    • coordinate with d-i team for text for d-i changes
  • Prepare the wiki changes
  • Prepare the website changes
    • Ensure the planned release date is on debian.org/releases
    • Ensure that the following pages exist on debian.org/releases/<RELEASENAME>

      • 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/<RELEASENAME+1> 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)

    • Have a patch ready for template/debian/release_info.wml to update the current release. This is to be deployed during the release.

While the Release

  • Mention things that are happening on IRC so the publicity team can 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
  • 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
  • Notify debian-security@lists.debian.org as people tend to cry occassionally

  • Notify the Press Team, that Release is done (tell them when the Release will be pushed out)
  • Notify the Debian CD Team that the Release is done

  • Notify the DebianLive Team that the Release is done

  • Update the website
  • Update the wiki (coordinated with ReleaseNotes's editor)

  • 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