MilestoneProcess

Differences between revisions 9 and 37 (spanning 28 versions)
⇤ ← Revision 9 as of 2008-08-06 16:37:23 →
Size: 4286
Editor: localhost
Comment: converted to 1.6 markup
← Revision 37 as of 2011-02-09 18:23:14 → ⇥
Size: 5489
Editor: 99-191-111-134
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
To be carried out by: Steve Langasek, with support from the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]] To be carried out by: Ubuntu Release Manager, with support from the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]]
Line 10: Line 10:
  * Please notify matthew.nuzum@canonical.com that there will be impending website changes   * Please notify web team (email: richard.lee@canonical.com, IRC: rhlee) that there will be impending website changes
  * Review list of full iso image names and sizing with Richard Lee
Line 12: Line 13:
  * Pointer to milestone page   * Pointer to milestone release notes page
Line 22: Line 23:
 1. Announce the milestone freeze on the `#ubuntu-devel` topic and [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce|ubuntu-devel-announce]]. There is generally no need to tell people to hold off on uploads, as they will be held automatically by Soyuz once the next task is performed.
 1. Set the distrorelease status to `FROZEN` in Launchpad		  1. Announce the milestone freeze on the `#ubuntu-devel` topic, [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce|ubuntu-devel-announce]], and [[https://release-blog.ubuntu.com/wp-admin/edit.php|http://release-blog.ubuntu.com/]]. There is generally no need to tell people to hold off on uploads, as they will be held automatically by Soyuz once the next task is performed.
 1. As first image becomes available, mail out to ubuntu-devel@lists.ubuntu.com and ubuntu-bugsquad@lists.ubuntu.com to announce that ISO images are ready for testing, and refer people to the ISO tracker.
 1. If a hard freeze is in use, set the distrorelease status to `FROZEN` in Launchpad
Line 29: Line 31:
 1. Ensure that you accept at least one package through the [[https://edge.launchpad.net/ubuntu/hardy/+queue?batch=500|Launchpad UI]], to ensure that launchpad has not broken (important for non-Canonical members of the release team). If it has, please file a bug on [[https://bugs.launchpad.net/soyuz/+bugs|Soyuz]], and scream loudly.  1. Ensure that you accept at least one package through the [[https://launchpad.net/ubuntu/natty/+queue?batch=300&queue_state=1|Launchpad UI]], to ensure that launchpad has not broken (important for non-Canonical members of the release team). If it has, please file a bug on [[https://bugs.launchpad.net/soyuz/+bugs|Soyuz]], and scream loudly.
Line 46: Line 48:
 1. Publish the milestone CD images. This usually requires mangling the `.htaccess` and the `HEADER.html` in the directory where the images are stored, since publish-release isn't smart enough to do the right thing there
 1. Notify Henrik Omma and Marc Tardif to begin [[https://wiki.canonical.com/CertificationTestingProcess|CertificationTestingProcess]] (private due to agreements with vendors)		  1. Publish the milestone CD images: `./publish-image-set.py` (from [[https://code.launchpad.net/+branch/ubuntu-archive-tools|lp:ubuntu-archive-tools]]) will print the necessary commands.
 1. [[https://wiki.ubuntu.com/UEC/Images/Publishing|Publish the milestone UEC images]] on uec-images.ubuntu.com.
 1. Notify Hardware Certification team ( email: Ara.Pulido@canonical.com, IRC: ara ) to begin [[https://wiki.canonical.com/CertificationTestingProcess|CertificationTestingProcess]] (private due to agreements with vendors)
Line 50: Line 53:
 1. Notify web site team (e: Richard.Lee@canonical.com, IRC: rhlee) to update to new images and notes.
  * `/testing` on the website with release notes
  * alphas are served off of cdimage, betas and others use `/testing/download
Line 51: Line 57:
 1. Notify Matthew Nuzum to update the website and the `/products/GetUbuntu/ReleaseNotes` redirection
  * `/testing`
Line 54: Line 58:
 1. Set the distrorelease back to `DEVELOPMENT` in Launchpad  1. If a hard freeze was in use, set the distrorelease back to `DEVELOPMENT` in Launchpad
Line 56: Line 60:
 1. Post an announcement on [[https://release-blog.ubuntu.com/wp-admin/edit.php|http://release-blog.ubuntu.com/]]
Line 58: Line 63:
 1. Create new milestone in Launchpad for the next milestone  1. Release manager to mark the old milestone inactive in Launchpad (https://launchpad.net/ubuntu/RELEASE)
 1. Release manager to work through any old milestoned bugs still remaining, and move to next milestone if appropriate.
 1. Release manager update the burndown chart links on ReleaseTeam/FeatureStatus
Line 60: Line 67:

Release plus 7 days:
 1. In planning cycle, review [[https://wiki.ubuntu.com/ReleaseManifest|Release Manifest]] and make any necessary updates.
Line 63: Line 74:
 * Warn the QA team (ubuntu-bugsquad@lists.ubuntu.com) ----
CategoryProcess

To be carried out by: Ubuntu Release Manager, with support from the Ubuntu release team

Goals:

  • Produce a set of distribution media images suitable for testing by advanced users and hardware recertification
  • Make the archive consistent so that upgrade testing can be performed

Release minus 6 days:

  1. Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone

    • Please notify web team (email: richard.lee@canonical.com, IRC: rhlee) that there will be impending website changes

    • Review list of full iso image names and sizing with Richard Lee

  2. Notify developers by mailing ubuntu-devel-announce:

    • Pointer to milestone release notes page
    • Reminder of milestone freeze

    • Request to avoid and eliminate PackageInconsistencies

    • Target any relevant bugs to the milestone
  3. Merge seeds and update metapackages for all releasing derivatives

  4. Notify Michael Vogt to perform a GnomeAppInstallDesktopDatabaseUpdate

  5. Discuss with Desktop team and MartinPitt whether or not to re-enable apport by default.

Release minus 2 days:

  1. Announce the milestone freeze on the #ubuntu-devel topic, ubuntu-devel-announce, and http://release-blog.ubuntu.com/. There is generally no need to tell people to hold off on uploads, as they will be held automatically by Soyuz once the next task is performed.

  2. As first image becomes available, mail out to ubuntu-devel@lists.ubuntu.com and ubuntu-bugsquad@lists.ubuntu.com to announce that ISO images are ready for testing, and refer people to the ISO tracker.

  3. If a hard freeze is in use, set the distrorelease status to FROZEN in Launchpad

  4. Review problems and file targeted bugs for those which need resolution before builds can begin:
  5. Selectively accept package uploads to resolve targeted bugs

  6. Ensure that you accept at least one package through the Launchpad UI, to ensure that launchpad has not broken (important for non-Canonical members of the release team). If it has, please file a bug on Soyuz, and scream loudly.

Release minus 1 day:

  1. Resolve any remaining targeted bugs

  2. Begin UpgradeTestingProcess, since the archive is now consistent

  3. Stop all live filesystem and cdimage cron jobs
  4. Produce full set of images

  5. Iterate ReleaseValidationProcess and fix showstopper bugs

  6. Prepare the release announcement

    • Review -changes mailing list since the last milestone to make sure that all relevant major changes have been documented in the milestone's web page

    • this should refer to the web page prepared by the marketing team rather than going into details of changes itself
    • update the page to include any caveats

Release:

  1. If there is a previous milestone for this series, move those images from /srv/cdimage.ubuntu.com/www/full to /srv/cdimage.ubuntu.com/old-images/, and notify the sysadmin team that these are available for off-line archival.

  2. Publish the milestone CD images: ./publish-image-set.py (from lp:ubuntu-archive-tools) will print the necessary commands.

  3. Publish the milestone UEC images on uec-images.ubuntu.com.

  4. Notify Hardware Certification team ( email: Ara.Pulido@canonical.com, IRC: ara ) to begin CertificationTestingProcess (private due to agreements with vendors)

  5. Verify that all mirrors listed in the announcement or release notes have images
  6. Check functionality of torrents

  7. Notify web site team (e: Richard.Lee@canonical.com, IRC: rhlee) to update to new images and notes.

    • /testing on the website with release notes

    • alphas are served off of cdimage, betas and others use `/testing/download

  8. Send the release announcement to ubuntu-devel-announce

  9. Confirm that UpgradeTestingProcess is complete before unfreezing archive

  10. If a hard freeze was in use, set the distrorelease back to DEVELOPMENT in Launchpad

  11. Update the topic on #ubuntu-devel

  12. Post an announcement on http://release-blog.ubuntu.com/

  13. Clear out any pending entries in the UNAPPROVED queue

  14. Turn live filesystems and cdimage cron jobs back on.

  15. Release manager to mark the old milestone inactive in Launchpad (https://launchpad.net/ubuntu/RELEASE)

  16. Release manager to work through any old milestoned bugs still remaining, and move to next milestone if appropriate.

  17. Release manager update the burndown chart links on ReleaseTeam/FeatureStatus

  18. If any modifications to this process were made in this run, check whether they apply to BetaProcess and ReleaseProcess as well.

Release plus 7 days:

  1. In planning cycle, review Release Manifest and make any necessary updates.

Outstanding issues

CategoryProcess

MilestoneProcess (last edited 2020-11-16 18:01:38 by vorlon)