ReleaseChecklist

Differences between revisions 27 and 28
Revision 27 as of 2013-04-19 08:25:29
Size: 2048
Editor: 82-69-40-219
Comment: up-to-date Contents hasn't been a problem for years; no need to keep checking this
Revision 28 as of 2019-10-15 11:03:32
Size: 1889
Editor: sil2100
Comment: Clean some obsolete points, formatting fixes
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * replace references to code names with references to the formal version number. See CodeNamesToVersionNumbers for relevant places  * Replace references to code names with references to the formal version number. See CodeNamesToVersionNumbers for relevant places
Line 11: Line 11:
 * Ensure that release notes are updated in ubuntu-docs  * Check the volume labels on ISO's for all architectures (cdimage/debian-cd/CONF.sh, OFFICIAL variable)
Line 13: Line 13:
 * 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
Line 15: Line 15:
 * check CD boot loader help text against menu configuration  * Disable apport via update-notifier (for RC leaving errors.ubuntu.com working though)
Line 17: Line 17:
 * ask MartinPitt to disable apport via update-notifier (for RC leaving errors.ubuntu.com working though)  * Check the lsb_release output for accuracy
Line 19: Line 19:
 * check the lsb_release output for accuracy  * Check /etc/issue and /etc/issue.net for accuracy
Line 21: Line 21:
 * check /etc/issue and /etc/issue.net for accuracy  * Check standard /etc/apt/sources.list for accuracy and ensure all suites exist
Line 23: Line 23:
 * check standard /etc/apt/sources.list for accuracy and ensure all suites exist  * Cnsure that the "about ubuntu" documents refer to the correct version, if at all
Line 25: Line 25:
 * 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.

 * p
repare release announcement
  * make sure the announcement has links to all derivatives being released
 * Prepare release announcement
   * Make sure the announcement has links to all derivatives being released
Line 34: Line 30:
 * request IS refresh images prior to push out to CloudFront
 * push isos to mirror pool and verify that all servers (releases, archive, cdimage) have the images
 * Request IS refresh images prior to push out to CloudFront
 * Push isos to mirror pool and verify that all servers (releases, archive, cdimage) have the images
Line 40: Line 36:
 * push links to mirrors and verify
 * check that http://releases.ubuntu.com/ has the proper links and text
 * check torrent functionality
 * Push links to mirrors and verify
 * Check that http://releases.ubuntu.com/ has the proper links and text
 * Check torrent functionality
Line 48: Line 44:
 * make sure that the upgrade tool has the proper release notes (or link to them)  * Make sure that the upgrade tool has the proper release notes (or link to them)

These are things that needed to be checked for any release (preview, release candidate, and final) by the release team and product 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 pre-release markers are removed from ubuntu-docs
  • 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
  • Disable apport via update-notifier (for RC leaving errors.ubuntu.com working though)
  • 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
  • Cnsure that the "about ubuntu" documents refer to the correct version, if at all
  • Prepare release announcement
    • Make sure the announcement has links to all derivatives being released

Once final image is ready

  • Request IS refresh images prior to push out to CloudFront

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

Before announcement

  • Call round table with stakeholders for a go/no-go survey prior to announce email going out.
  • 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)

ReleaseChecklist (last edited 2020-04-17 08:29:10 by sil2100)