MilestoneProcess
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:
- 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.
- 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)
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
- Merge seeds and update metapackages for all releasing derivatives
Notify Michael Vogt to perform a GnomeAppInstallDesktopDatabaseUpdate
Discuss with Desktop team and MartinPitt whether or not to re-enable apport by default.
Release minus 2 days:
Announce the milestone freeze on the #ubuntu-release topic, #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.
If a hard freeze is in use, set the distrorelease status to FROZEN in Launchpad
- Coordinate with cloud image builds (Ben Howard, IRC: utlemming) to check for issues.
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.
- Review problems and file targeted bugs for those which need resolution before builds can begin:
- Live filesystem build failures
NBS list
- Selectively accept package uploads to resolve targeted bugs
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 Launchpad, and scream loudly.
check with QA on UpgradeTestingProcess results (auto test) and manual smoke tests, since the archive is now consistent
Notify commercial engineering (email: david.murphy@canonical.com AND cc: ce-infrastructure@lists.canonical.com; IRC: schwuk) that the archive is in a consistent state
- Ensure that the ISO tracker lists the new milestone
Edit default_milestone in ~cdimage/.isotracker.conf to match the new milestone name in the ISO tracker
- Stop all live filesystem and cdimage cron jobs
- Produce full set of images
Iterate ReleaseValidationProcess and fix showstopper bugs
Release minus 1 day:
- Fix any blocker bugs that have come up during testing
- Coordinate with QA and other team leads to make sure blockers visible
- Resolve any remaining targeted blocker bugs with development teams
- Produce final set of images (if needed)
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
- 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:
- Start the image publishing off
- 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.
Publish the milestone CD images: ./publish-image-set.py (from lp:ubuntu-archive-tools) will print the necessary commands.
Publish the milestone Cloud images on cloud-images.ubuntu.com. (ping IRC: utlemming)
- Verify that all mirrors listed in the announcement or release notes have images
- Check functionality of torrents
- Once it's clear we won't pick up and test any last respins
Notify Hardware Certification team (email: hardware-certification@canonical.com, IRC: ara) to begin CertificationTestingProcess (private due to agreements with vendors)
Confirm that UpgradeTestingProcess is complete before unfreezing archive
If a hard freeze was in use, set the distrorelease back to DEVELOPMENT in Launchpad.
Clear out any pending entries in the UNAPPROVED queue
- Update topic on #ubuntu-devel that archive is unfrozen.
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
- verify that the links in the announce and release notes work, and its picking up the new images
- Announce the milestone is available
Send the release announcement to ubuntu-devel-announce
Update the topic on #ubuntu-devel and #ubuntu-release to indicate milestone is available.
Post an announcement on http://release-blog.ubuntu.com/
- Switch from publishing images for the milestone back to publishing the dailies
- Update the ISO tracker to set the milestone to "released", re-enable the "daily", and update the notice.
Update the build machine, to change default_milestone in ~cdimage/.isotracker.conf back to "Precise Daily" (etc.), and to turn live filesystems and cdimage cron jobs back on.
- Clean up milestone status on Launchpad
mark the old milestone inactive in Launchpad (https://launchpad.net/ubuntu/RELEASE)
- work through any old milestoned bugs still remaining, and move to next milestone if appropriate.
Release manager update the burndown chart links on ReleaseTeam/FeatureStatus
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:
In planning cycle, review Release Manifest and make any necessary updates.