ReleaseChecklist

Differences between revisions 1 and 20 (spanning 19 versions)
Revision 1 as of 2005-05-28 20:30:06
Size: 1035
Editor: adsl-213-190-44-43
Comment: imported from the old wiki
Revision 20 as of 2008-08-06 16:34:39
Size: 2108
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= ReleaseChecklist = These are things that needed to be checked for any release (preview, release candidate, and final) by the release manager:
Line 3: Line 3:
These are things that needed to be checked for any release by the release manager: == Before building candidates ==
Line 5: Line 5:
 * change the description in dists/xxx/Release  * 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?)
Line 9: Line 15:
 * 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)
Line 11: Line 23:
 * check /etc/debian_version, /etc/issue, and /etc/issue.net for accuracy  * check /etc/issue and /etc/issue.net for accuracy
Line 13: Line 25:
 * check standard /etc/apt/sources.list for accuracy and ensure all suites exist
Line 14: Line 27:
== Release timeline: ==  * ensure that the "about ubuntu" documents refer to the correct version, if at all
Line 16: Line 29:
 * 7 days prior:  * ensure the debsearch firefox plugin searchs in the right package repository.
Line 18: Line 31:
  * release candidate release  * make sure Contents files are up-to-date and hassle the Soyuz team if not
Line 20: Line 33:
  * '''FINAL ARTWORK'''  * prepare release announcement
  * make sure the announcement has links to all derivatives being released
Line 22: Line 36:
  * draft release announcement == Once final image is ready ==
Line 24: Line 38:
 * 1 day before:  * push isos to mirror pool and verify that all servers (releases, archive, cdimage) have the images
Line 26: Line 40:
  * finalise release announcement == Before announcement ==
Line 28: Line 42:
  * get release announcement translated

  * finalise media announcement list (list of email addresses, and who is sending)

  * make sure candidate final iso is in pool dir on mirror-master

  * verify torrents are working

  * verify that all servers have the image internally (releases, archive, cdimage)

 * on publishing:
 * push links to mirrors and verify
Line 42: Line 45:
  * check final torrents  * 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)

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

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)