MilestoneProcess
To be carried out by: Steve Langasek, with support from the [https://launchpad.net/~ubuntu-release 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:
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
Notify developers by mailing [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce ubuntu-devel-announce]:
- Pointer to milestone 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-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.
Set the distrorelease status to FROZEN in Launchpad
- Review problems and file targeted bugs for those which need resolution before builds can begin:
- Live filesystem build failures
[http://people.ubuntu.com/~ubuntu-archive/NBS NBS] list
- Selectively accept package uploads to resolve targeted bugs
Release minus 1 day:
- Resolve any remaining targeted bugs
Begin UpgradeTestingProcess, since the archive is now consistent
- Stop all live filesystem and cdimage cron jobs
- Produce full set of images
Iterate ReleaseValidationProcess and fix showstopper bugs
- 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:
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
Notify Henrik Omma and Marc Tardif to begin [https://wiki.canonical.com/CertificationTestingProcess CertificationTestingProcess] (private due to agreements with vendors)
- Verify that all mirrors listed in the announcement or release notes have images
- Check functionality of torrents
Send the release announcement to ubuntu-devel-announce
Notify Matthew Nuzum to update the website and the /products/GetUbuntu/ReleaseNotes redirection
/testing
Confirm that UpgradeTestingProcess is complete before unfreezing archive
Set the distrorelease back to DEVELOPMENT in Launchpad
Update the topic on #ubuntu-devel
Clear out any pending entries in the UNAPPROVED queue
- Turn live filesystems and cdimage cron jobs back on.
- Create new milestone in Launchpad for the next milestone
If any modifications to this process were made in this run, check whether they apply to BetaProcess and ReleaseProcess as well.
Outstanding issues
Warn the QA team (ubuntu-bugsquad@lists.ubuntu.com)