MilestoneProcess

Differences between revisions 31 and 45 (spanning 14 versions)
⇤ ← Revision 31 as of 2010-12-10 20:27:42 →
Size: 4774
Editor: 99-191-111-134
Comment:
← Revision 45 as of 2011-11-30 15:57:02 → ⇥
Size: 6271
Editor: 99-191-111-134
Comment: Adjusting tasks around in timeline to when they are actually occuring. Add cross checks with QA.
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 1. Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone
  * Please notify matthew.nuzum@canonical.com that there will be impending website changes
  * Review list of full iso image names and sizing with Matthew Nuzum		  1. Start to prepare web page summarizing the changes since the last milestone
  * Set up template
  * Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) if they have input
  * Notify the technical leads and product managers/designates for their input.
 1. Coordinate with web team for contacts and plans during release day
  * Please notify web team (email: ellen.arnold@canonical.com, IRC:ellen) that there will be impending website changes
  * Review list of full iso image names and sizing with the web team (ellen.arnold@canonical.com, IRC ellen)
Line 13: Line 17:
  * Pointer to milestone page   * Pointer to milestone release notes page
Line 23: Line 27:
 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. Announce the milestone freeze on the `#ubuntu-devel` topic, [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce|ubuntu-devel-announce]]. If it is not a hard freeze, let people know to hold off on the uploads. When it is a hard freeze, they will be held automatically by Soyuz once the next task is performed.
Line 25: Line 29:
 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.
Line 28: Line 33:
  * [[http://people.ubuntu.com/~ubuntu-archive/NBS|NBS]] list   * [[http://people.ubuntu.com/~ubuntu-archive/nbs.html|NBS]] list
Line 30: Line 35:
 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.  1. Ensure that you accept at least one package through the [[https://launchpad.net/ubuntu/oneiric/+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.
 1. Begin UpgradeTestingProcess, since the archive is now consistent
 1. Ensure that the ISO tracker lists the new milestone
 1. Edit `default_milestone` in `~cdimage/.isotracker.conf` to match the new milestone name in the ISO tracker
 1. Stop all live filesystem and cdimage cron jobs
 1. Produce full set of images
 1. Iterate ReleaseValidationProcess and fix showstopper bugs
Line 34: Line 45:
 1. Coordinate with QA and other team leads to make sure no blocker bugs have come up during testing.
Line 35: Line 47:
 1. Begin UpgradeTestingProcess, since the archive is now consistent
 1. Stop all live filesystem and cdimage cron jobs
 1. Produce full set of images
 1. Iterate ReleaseValidationProcess and fix showstopper bugs		  1. Produce final set of images (if needed)
 1. Prepare the release web page content (TechnicalOverview)
   * review input from tech leads
   * add discovered bugs not going to be fixed from ISO testing
   * 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
Line 40: Line 53:
  * 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		    * this should refer to the summary web page prepared by the teams rather than going into details of changes itself
   * update the page to include any caveats
Line 48: Line 60:
 1. [[https://wiki.ubuntu.com/UEC/Images/Publishing|Publish the milestone UEC images]] on uec-images.ubuntu.com.
 1. Notify AraPulido to begin [[https://wiki.canonical.com/CertificationTestingProcess|CertificationTestingProcess]] (private due to agreements with vendors)		  1. [[https://wiki.ubuntu.com/UEC/Images/Publishing|Publish the milestone Cloud images]] on cloud-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 52: Line 64:
 1. Notify Matthew Nuzum to update `/testing` on the website  1. Notify web site team (email: ellen.arnold@canonical.com, IRC: ellen) 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 59: Line 73:
 1. Change `default_milestone` in `~cdimage/.isotracker.conf` back to "Precise Daily" (etc.)
Line 61: Line 76:
 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 62: Line 79:
 1. Update the burndown chart links on ReleaseTeam/FeatureStatus
Release plus 7 days:
 1. In planning cycle, review [[https://wiki.ubuntu.com/ReleaseManifest|Release Manifest]] and make any necessary updates.
Line 66: Line 86:
 * Warn the QA team (ubuntu-bugsquad@lists.ubuntu.com)

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. Start to prepare web page summarizing the changes since the last milestone
    • Set up template

    • Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) if they have input

    • Notify the technical leads and product managers/designates for their input.
  2. Coordinate with web team for contacts and plans during release day

  3. 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
  4. Merge seeds and update metapackages for all releasing derivatives

  5. Notify Michael Vogt to perform a GnomeAppInstallDesktopDatabaseUpdate

  6. 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. If it is not a hard freeze, let people know to hold off on the uploads. When it is a hard freeze, they will be held automatically by Soyuz once the next task is performed.

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

  3. 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.

  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.

  7. Begin UpgradeTestingProcess, since the archive is now consistent

  8. Ensure that the ISO tracker lists the new milestone

  9. Edit default_milestone in ~cdimage/.isotracker.conf to match the new milestone name in the ISO tracker

  10. Stop all live filesystem and cdimage cron jobs
  11. Produce full set of images

  12. Iterate ReleaseValidationProcess and fix showstopper bugs

Release minus 1 day:

  1. Coordinate with QA and other team leads to make sure no blocker bugs have come up during testing.
  2. Resolve any remaining targeted bugs
  3. Produce final set of images (if needed)

  4. Prepare the release web page content (TechnicalOverview)

    • review input from tech leads
    • add discovered bugs not going to be fixed from ISO testing

    • 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

  5. Prepare the release announcement
    • this should refer to the summary web page prepared by the teams 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 Cloud images on cloud-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 (email: ellen.arnold@canonical.com, IRC: ellen) 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. Change default_milestone in ~cdimage/.isotracker.conf back to "Precise Daily" (etc.)

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

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

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

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

  19. 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)