Ubuntu Wiki

These are things that needed to be checked for any release (preview, release candidate, and final) by the release manager:

Before building candidates

• replace references to code names with references to the formal version number. See CodeNamesToVersionNumbers for relevant places

• Ensure all pre-release markers are removed from artwork
• Ensure that release notes are updated in ubuntu-docs
• change the description in dists/xxx/Release (possibly not needed now, could be superseded by Launchpad?)
• check the volume labels on ISO's for all architectures (cdimage/debian-cd/CONF.sh, OFFICIAL variable)
• check CD boot loader help text against menu configuration

• ensure that cd release-upgrader is set to ""useDevelopmentRelease=False" (https://launchpad.net/ubuntu/+source/update-manager/+bug/99171) [mvo]

• ask MartinPitt to disable apport via update-notifier (for RC)

• check the lsb-release output for accuracy
• check /etc/issue and /etc/issue.net for accuracy
• check standard /etc/apt/sources.list for accuracy and ensure all suites exist
• ensure that the "about ubuntu" documents refer to the correct version, if at all
• ensure the debsearch firefox plugin searchs in the right package repository.
• make sure Contents files are up-to-date and hassle the Soyuz team if not
• prepare release announcement
  • make sure the announcement has links to all derivatives being released

Once final image is ready

• push isos to mirror pool and verify that all servers (releases, archive, cdimage) have the images

Before announcement

• push links to mirrors and verify

  • check that http://releases.ubuntu.com/ has the proper links and text

• check torrent functionality

Announcement

• Email ubuntu-announce

• Modify meta-release file to notify users of the availability of the new release

• make sure that the upgrade tool has the proper release notes (or link to them)

• Replace upgrade instructions with simplified version (update-manager no longer requires -d option)