ReleaseCandidateProcess
5826
Comment: website then announcement (from ReleaseProcess)
|
← Revision 42 as of 2020-10-21 18:50:56 ⇥
6094
|
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 the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]] |
Line 10: | Line 10: |
1. Prepare the release announcement and formal $RELEASE/ReleaseNotes * Notify leads for Kubuntu, Edubuntu, Xubuntu, Ubuntu-Studio, Lubuntu, Mythbuntu inputs * 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 * update the page to include any caveats * request that contributors to Release Notes provide links to upstream project web pages and change logs in their entries, where appropriate. * notify loco teams to translate release notes (coordinate with Matthew Nuzum; URLs should be https://wiki.ubuntu.com/<releasenotepath>/<lang> for all languages) * obtain up-to-date list of triggered release mirrors from Canonical sysadmin * Notify `ubuntu-doc@lists.ubuntu.com` to proofread the announcement and suggest changes, CC product owners (from ReleaseManifest) and Marketing. |
|
Line 13: | Line 21: |
1. Notify developers by mailing [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce ubuntu-devel-announce]: | 1. Notify developers by mailing [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce|ubuntu-devel-announce]]: |
Line 16: | Line 24: |
* Reminder for integrating all translations listed in NonLanguagePackTranslationDeadline to packages. DavidPlanella can help with exporting the translations from Launchpad to facilitate the work. | |
Line 22: | Line 31: |
1. Merge seeds and update metapackages for all derivatives | 1. Update metapackages for all derivatives |
Line 24: | Line 33: |
1. Notify Scott James Remnant to perform a ReadaheadListUpdate 1. Get new WinFOSS from Henrik Omma |
|
Line 30: | Line 37: |
RC minus 7 days: | RC minus 7 days (Final Freeze): |
Line 35: | Line 42: |
* Clear the [http://people.ubuntu.com/~ubuntu-archive/NBS NBS] list. 1. Announce the 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. |
* Clear the [[http://people.ubuntu.com/~ubuntu-archive/NBS|NBS]] list. 1. Announce the 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. |
Line 47: | Line 54: |
1. Modify `debian-cd/CONF.sh` to set `OFFICIAL="Release Candidate"` | 1. Modify `debian-cd/CONF.sh` to set `OFFICIAL="Release Candidate"` (Edit from bzr co bzr+ssh://nusakan.canonical.com/srv/cdimage.ubuntu.com/bzr/debian-cd/ and pull from /srv/cdimage.ubuntu.com/debian-cd on nusakan) 1. Ensure that the ISO tracker lists the new milestone, marked as "automatically publish" |
Line 50: | Line 58: |
1. Notify Henrik Omma to begin ReleaseValidationProcess 1. Notify Marc Tardif and ask for re-certification on test hardware |
1. Notify QA team (Jean-Baptiste Lallement) to begin ReleaseValidationProcess 1. Notify Cert team (Ara Pulido) and ask for re-certification on test hardware |
Line 53: | Line 61: |
1. Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone. Please cc matthew.nuzum@canonical.com and gerry.carr@canonical.com 1. Notify Matthew Nuzum to ensure that the release notes redirection table on `http://www.ubuntu.com/products/GetUbuntu/ReleaseNotes` is up to date 1. Notify Adam Conrad to prepare buildds for opening `-updates` and `-security` |
1. Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone. 1. Notify web team (ellen.arnold@canonical.com, IRC: ellen) to ensure that the release notes redirection table on `http://www.ubuntu.com/getubuntu/releasenotes` is up to date |
Line 59: | Line 66: |
1. Receive certification test results from Marc Tardif 1. Prepare the release announcement * Notify Jonathan Riddell, Oliver Grawert for Kubuntu and Edubuntu inputs * 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 doc team rather than going into details of changes itself * update the page to include any caveats * notify loco teams to translate release notes (coordinate new translation URLs with Matthew Nuzum) * obtain up-to-date list of triggered release mirrors from Canonical sysadmin * Notify Matt Zimmerman, `ubuntu-doc@lists.ubuntu.com` to proofread the announcement and suggest changes |
1. Receive certification test results from Ara Pulido |
Line 69: | Line 68: |
1. Open `-updates` and `-security` 1. Pre-publish ISOs (for CDs only). This is typically done with: * {{{for-project kubuntu publish-release daily 20061019 alternate poolonly rc}}} Server is a bit different and requires something like: * {{{ARCHES="i386 amd64 sparc" for-project ubuntu publish-release daily ../ubuntu-server/daily/20061017.1 server poolonly rc}}} |
|
Line 76: | Line 69: |
1. If requested by the sysadmin team, ask Colin Watson to remove the beta release from releases.ubuntu.com and torrent.ubuntu.com, by moving all `*-beta-*` in .pool directories under `/srv/cdimage.ubuntu.com/www/simple` to directories under `~cjwatson/old-images/`, removing the symlinks from other directories under `/srv/cdimage.ubuntu.com/www/simple`, editing corresponding `MD5SUMS` files, and removing all `*-beta-*` from directories under `/srv/cdimage.ubuntu.com/www/torrent`. Note that this will leave releases.ubuntu.com without any visible images for this release for a short while. | Night before release: 1. Pre-publish ISOs (for CDs only): `./publish-image-set --prepublish` (from [[https://code.launchpad.net/+branch/ubuntu-archive-tools|lp:ubuntu-archive-tools]]) will print the necessary commands. |
Line 80: | Line 75: |
1. Publish the CD images. This usually requires mangling the `.htaccess` and the `HEADER.html` in the directory where the images are stored to say "Release Candidate" instead of "Beta", since publish-release isn't smart enough to do the right thing there | 1. Copy the beta release from releases.ubuntu.com, by moving all `*-beta-*` in .pool directories under `/srv/cdimage.ubuntu.com/www/simple` to directories under `/srv/cdimage.ubuntu.com/old-images/`. If requested by IS, also remove these files after archival; note that this will leave releases.ubuntu.com without any visible images for this release for a short while. 1. Publish the CD images: `./publish-image-set` will print the necessary commands. * You need to edit `cdimage/www/simple/HEADER.html` and `cdimage/www/simple/.htaccess` by hand to change "Beta" to "Release Candidate", since neither publish-release nor publish-image-set is yet smart enough to do the right thing there. 1. Copy .manifest to .manifest.full, pruning all images from previous releases from the .manifest file to allow timely mirror probing. |
Line 88: | Line 86: |
1. Notify Matthew Nuzum to put the announcement on the website | 1. Notify the web team (ellen.arnold@canonical.com, IRC: ellen) to put the announcement on the website |
Line 92: | Line 90: |
1. Post announcement to [http://www.ubuntuforums.org/forumdisplay.php?f=13 News & Announcements section] (Matt Zimmerman and forum admins have posting rights) | 1. Post an announcement on http://release-blog.ubuntu.com/ 1. Post announcement to Launchpad (ubuntu-drivers members have posting rights) |
Line 98: | Line 97: |
---- CategoryProcess |
To be carried out by the Ubuntu release team
Goals:
- Produce a comprehensive, thoroughly tested release intended for final publication
- Execute a complete functional test of the release process in preparation for the final release
RC minus 14 days:
Notify kernel team of KernelFreeze
- Prepare the release announcement and formal $RELEASE/ReleaseNotes
- Notify leads for Kubuntu, Edubuntu, Xubuntu, Ubuntu-Studio, Lubuntu, Mythbuntu inputs
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
- update the page to include any caveats
- request that contributors to Release Notes provide links to upstream project web pages and change logs in their entries, where appropriate.
notify loco teams to translate release notes (coordinate with Matthew Nuzum; URLs should be https://wiki.ubuntu.com/<releasenotepath>/<lang> for all languages)
- obtain up-to-date list of triggered release mirrors from Canonical sysadmin
Notify ubuntu-doc@lists.ubuntu.com to proofread the announcement and suggest changes, CC product owners (from ReleaseManifest) and Marketing.
RC minus 10 days:
Notify developers by mailing ubuntu-devel-announce:
- Pointer to milestone page
- Reminder of freeze
Reminder for integrating all translations listed in NonLanguagePackTranslationDeadline to packages. DavidPlanella can help with exporting the translations from Launchpad to facilitate the work.
- Target any relevant bugs to the milestone
- Review problems and file targeted bugs for those which need resolution for the release candidate:
- Live filesystem build failures
- Upgrade failures
- Oversized ISOs
- Update metapackages for all derivatives
Notify Michael Vogt to perform a GnomeAppInstallDesktopDatabaseUpdate
- Notify James Troup to remind mirrors to check free disk space
- Include estimate of disk space requirements for pre-publishing the release candidate
Begin UpgradeTestingProcess
RC minus 7 days (Final Freeze):
- All CD-related problems should be resolved
- Live filesystem build failures
Clear the NBS list.
Announce the freeze on the #ubuntu-devel topic and 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 for the release:
- Installation bugs
- Upgrade bugs
- High-severity bugs
- Selectively accept package uploads to resolve targeted bugs
RC minus 3 days:
- Stop all live filesystem and cdimage cron jobs
Modify debian-cd/CONF.sh to set OFFICIAL="Release Candidate" (Edit from bzr co bzr+ssh://nusakan.canonical.com/srv/cdimage.ubuntu.com/bzr/debian-cd/ and pull from /srv/cdimage.ubuntu.com/debian-cd on nusakan)
- Ensure that the ISO tracker lists the new milestone, marked as "automatically publish"
Go through ReleaseChecklist
- Produce a full set of images
Notify QA team (Jean-Baptiste Lallement) to begin ReleaseValidationProcess
- Notify Cert team (Ara Pulido) and ask for re-certification on test hardware
- Iteratively test and accept select showstopper fixes
Ask the marketing team (ubuntu-marketing@lists.ubuntu.com) to prepare a web page about the changes since the last milestone.
Notify web team (ellen.arnold@canonical.com, IRC: ellen) to ensure that the release notes redirection table on http://www.ubuntu.com/getubuntu/releasenotes is up to date
RC minus 2 days:
- Receive certification test results from Ara Pulido
- Review targeted bugs and take final decisions on what to fix and what to defer
Night before release:
Pre-publish ISOs (for CDs only): ./publish-image-set --prepublish (from lp:ubuntu-archive-tools) will print the necessary commands.
RC minus 15 minutes:
Copy the beta release from releases.ubuntu.com, by moving all *-beta-* in .pool directories under /srv/cdimage.ubuntu.com/www/simple to directories under /srv/cdimage.ubuntu.com/old-images/. If requested by IS, also remove these files after archival; note that this will leave releases.ubuntu.com without any visible images for this release for a short while.
Publish the CD images: ./publish-image-set will print the necessary commands.
You need to edit cdimage/www/simple/HEADER.html and cdimage/www/simple/.htaccess by hand to change "Beta" to "Release Candidate", since neither publish-release nor publish-image-set is yet smart enough to do the right thing there.
- Copy .manifest to .manifest.full, pruning all images from previous releases from the .manifest file to allow timely mirror probing.
- Remove any not-yet-official warnings from the announcement and release notes
- Verify that all mirrors listed in the announcement or release notes have images, and remove faulty mirrors
- Check torrents for proper functionality
RC release:
Update the topic on #ubuntu-devel
Notify the web team (ellen.arnold@canonical.com, IRC: ellen) to put the announcement on the website
- News sidebar
/testing
Send the release announcement to ubuntu-announce
Post an announcement on http://release-blog.ubuntu.com/
- Post announcement to Launchpad (ubuntu-drivers members have posting rights)
RC plus 1 day:
Continue on ReleaseProcess
If any changes were made to this document in this run, check whether the changes also apply to MilestoneProcess, BetaProcess or ReleaseProcess.
ReleaseCandidateProcess (last edited 2020-10-21 18:50:56 by brian-murray)