This page is the canonical tracking document for the upcoming Groovy Gorilla release. It’s a live document. The Ubuntu release team will be updating it as we work on releasing 20.10.
Status
20.10 is released!
Summary
proposed-migration block in place
We’re DONE!
Current blockers
LP: #1899519 - booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded (need respin)
LP: #1898038 - docker-support/multipass-support broken with system apparmor3 (20.10)
Try to get release name earlier, so we can open the new series in order to be able to clear out -proposed to make proposed-migration runs go faster.
The mirror prober’s output dropped off a cliff after we published - as expected - but took a long time to recover. Is there a way we can make this more efficient? It blocks publishing of the website. (It’d run faster if if the .manifest only had the current series.)
Release checklist
The following list is strictly for ubuntu-release team members, based on the ReleaseProcess document.
Legend:
- Task assigned and worked on
- Task finished
- Task skipped or failed
XXX - Task contents added or modified during this release
Release minus 14 days:
[sil2100] NonLanguagePackTranslationDeadline , ensure uploads with updated translations downloaded from Rosetta are done for:
– ubiquity (debian-installer)
– ubiquity-slideshow-ubuntu
– gfxboot-theme-ubuntu
– yelp, gnome-user-docs and ubuntu-docs
– DDTP data (package description translations)
[sil2100] Notify Language Translation Lead (GunnarHj) and the current langpack-o-matic maintainer (sil2100) to coordinate a fresh set of language packs which will be exported, uploaded, and built in time for the release.
[bdmurray] If the new release is an LTS, make sure that hwe-support-status (located in update-manager) is up to date with the current HWE stack info, dates and versions.
Release minus 10 days:
If any image names have changed since the previous cycle, notify the web team (#web-team on canonical; email: webteam@canonical.com) to check the website downloader code. Ask the web team to review Release Manifest.
Start off release notes and announce framework. Call for ubuntu-docs and other team participation in content creation of overview and documentation of release bugs.
Release minus 7 days (release candidate week):
Selectively accept package uploads to resolve targeted bugs
[sil2100] Review list of full iso image names and plans with web team (#web-team on canonical; email: webteam@canonical.com)
[bdmurray] Disable apport and kerneloops uploads to Launchpad (‘problem_types’: [‘Bug’, ‘Package’], in /etc/apport/crashdb.conf)
– You can reach out to BrianMurray if in doubt.
Prepare the release announcement
– Notify Flavor Product Managers (Kubuntu, Xubuntu, Lubuntu, Ubuntu Studio, Ubuntu MATE, Ubuntu Budgie, Ubuntu Kylin) to prepare separate release announcements and review/update Release Notes.
– this should refer to the web page prepared by the teams rather than going into details of changes itself
– update the page to include any caveats
Review targeted bugs and take final decisions on what to fix and what to defer
Apply a “block-all source” hint to proposed-migration; any further changes to -proposed not intended for SRU will need to be unblocked manually XXX this should be in release day, and in “minus 3” there should be a reference to generate-freeze-block instead
Release minus 1 day:
[sil2100] Pre-publish the CD images: ./publish-image-set --prepublish will print the necessary commands.
Copy .manifest to .manifest.full, and prune all images from previous releases from the .manifest file to allow timely mirror probing
Run sync-mirrors on ancientminister to push out the pre-published file structure.
Begin running the mirror prober hourly on staging.ubuntu.com to monitor the propagation of the images to mirrors
Review on the staging server the feature walk through on the website (web-team)
Build and wait for the source images ( cron.source ) to be published by the publisher script.
Ping CPC using cpc-help keyword in #ubuntu-release to update on current status to see if CPC can start staging cloud images ready for publication.
Release minus 6 hours:
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.
Disable sync-mirrors on ancientminister, best by adding an early exit to the sync-mirrors command.
Ask #is to disable rsyncd on ancientminister so images don’t get published early
: 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 drop the mention of “Release Candidate”, since neither publish-release nor publish-image-set is yet smart enough to do the right thing there.
Notify the vanguard in #IS that images are ready to be pushed to s3 to be ready for CloudFront:
– find /srv/cdimage.ubuntu.com/www -name \*20.04\*iso -o -name \*20.04\*xz -o -name \*20.04\*gz | grep -v torrent
Once the s3 copy is done, re-enable sync-mirrors (by removing the temporary early exit) and ask #is to re-enable rsyncd on ancientminister
XXX Re-enable rsync and sync-mirrors. Run sync-mirrors manually to push out the updated images to cdimage & releases
Ping CPC using cpc-help keyword in #ubuntu-release to start the process of building and publishing cloud images.
Copy .manifest to .manifest.full again, pruning all images from previous releases from the .manifest file to allow timely mirror probing
Ask the #is vanguard to run the mirror prober continuously to verify which mirrors are up to date; output visible here. Take a note of how many mirrors were there before this started.
Check torrents for proper functionality.
Confirm that website content is finalized, as further edits will be difficult under load and check with sysadmin that caches will be cleared on time (web-team, IS, release-team).
Check the mirror prober loop has resulted in at least 60% of the mirrors being restored, so the website can spread the load amongst more mirrors. This list is baked into the Ubuntu website at build time, so notify the web team to (re)build the site.
Ask a Launchpad engineer to check that we haven’t lost the race on Contents file generation ; Contents generation takes on the order of two hours plus a publisher run, so give it at least that much headroom.
Release minus 1 hour:
Coordinate with web team for publishing of staging.
Coordinate with PR team (Sian Aherne) to inform media who are waiting for launch to post their articles.
Release:
Update the topic on #ubuntu-devel, #canonical, and #ubuntu-release-party and make announcement in #ubuntu-release-announce, and then in #ubuntu-release-party.
Update the appropriate meta-release files (including raspi/os_list_imagingutility_ubuntu.json) in the bzr branch. Then a member of the changelogs group (BrianMurray, laney, sil2100) updates the meta-release bzr branch on rubay /srv/changelogs.ubuntu.com/meta-release and copies updated files to /srv/changelogs.ubuntu.com/www .
Switch the development release from its codename to its version in errors/templates/bucket.html in errors
Notify web team to announce on the website
Send the release announcement to ubuntu-announce.
Notify a Launchpad admin to set the status of this distrorelease to CURRENT, and to change any previous CURRENT distrorelease(s) to SUPPORTED.
Update Relevant community documentation with references to this new release
– https://help.ubuntu.com/community/ReportingBugs1 Review through the process pages, and update to the release name (e.g. oneiric->precise)
- Task assigned and worked on
- Task finished
- Task skipped or failed