Merge ~paride/ubuntu-release-tools/+git/templates:snap-channel-opening-howto into ubuntu-release-tools:main

[Paride Legovini]

Add steps on how to verify that snap stable channels are open

Unmerged commits

4c75b1b... by Paride Legovini on 2022-05-31

Add steps on how to verify that snap stable channels are open

9f14f4b... by Łukasz Zemczak on 2022-05-31

new-cycle-opening: remove some outdated tasks.

a9f0bd5... by Łukasz Zemczak on 2022-05-31

final-release: remove one irrelevant task, add tasks to update the Releases wiki page.

ae75568... by Łukasz Zemczak on 2022-05-31

eol: only send warning to ubuntu-announce@

2088557... by Łukasz Zemczak on 2022-05-30

Reformat one item to make the yaml parser happy.

59e959c... by Brian Murray on 2022-05-18

add tasks regarding reviewing and cleaning release note'd known issues

105c5a7... by Brian Murray on 2022-05-13

Clarify that all autopkgtest test results should be deleted for the EoL release

765fcf1... by Łukasz Zemczak on 2022-05-13

Add an initial EOL jira template. This one might need some work, there's still a few outdated items that I didn't take a look at (like using our new archival tooling for image archival)

3bdeb4e... by Łukasz Zemczak on 2022-05-12

Add template for point-releases.

f8870d0... by Brian Murray on 2022-05-11

clarify which meta-release files need updating because somebody might have forgot one once.

diff --git a/announcements/final-release-lts b/announcements/final-release-lts
new file mode 100644
index 0000000..e7d3756
--- /dev/null
+++ b/announcements/final-release-lts
@@ -0,0 +1,99 @@
+Ubuntu <VERSION> LTS, codenamed “<FULL NAME>”, is here. This release
+continues Ubuntu's proud tradition of integrating the latest and
+greatest open source technologies into a high-quality, easy-to-use Linux
+distribution. The team has been hard at work through this cycle, together
+with the community and our partners, to introduce new features and fix bugs.
+
+<BRIEF>
+
+<UPDATE FLAVOR NAMES ACCORDINGLY>
+The newest Ubuntu Budgie, Kubuntu, Lubuntu, Ubuntu Kylin, Ubuntu MATE,
+UbuntuStudio, and Xubuntu are also being released today. More details
+can be found for these at their individual release notes under the
+Official Flavours section:
+
+   https://discourse.ubuntu.com/t/<LOWERCASE NAME>-release-notes/
+
+Maintenance updates will be provided for 5 years for Ubuntu Desktop,
+Ubuntu Server, Ubuntu Cloud and Ubuntu Core. All the remaining flavours
+will be supported for 3 years. Additional security support is available
+with ESM (Extended Security Maintenance).
+
+To get Ubuntu <VERSION> LTS
+-------------------
+
+In order to download Ubuntu <VERSION> LTS, visit:
+
+   https://ubuntu.com/download
+
+Users of Ubuntu <PREVIOUS VERSION> will soon be offered an automatic upgrade to <VERSION>.
+Users of <PREVIOUS LTS> LTS will be offered the automatic upgrade when <VERSION>.1
+LTS is released, which is scheduled for the 4th of August.
+For further information about upgrading, see:
+
+   https://ubuntu.com/download/desktop/upgrade
+
+As always, upgrades to the latest version of Ubuntu are entirely free of
+charge.
+
+We recommend that all users read the release notes, which document
+caveats, workarounds for known issues, as well as more in-depth
+information on the release itself. They are available at:
+
+   https://discourse.ubuntu.com/t/<LOWERCASE NAME>-release-notes/
+
+Find out what's new in this release with a graphical overview:
+
+   https://ubuntu.com/desktop
+   https://ubuntu.com/desktop/features
+
+If you have a question, or if you think you may have found a bug but
+aren't sure, you can try asking in any of the following places:
+
+   #ubuntu on irc.libera.chat
+   https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
+   https://ubuntuforums.org
+   https://askubuntu.com
+   https://discourse.ubuntu.com
+
+
+Help Shape Ubuntu
+-----------------
+
+If you would like to help shape Ubuntu, take a look at the list of ways
+you can participate at:
+
+   https://discourse.ubuntu.com/contribute
+
+
+About Ubuntu
+------------
+
+Ubuntu is a full-featured Linux distribution for desktops, laptops, IoT,
+cloud, and servers, with a fast and easy installation and regular
+releases. A tightly-integrated selection of excellent applications is
+included, and an incredible variety of add-on software is just a few
+clicks away.
+
+Professional services including support are available from Canonical and
+hundreds of other companies around the world. For more information about
+support, visit:
+
+   https://ubuntu.com/support
+
+
+More Information
+----------------
+
+You can learn more about Ubuntu and about this release on our website
+listed below:
+
+   https://ubuntu.com
+
+To sign up for future Ubuntu announcements, please subscribe to Ubuntu's
+very low volume announcement list at:
+
+   https://lists.ubuntu.com/mailman/listinfo/ubuntu-announce
+
+
+On behalf of the Ubuntu Release Team,
diff --git a/announcements/open-for-development b/announcements/open-for-development
new file mode 100644
index 0000000..87d0c9b
--- /dev/null
+++ b/announcements/open-for-development
@@ -0,0 +1,17 @@
+We're pleased to announce that <CODENAME> is now open for development.
+auto-sync has been enabled and will run soon. As usual, we expect a large
+influx of builds and autopkgtests in this initial period, which will cause
+delays. Please help fixing any breakage that occurs.
+
+The release schedule can be found at
+
+  https://discourse.ubuntu.com/t/
+
+Please check your uploads in a <CODENAME> chroot. See [1] or [2] for details on
+how to set up such a development chroot.
+
+Please see the release schedule page for information about any major changes
+and for all milestone dates.
+
+[1] https://wiki.ubuntu.com/SimpleSbuild
+[2] https://wiki.ubuntu.com/DebootstrapChroot
diff --git a/jira-milestones/end-of-life.yaml b/jira-milestones/end-of-life.yaml
new file mode 100644
index 0000000..701c3f1
--- /dev/null
+++ b/jira-milestones/end-of-life.yaml
@@ -0,0 +1,122 @@
+
+- timeline: -45
+  duedate: 3
+  tasks:
+  - task: Send Release End of Life Warning to ubuntu-announce
+    description: Ensure that the email gets moderated and accepted.
+  - task: Notify the web team manager that ubuntu pages will need to be updated to remove EOL release
+- timeline: -10
+  duedate: 3
+  tasks:
+  - task: Verify that distro-info-data has the correct EOL date for this release, and fix it if it does not
+- timeline: 0
+  duedate: 7
+  tasks:
+  - task: Clean up things before setting release to OBSOLETE in Launchpad, as otherwise removals are not actually published
+    checklist:
+    - NBS
+    - New queue
+    - Unapproved queue
+    - Packages in -proposed (Any packages in -proposed which are just autopkgtest fixes should be removed from -proposed.)
+    - Check for any updates which are phasing and decide if they should be fully phased or the changes reverted
+  - task: Set release to OBSOLETE in Launchpad 
+    description: |
+      Work with SRE, who can visit e.g. https://launchpad.net/ubuntu/$releasename/+admin even if the series page itself is too slow to load any longer).
+  - task: Update http://changelogs.ubuntu.com/meta-release and http://changelogs.ubuntu.com/meta-release-proposed
+    checklist:
+    - "Set the release to Supported: 0"
+    - "Update the ReleaseNotes URI so that it includes an EOL disclaimer, such as in PrecisePangolin/ReleaseNotes"
+  - task: Update https://wiki.ubuntu.com/Releases for Canonical support
+  - task: Deactivate any milestones for the release
+    description: >
+      Look at https://launchpad.net/ubuntu/$releasename/+milestones and open a tab for each one.
+      Then switch the milestone from active to inactive.
+  - task: Archive the release on old-releases on ancientminister
+    description: |
+      Warning: It may not be possible to follow this procedure entirely mechanically! old-releases is by its nature not very regularly maintained, and the fact that many files are purged from the master system and only exist on mirrors can cause a good deal of confusion.
+      Refer to the publicly-visible structure on http://old-releases.ubuntu.com/releases/.
+      This procedure indicates with some degree of accuracy what steps need to be taken, but anyone following this procedure is strongly advised to use their initiative. 
+      In the following instructions, RELEASE should be replaced throughout with the name of the EOLed release. PROJECT is used for flavours of Ubuntu other than Ubuntu itself (e.g. Kubuntu, Edubuntu, etc.).
+
+      Required steps (this could be a checklist, but items are quite 'huge'):
+
+      * Disable mirror syncing: `touch /srv/cdimage.ubuntu.com/etc/STOP_SYNC_MIRRORS`
+      * In /srv/cdimage.ubuntu.com/www/simple/, find all directories named after the EOLed release. In each one:
+        * Move all files containing the release number in the adjacent .pool directory to the corresponding .pool subdirectory of /srv/cdimage.ubuntu.com/www/old-releases/ (either .pool or PROJECT/.pool), creating it if necessary.
+        * In the target .pool directory, run checksum-directory . /path/to/old/directory, or update checksums manually if necessary (in the latter case, remember to use sign-cdimage on each checksums file).
+        * Move all files starting with a lower-case letter to the corresponding subdirectory of /srv/cdimage.ubuntu.com/www/old-releases/ (either RELEASE or PROJECT/RELEASE), creating it if necessary.
+        * In the target directory, run checksum-directory . /path/to/old/directory ../.pool, or update checksums manually if necessary (in the latter case, remember to use sign-cdimage on each checksums file).
+        * In the target directory, update web indices. The procedure for doing this varies depends on whether the images currently being archived supersede all previous images from the previous point release (if any), or if some images from a previous point release must be kept visible (as is the case when EOLing the server part of an LTS release).
+          * In the former case, run DIST=RELEASE for-project PROJECT make-web-indices . PREFIX, where PREFIX is the common prefix of the images without any trailing - (e.g. ubuntu-9.10).
+          * In the latter case, edit .htaccess and HEADER.html by hand and change the version numbers for only those images that are being superseded. 
+        * Make sure that appropriate version-number symlinks to the release name exist in /srv/cdimage.ubuntu.com/www/old-releases/ or /srv/cdimage.ubuntu.com/www/old-releases/PROJECT/.
+        * Edit /srv/cdimage.ubuntu.com/www/old-releases/.htaccess and /srv/cdimage.ubuntu.com/www/old-releases/HEADER.html (or old-releases/PROJECT/...) by hand to refer to the EOLed releases.
+        * In the source .pool directory (under /srv/cdimage.ubuntu.com/www/simple/), run checksum-directory . to get rid of references to the EOLed release.
+        * Remove the remaining files and symlinks corresponding to the EOLed release from under /srv/cdimage.ubuntu.com/www/simple/. Clean up emptied directories if any.
+        * Edit /srv/cdimage.ubuntu.com/www/simple/.htaccess and /srv/cdimage.ubuntu.com/www/simple/HEADER.html (or simple/PROJECT/...) by hand to remove references to the EOLed release.
+        * Edit /srv/cdimage.ubuntu.com/www/simple/.htaccess (not PROJECT-specific) to add appropriate RedirectPermanent directives redirecting users to the new URLs. 
+      * Re-enable mirror syncing: `rm /srv/cdimage.ubuntu.com/etc/STOP_SYNC_MIRRORS`
+      * Push to mirrors: `sync-old-releases; sync-mirrors`
+  - task: Move any images from cdimage.ubuntu.com to old-images on nusakan and notify IS team for archival
+    description: |
+      Required steps (this could be a checklist, but items are quite 'huge'):
+
+      * Disable mirror syncing: `touch /srv/cdimage.ubuntu.com/etc/STOP_SYNC_MIRRORS`
+      * If /srv/cdimage.ubuntu.com/www/full/netboot/RELEASE/ exists, remove it (it is only an HTML page with links, and does not need to be archived), remove any symlinks to it, and remove references to it from /srv/cdimage.ubuntu.com/www/full/netboot/index.html.
+      * In /srv/cdimage.ubuntu.com/www/full/, find all directories named after the EOLed release which have /releases/ in their path. Each one will have a subdirectory identifying the milestone (e.g. release, release.1, etc.). For each one:
+        * Move the directory to the corresponding subdirectory of /srv/cdimage.ubuntu.com/old-images/, creating it if necessary.
+        * Remove any remaining files and symlinks corresponding to the EOLed release from under /srv/cdimage.ubuntu.com/www/full/. Clean up emptied directories if any. 
+      * In /srv/cdimage.ubuntu.com/www/torrent/, find all directories named after the EOLed release which have /releases/, /ports/, or /simple/ in their path. Remove these directories.
+      * Re-enable mirror syncing: `rm /srv/cdimage.ubuntu.com/etc/STOP_SYNC_MIRRORS`
+      * Push to mirrors: `sync-mirrors`
+  - task: Archive the apt archive to old-releases
+    description: >
+      Even with sign-off from all parties, we typically give a generous grace period between backup and removal, a month for 9mo releases and 6mo for LTS
+      is a reasonable lower bound.
+    checklist:
+    - Notify IS to backup (and verify) the ftp archive to old-releases. They should have tickets filed for this well in advance. 
+    - Remove the release from the archive (send RT ticket asking IS to follow this procedure, requiring sign-off from IS, Foundations, Release Team,
+    - Commercial Engineering, and Launchpad) 
+    - Once that is done, ask IS to run https://wiki.canonical.com/InformationInfrastructure/OSA/LPHowTo/ObsoleteDistroSeries to remove the series from the internal FTP master host and obsolete the publications on Launchpad. 
+  - task: Update lp:ubuntu-archive-scripts to drop references to the removed release
+    description: >
+      This will stop tasks such as component-mismatches, proposed-migration, germinate and so on from being run.
+      Add the EOLing release to the exclusion list in the archive-reports rsync, to stop it being mirrored from ftpmaster.
+  - task: Disable the release in appstream-generator
+    description: >
+      Usually done by HeatherEllsworth. Can be done in https://git.launchpad.net/~ubuntu-desktop/+git/appstream-cloud/, removing the release from config.json,
+      then git pull and run juju set appstream-generator config="$(cat config.json)" as prod-ue-appstream-back@wendigo (Canonical only).
+  - task: Update osinfo-db for the move to old-releases
+    description: Usually done by JeremyBicha.
+  - task: Remove the EOL release from autopkgtest
+    description: >
+      Notify BrianMurray, JulianAndresKlode, SteveLangasek or LukaszZemczak for this task.
+      Edit mojo/service-bundle in lp:autopkgtest-cloud to remove the release, then run mojo run on the bastion host; and remove the images
+      (in all cloud regions, run something like glance image-list | awk -F '| ' '/adt\/ubuntu-RELEASE/ { print $2 }' | xargs glance image-delete.
+      Also clean up old logs and results for the series with swift --os-auth-url $SWIFT_AUTH_URL --auth-version $SWIFT_AUTH_VERSION --os-tenant-name
+      $SWIFT_TENANT --os-username $SWIFT_USERNAME --os-password $SWIFT_PASSWORD --os-region-name $SWIFT_REGION delete autopkgtest-RELEASE. (and autopkgtest-RELEASE-*)
+  - task: Notify someone with access to the "prod-cnf-extractor" group to disable generation of command-not-found indices
+    description: juju config cnf-extractor releases="space separated list of releases"
+  - task: Tell Canonical IS that they can remove images for this release from the internal clouds
+  - task: Manually remove the release from snakefruit:~ubuntu-archive/.madison-lite/config so it doesn't show up in rmadison output
+  - task: As ubuntu-archive on snakefruit, manually remove files related to the release
+    description: >
+      ~/public_html/proposed-migration/RELEASE* ~/proposed-migration/output/RELEASE ~/proposed-migration/data/RELEASE* ~/public_html/seeds/*.RELEASE
+      ~/public_html/germinate-output/*.RELEASE
+  - task: Clear all packages from the partner repository for this release with remove-package (check with PES first)
+  - task: Send EndOfLifeAnnouncement to ubuntu-announce, ubuntu-security-announce
+  - task: Notify the web team manager to remove the release from the website
+  - task: Run close-EOL-bugs RELEASE from ubuntu-archive-tools
+  - task: Update charmed daisy retracer cronjob named "whoopsie-update-daily-users.bash.tmpl" to no longer collect stats on the release
+    description: e.g. https://bazaar.launchpad.net/~daisy-pluckers/charms/xenial/daisy-retracer/trunk/revision/206
+  - task: Update utils.py in https://code.launchpad.net/~daisy-pluckers/daisy/trunk so that the release is in EOL_RELEASES
+    description: ...which will also increment a counter for that specific release e.g. unsupported.eol_raring.
+  - task: Run script which unsubscribes teams (specifically Canonical teams) from packages which are no longer in main or restricted for supported releases
+  - task: Remove /srv/cdimage.ubuntu.com/scratch/*/RELEASE to free up disk space
+  - task: Remove the EoL release from ddebs
+    description: >
+      On ddebs.internal, move /srv/ddebs.ubuntu.com/www/dists/RELEASE* to /srv/ddebs.ubuntu.com/www/dists.old/, after which ddeb-retriever will do
+      a garbage-collection pass.
+  - task: Submit an RT to remove unnecessary crash data from the Error Tracker for the EoL release
+    description: See https://rt.admin.canonical.com/Ticket/Display.html?id=128690 as an example.
+
diff --git a/jira-milestones/final-release.yaml b/jira-milestones/final-release.yaml
new file mode 100644
index 0000000..171bdb2
--- /dev/null
+++ b/jira-milestones/final-release.yaml
@@ -0,0 +1,140 @@
+- timeline: -14
+  tasks:
+  - task: NonLanguagePackTranslationDeadline, ensure uploads with updated translations downloaded from Rosetta are done
+    checklist:
+    - ubiquity (debian-installer)
+    - ubiquity-slideshow-ubuntu (watch out for Xubuntu - translations not hosted on LP!)
+    - gnome-user-docs and ubuntu-docs
+    - DDTP data (package description translations)
+  - task: Notify Language Translation Lead and the current langpack-o-matic maintainer to coordinate a fresh set of language packs
+    description: |
+      Currently GunnarHj and sil2100.
+      Those need to be exported, uploaded, and built in time for the release.
+  - task: 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
+  - task: Verify there are no remaining 'bootstrap' entries in the update-i386-whitelist script in ubuntu-archive-tools
+  - task: "Run vorlon/remove-i386-binaries from [e-mail]:canonical/foundations-sandbox.git to remove any built i386 binaries that are no longer seeded"
+- timeline: -10
+  tasks:
+  - task: If any image names have changed since the previous cycle, notify the web team to check the website downloader code
+    description: |
+      (#web-team on canonical; email: [e-mail]) Ask the web team to review Release Manifest.
+  - task: Start off release notes and announce framework
+    description: |
+      Call for ubuntu-docs and other team participation in content creation of overview and documentation of release bugs.
+- timeline: -7
+  duedate: 0
+  tasks:
+    - task: Selectively accept package uploads to resolve targeted bugs
+    - task: Go through ReleaseChecklist (again, yes)
+    - task: Review list of full iso image names and plans with web team
+    - task: "Disable apport uploads to Launchpad ('problem_types': ['Bug', 'Package'], in /etc/apport/crashdb.conf)"
+      description: You can reach out to BrianMurray if in doubt.
+    - task: Notify Ubuntu and other flavour contacts to create and update their Upgrade docs at https://help.ubuntu.com/community/SERIESUpgrades
+    - task: Send out FinalFreeze announcement to [e-mail] (usually somewhere around 21:00 UTC)
+- timeline: -6
+  tasks:
+    - task: Contact the web team to confirm status
+      checklist:
+      - website preparations are on-track; this includes preparing download pages
+      - update https://ubuntu.com/download/flavours
+    - task: Post full set of pre-release images with last language pack updates to QA iso tracker to start QA testing
+    - task: Turn off daily builds
+      description: Unless explicit reason why they need to remain on.
+    - task: Review unsubscribed packages in the team to package mapping report - there should be none
+- timeline: -3
+  tasks:
+    - task: Make sure that /etc/issue, /etc/issue.net, /etc/lsb-release, and /etc/os-release are correct
+    - task: Modify debian-cd/CONF.sh to set OFFICIAL
+    - task: Ensure that the ISO tracker lists the new milestone with the "publish from manifest" flag set
+    - task: Produce a full set of official images
+    - task: Check the volume labels on ISO's for all architectures (cdimage/debian-cd/CONF.sh, OFFICIAL variable)
+    - task: Clear out the testing grid
+    - task: Clear the NBS list
+    - task: Notify Hardware Certification team to begin certification testing
+    - task: Notify QA to begin ReleaseValidationProcess
+    - task: Prepare the release announcement
+    - task: Notify Flavor Product Managers to prepare separate release announcements and review/update Release Notes
+      description: |
+        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 
+    - task: Review targeted bugs and take final decisions on what to fix and what to defer
+    - task: In a local checkout of hints-ubuntu, run generate-freeze-block <list of flavours> > freeze
+      description: |
+        generate-freeze-block comes from lp:ubuntu-archive-tools
+- timeline: -1
+  tasks:
+    - task: Pre-publish the CD images
+      description: |
+        Run `/home/lzemczak/ubuntu-archive-tools/publish-image-set --prepublish` will print the necessary commands.
+    - task: Copy .manifest to .manifest.full, and prune all images from previous releases from the .manifest file
+      description: |
+        This allows timely mirror probing
+    - task: Run sync-mirrors on ancientminister to push out the pre-published file structure
+    - task: Review on the staging server the feature walk through on the website (web-team)
+    - task: Build the sources images (cron.source) to be published, by the publisher script
+    - task: "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"
+    - task: Apply a "block-all source" hint to proposed-migration; any further changes to -proposed not intended for SRU will need to be unblocked manually
+- timeline: 0
+  tasks:
+    - task: If there is a previous milestone for this series, archive it to old-images
+      description: >
+        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.
+    - task: Disable mirror syncing on ancientminister, by creating /srv/cdimage.ubuntu.com/etc/STOP_SYNC_MIRRORS.
+    - task: Publish the CD images
+      description: |
+        ./publish-image-set will print the necessary commands.
+        You might need to edit cdimage/www/simple/HEADER.html and cdimage/www/simple/.htaccess by hand, if needed.
+    - task: "Ping CPC using cpc-help keyword in #ubuntu-release to start the process of building and publishing cloud images"
+    - task: Ping the WSL team to release the images to the store
+    - task: Copy .manifest to .manifest.full again, pruning all images from previous releases from the .manifest file
+    - task: Verify .manifest only contains the images currently being released, and then ask the IS vanguard to run the mirror prober continuously
+      description: |
+        This is to verify which mirrors are up to date; output visible here.
+        Take a note of how many mirrors were there before this started.
+        You can refer to the following wiki page https://wiki.canonical.com/InformationInfrastructure/OSA/LPHowTo/ManualCdImageMirrorProber
+        NOTE! This requires the previous mirror prober run to finish first, so it might take some minutes before mirrors are cleared out.
+    - task: Check torrents for proper functionality
+      description: |
+        Check that https://torrent.ubuntu.com/tracker_index has all the new images 
+        Ensure the tracker knows about the torrent, either by checking Properties -> Trackers in Transmission, or by using a CLI client such as aria2c which prints the errors to its stdout).
+    - task: Confirm that website content is finalized
+      description: |
+        Further edits will be difficult under load and check with sysadmin that caches will be cleared on time (web-team, IS, release-team).
+    - task: 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
+      description: |
+        This list is baked into the Ubuntu website at build time, so notify the web team to (re)build the site. 
+    - task: Coordinate with web team for publishing of staging
+    - task: Coordinate with PR team to inform media who are waiting for launch to post their articles
+    - task: Check through the release notes for links to old milestones and update them 
+    - task: "Update the topic on #ubuntu-devel, and #ubuntu-release-party"
+    - task: "Make announcement in #ubuntu-release-announce, and then in #ubuntu-release-party"
+    - task: Update the appropriate meta-release files
+      description: >
+        Update the appropriate meta-release files (including meta-release, meta-release-proposed, and raspi/os_list_imagingutility_ubuntu.json) in the bzr branch. N.B. meta-release-lts is done at the first point release of an LTS.
+        Then a member of the ubuntu-release group (bdmurray, vorlon, sil2100) updates the meta-release files via foundations-bastion-ps5.internal.
+        ssh -i ~/.ssh/id_rsa_autodeploy_trigger [e-mail] /usr/bin/autodeploy-trigger prod-ubuntu-web-frontends refresh-changelogs
+    - task: Ping Canonical IS to clear the content-cache in is-content-cache for changelogs.ubuntu.com-http and changelogs.ubuntu.com-https
+    - task: Switch the development release from its codename to its version in errors/templates/bucket.html in errors
+    - task: Notify web team to announce on the website
+    - task: Send the release announcement to ubuntu-announce
+    - task: Notify a Launchpad admin to set the status of this distrorelease to CURRENT, and to change any previous CURRENT distrorelease(s) to SUPPORTED
+    - task: Deactivate release milestone in Launchpad
+    - task: Post announcement to News & Announcements section (forum admins have posting rights)
+    - task: Post announcement to Launchpad (ubuntu-drivers members have posting rights)
+    - task: Create a branch for the stable release in hints-ubuntu
+      description: |
+        git branch <release> devel; git push origin <release> (To ensure it’s available before any 0-day SRUs are uploaded)
+    - task: Update the main page of wiki.ubuntu.com to include the new release in the Releases table
+    - task: Update the https://wiki.ubuntu.com/Releases table with the new release
+    - task: Mark the ISO Tracker milestone as Released
+    - task: Sleep!
+- timeline: 1
+  tasks:
+    - task: If any changes were made to the process in this run, check whether the changes also apply to BetaProcess or ReleaseCandidateProcess.
+      description: |
+        Remember to modify the Jira release templates as well.
+    - task: Restore the .manifest.full file on releases.ubuntu.com
+    - task: Ask Canonical IS to restore the mirror prober back to normal operation
+    - task: Continue on NewReleaseCycleProcess
+    - task: Review through the process pages
diff --git a/jira-milestones/new-cycle-opening.yaml b/jira-milestones/new-cycle-opening.yaml
new file mode 100644
index 0000000..a00db44
--- /dev/null
+++ b/jira-milestones/new-cycle-opening.yaml
@@ -0,0 +1,209 @@
+- timeline: -14
+  tasks:
+  - task: Ask for the maillist distroseries-changes to be set up by sending email to [e-mail] to file an RT ticket
+    description: <
+      Note that this requires special configuration. 
+  - task: Create a release schedule for the new series
+    description: If the release name is not yet known, substitute the letter twice, e.g. FF for the F-series.
+  - task: Create a thread on the release category on discourse
+    checklist:
+    - Use generate-release-schedule-markdown CODENAME STARTDATE ENDDATE from lp:ubuntu-archive-tools to make a template, and then edit as needed (mark as draft)
+    - "Create a redirect from https://wiki.ubuntu.com/ReleaseName/ReleaseSchedule to the new page (syntax: #REFRESH 0 https://URL.TO.THREAD)"
+  - task: Create a release notes document for the new series
+    description: If the release name is not yet known, substitute the letter twice, e.g. FF for the F-series.
+    checklist:
+    - Create a thread on the release category on discourse. Check previous discourse release notes for format.
+    - "Create a redirect from https://wiki.ubuntu.com/ReleaseName/ReleaseNotes to the new page (syntax: #REFRESH 0 https://URL.TO.THREAD)"
+  - task: Close the new threads, so they can be edited but not replied to
+    description: <
+      Release team members can do this. Until Discourse can sync groups from SSO (LP) directly, the release team group in Discourse is manually managed.
+      Contact an admin (e.g. the Canonical community team) to be added if you need this. 
+- timeline: 1
+  tasks:
+  - task: Edit (cowboy) run-proposed-migration on snakefruit to disable proposed-migration for the new series (add an exit 0 to the ubuntu/$DEFAULT_SERIES case branch)
+    description: proposed-migration must not run until autopkgtest is ready to receive test requests for the series.
+  - task: Update lp:ubuntu-archive-scripts update-seeds, update-germinate etc. for the new name and pull it into snakefruit:~ubuntu-archive/bin/
+    description: This will cause update-seeds to start failing until the below step is done, so do it quickly afterwards.
+  - task: Create new seed branches based on those for the previous release, and push them to the appropriate subdirectories of git+ssh://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git
+    description: The branch-seeds script in lp:ubuntu-archive-tools can do the hard work here.
+  - task: Create new seed branches based on those for the previous release, and push them to the appropriate branches on Launchpad
+    description: The branch-seeds script in lp:ubuntu-archive-tools can do the hard work here.
+    checklist:
+    - Have a checkout of all the seeds for the current stable release as COLLECTION.series
+    - Run branch-seeds --dest-series <new series> <collection> ... for all the collections
+    - Run update-seeds manually on snakefruit to confirm this all worked. Check the exit status is 0
+  - task: Request Launchpad disable the primary Ubuntu publisher cron jobs
+    description: <
+      https://wiki.canonical.com/InformationInfrastructure/OSA/LaunchpadRollout#Disable_fragile_Soyuz_cron_jobs_.2835_mins_before_rollout.29 
+  - task: Notify a Launchpad admin (IS) to create new distroseries with status FROZEN
+    description: Copy the Release Manager and Drivers forward 
+  - task: Create milestones in the new series
+    checklist:
+    - ubuntu-YY.MM etc., set at monthly intervals after the previous release until feature freeze
+    - ubuntu-$version-feature-freeze, ubuntu-$version-beta or ubuntu-$version-beta-1 etc. as required
+    - ubuntu-$version at the next release date
+    - ubuntu-$version-updates at EOL 
+  - task: Check that the new distroseries exists with status FROZEN, and that the previous distroseries has status CURRENT
+  - task: Initialize the series
+    description: <
+      Visit http://launchpad.net/ubuntu/<series> and click "Initialize Series" in the top right menu.
+      Select which Debian parents you want for this series (it defaults to the existing ones), which architectures you want,
+      ensure "Copy Source And Binaries" is selected and click the "Initialize Series" button. Wait for this to finish before running the publisher,
+      this will take 15 to 30 minutes.
+      In the event that a new architecture was added ensure it is also added to command-not-found-extractor's update_all.sh script. 
+  - task: Re-enable the Soyuz publisher cron job for a single publisher run
+  - task: Add the new series name to the official Launchpad bug tags, and add verification-needed-PREVIOUS and verification-done-PREVIOUS where PREVIOUS is the name of the previous series
+  - task: After the first publisher run has completed, ask ~IS to run "ANALYZE sourcepackagepublishinghistory; ANALYZE binarypackagepublishinghistory;" on launchpad_prod
+  - task: Re-enable the Soyuz publisher cron job for a second publisher run
+    description: Watch the logs to make sure this work.
+  - task: As ubuntu-archive@snakefruit, use compare-archives to compare dists trees under ~/mirror/ubuntu/ for previous and current distroseries and sign off on any differences
+    description: <
+      The only differences should be the distroseries name, that custom uploads (installer-*, dist-upgrader-all, and i18n) are missing from dists/DSN/main,
+      and that Contents-*.gz do not yet exist (these will be created when generate-contents next runs).
+  - task: Permanently re-enable the Soyuz publisher cron job
+  - task: Copy the pending syncs which we didn’t want to accept from previous-proposed UNAPPROVED, and then reject them
+  - task: Notify the autopkgtest infra maintainers to run through https://autopkgtest-cloud.readthedocs.io/en/latest/administration.html#opening-up-a-new-series
+  - task: Update lp:~ubuntu-release/britney/britney1-ubuntu/ with the new DEFAULT_SERIES
+  - task: Once autopkgtest is ready, finish the britney initialization
+    checklist:
+    - on snakefruit, cp -a ~/proposed-migration/data/OLDRELEASE ~/proposed-migration/data/NEWRELEASE and cp -a ~/proposed-migration/data/OLDRELEASE-proposed ~/proposed-migration/data/NEWRELEASE-proposed so that we do not reset state for devel
+    - undo the run-proposed-migration cowboy from above, so that proposed-migration can start running for the new series
+  - task: [~techboard] Check that the process of initialising the new distroseries granted queue admin access to ~ubuntu-release to the new distroseries
+    description: edit-acl -p ubuntu-release -S NEW -t admin query
+  - task: Move the bootstrap archive on snakefruit to use the new series, so the chroots can reference it
+  - task: Ask the launchpad team to run manage-chroot operations to copy OLDRELEASE buildd chroots forward to NEWRELEASE
+  - task: As lp_buildd@anonster, run /srv/launchpad.net/production/launchpad/scripts/add-missing-builds.py -s NEW-proposed plus -a ARCH for each architecture in NEW
+    description: Steve Langasek and Colin Watson have access, or ask IS.
+  - task: Add a request to Launchpad devs and admins to open Launchpad translations for the new distroseries
+    description: "Also make sure this actually happens. (TODO: Work out a better process for keeping track of this in conjunction with Launchpad.)"
+  - task: Modify various reports on snakefruit (at least britney) to point to the new distroseries
+    checklist:
+    - cd public_html; find . -maxdepth 3 -type l | while read symlink; do target=$(readlink "$symlink"); case $target in \*autopkgtest-results.cache\*) ;; \*OLDRELEASE\*) echo $symlink '->' $target; target=$(echo "$target" | sed -e's/OLDRELEASE/NEWRELEASE/'); ln -sf $target $symlink ;; esac; done
+    - See the git log in ~ubuntu-archive/ubuntu-archive-tools for the changes done for the last release and update to the current one
+    - Add the new release to ~ubuntu-archive/.madison-lite/config on snakefruit so that rmadison starts working
+  - task: Notify someone in the 'merges' LDAP group to set up merge-o-matic to point to the new distroseries
+    description: Switch to the merge user, cd /srv/patches.ubuntu.com/code/, bzr pull.
+  - task: Upload some basic packages for the new series
+    description: At least debootstrap is needed to build the livefs builds.
+    checklist:
+    - Update distro-info-data for the new series.
+    - Merge base-files if necessary and change /etc/issue, /etc/issue.net, /etc/lsb-release, and /etc/os-release to refer to the new release.
+    - Add the symlink for the new series in debootstrap
+    - Make sure these are migrated and ping the cpc team to do the livefs builds. 
+  - task: Update global.conf and go in lp:~ubuntu-transition-trackers/ubuntu-transition-tracker/configs
+  - task: Notify toolchain developers to upload new toolchain
+    description: Iterate uploads as necessary until this has successfully built on all architectures.
+  - task: Make sure that proposed-migration is configured properly for the new series
+    description: |
+      Check that https://people.canonical.com/~ubuntu-archive/proposed-migration/<NEWSERIES>/autopkgtest-results.cache exists, as required by bileto.
+      If not, this can be done by creating a new symlink to the proposed-migration’s data directory. 
+  - task: Remove the "block-all source" hint from proposed-migration
+  - task: Once the tool chain is ready, notify about readiness for uploads
+    checklist:
+    - Notify a Launchpad admin to set the status of the new distroseries to 'Active Development'.
+    - Accept everything in the Unapproved queue for the new distroseries
+    - Update the topic on #ubuntu-devel and #ubuntu-release the new release is open
+    - Email ubuntu-devel-announce that the new release is now open for uploads
+  - task: Check whether there are any uploads in the previous release's -updates pocket not in the new release, and copy them over if so
+  - task: [~ubuntu-archive] Copy everything from PREVIOUS-proposed to DEVEL-proposed, and delete the ones from PREVIOUS-proposed that aren't SRUs
+  - task: [~techboard] Grant ~ubuntu-sru queue admin access to the previous distroseries
+    description: |
+      for pocket in proposed updates; do edit-acl -p ubuntu-sru -S PREVIOUS --pocket $pocket -t admin add; done;
+      Remove ~ubuntu-release's queue admin access 
+      for pocket in release proposed; do edit-acl -p ubuntu-release -S PREVIOUS --pocket $pocket -t admin delete; done.
+  - task: Inform the SRU team that the bulk copy has been done, so that they know to sort out PREVIOUS-proposed vs. DEVEL-proposed for any new SRUs they accept
+  - task: Drop the --dry-run flag from the auto-sync job in ubuntu-archive@snakefruit's crontab
+  - task: Contact owners of each image with seeded snaps to have snap channels opened and closed for the new release
+    description: |
+      Note: image owners are not well defined, some guesswork may be needed. For example for Desktop a starting point could be a Desktop Team manager.
+    checklist:
+      - Get the list of seeded snaps from the seeds: `readarray -t seeded_snaps < <(grep -ohP '(?<=snap:)[^\s/]*' * 2>/dev/null | sort -u)`
+      - Add subiquity as it's seeded but not in the seeds: `seeded_snaps+=(subiquity)`
+      - Try downloading all the snaps from the stable channel: for `s in "${seeded_snaps[@]}"; do snap download "$s" --channel=stable/ubuntu-XX.YY; done`
+      - If a failing download is for an internally developed snap (we're upstream), contact the relevant team to have the channel open.
+      - If a failing download is for an external snap (e.g. firefox), ask the image owner to ask the snap upstream to open the channel.
+      - Iterate until all the downloads succeed.
+    description: <
+      The list of seeded snaps can be extracted from the seeds via `grep -ohP '(?<=snap:)[^ ]*' * 2>/dev/null | sort -u`. The list may
+      have to be manually amended (e.g. dropping experimental snaps, or adding `subiquity` as it's not in the seeds).
+      Assuming 
+
+  - task: "Create new live filesystem configurations for the new distroseries, using branch-livefses in lp:ubuntu-archive-tools"
+    description: <
+      This requires someone in ~launchpad-ppa-admins/~launchpad-ppa-self-admins, ~ubuntu-cdimage and ~launchpad-livefs-builders.
+      This currently needs to be done for multiple owners.
+    checklist:
+    - ubuntu-cdimage
+    - cloud-images
+    - cloudware
+    - cloud-images-release-managers 
+  - task: Create data/RELEASE, tools/RELEASE, and tools/boot/RELEASE directories in debian-cd based on corresponding directories for the previous release
+  - task: Add the new release to CONF.sh and set OFFICIAL to "Alpha".
+  - task: Adjust cdimage code to be aware of the new release
+    description:
+      Example - https://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/revision/2030
+  - task: On ancientminister configure ~cdimage/.isotracker.conf
+  - task: Notify stgraber, vorlon, or bdmurray to follow README.series on db@limequat (the ISO tracker database) after sudo'ing to db
+    description: Confirm that the new series has a manifest in the ISO tracker administrative interface.
+  - task: Target issues from the previous release's release notes to be fixed in the new release
+  - task: Notify Brian Murray or a real ~ubuntu-archive member to create an Apport retracer apt configuration (example for 17.04) for the new release
+    description: <
+      Roll it out to porter-i386:/home/ubuntu-archive/config. Additionally, enable -proposed for the version of Ubuntu which was just released.
+      It'd also be good to clean out the retracer cache (in /home/ubuntu-archive/cache-$arch/) for the previous development release as crashes should no longer
+      be submitted to Launchpad.
+  - task: Check http://ddebs.ubuntu.com for the new release
+    description: <
+      In principle that should happen by itself, but in practice it may crash/hang on archive.ubuntu.com not yet having indexes, or run into time outs on
+      the gigantic first import after opening/copying the new release). This is running on ddebs.internal → sudo -u ddebs -i; This has a checkout of
+      lp:ddeb-retriever and is cron driven.
+  - task: Notify someone with access (hellsworth) to the user update config.json to add the new release to the list in git lp:~ubuntu-desktop/+git/appstream-cloud
+    description: <
+      Make sure the json is valid, and then as prod-ue-appstream-back@wendigo run juju set appstream-generator config="$(cat config.json)" after pulling.
+      See 9163c1a2bc5fb3c2c2ba1c27df8f7573a54b4045.
+  - task: Notify William Grant to update the ftbfs on qa.ubuntuwire.com
+  - task: Notify Rhonda D'Vine (Rhonda) to update packages.ubuntu.com
+  - task: Notify an archive admin to update people.c.c/~ubuntu-archive/transitions and udd.debian.org
+    description: currently done in the `ben` lxc container
+  - task: Update lp:ubuntu-manpage-repository/production for the new release codename
+    description: e.g. adding a release, and submit an RT to have the server updated
+  - task: Notify Brian Murray to update whoopsie-update-daily-users cronjob in the retracer charm owned by the daisy-pluckers team to include the new release of Ubuntu
+  - task: Notify Brian Murray to update the Ubuntu Error Tracker for the new release of ubuntu
+    description: e.g. errors change (https://bazaar.launchpad.net/~daisy-pluckers/errors/trunk/revision/644) and daisy change (https://bazaar.launchpad.net/~daisy-pluckers/daisy/trunk/revision/946)
+  - task: Notify someone with access to the "prod-cnf-extractor" group on wendigo to enable generation of command-not-found indices
+    description: juju config cnf-extractor releases="space separated list of releases"
+  - task: Update ubuntu-release-upgrader to handle the new release
+    description: <
+      e.g. https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/trunk/revision/3181 and DistUpgradeQuirks
+      e.g. https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/trunk/revision/3232.
+  - task: If the new release is an LTS, reach out to the official Ubuntu flavors regarding their LTS status (the maintenance period)
+    description: After gathering feedback, updating both the release schedule and release notes discourse threads.
+  - task: Revisit the post-release items for the release which was just performed, confirm they were completed, and complete them now if not
+- timeline: 7
+  duedate: 14
+  tasks:
+  - task: Notify 'ubuntu-devel' and 'ubuntu-devel-announce' that the release is now open and where to subscribe to the release'-changes' maillist
+  - task: Notify the Launchpad team to upload new buildd chroots
+    description: (which should be done occasionally throughout the cycle, for efficiency).
+  - task: Merge base-files if necessary and change /etc/issue, /etc/issue.net, /etc/lsb-release, and /etc/os-release to refer to the new release
+  - task: Merge debootstrap if necessary and create a bootstrap script for the new release as a copy of the previous one
+    description: Currently, we can just make the new one a symlink to gutsy, as it hasn't changed since then.
+  - task: Merge lintian if necessary and update the lists of Ubuntu release names to include the new release name in all supported releases of Ubuntu (i.e. SRU it!)
+  - task: Merge vim if necessary and update lists of Ubuntu release names to include the new release name
+  - task: Merge clang if necessary and update lists of Ubuntu release names to include the new release name
+  - task: Do a no change rebuild of devscripts to pick up the new development release from distro-info
+  - task: Update meta-release-development to handle the new release
+  - task: Notify ubiquity maintainer(s) to run debian/rules update, adjust as necessary to account for changes, and upload
+  - task: Ensure that the ISO tracker has a daily-build "milestone" for the new release
+  - task: Edit default_milestone in ~cdimage/.isotracker.conf to match the new milestone name in the ISO tracker
+  - task: Notify canonical-platform-qa ([e-mail]) to set up Utah jobs for Ubuntu desktop and server
+  - task: In production/current-triggers if anything is not open ended in the third column (series names) update them for the new series on cdimage-builder.internal as appropriate.
+  - task: On cdimage-builder.internal turn live filesystem and cdimage cron jobs back on
+    description: After ensuring that the debian-cd and cdimage branches have been updated
+  - task: Add the date of the previous release to calendar.ubuntu in bsdmainutils
+  - task: Update ubuntu-release-notes project to know about the new series
+  - task: Contact flavours to confirm their ongoing participation in the new release, and verify that the contact in the ISO tracker is still accurate
+  - task: If it has not already been done calculate the release date for the next release of Ubuntu
+    description: <
+      In general, October releases follow a 25-week schedule, while April releases follow a 27-week schedule, to compensate for year-end holiday
+      (non-LTS releases might break this cycle to wiggle things a bit). Add the release date to the Canonical Ubuntu Release Calendar.
+  - task: Continue on MilestoneProcess
diff --git a/jira-milestones/point-release.yaml b/jira-milestones/point-release.yaml
new file mode 100644
index 0000000..94703da
--- /dev/null
+++ b/jira-milestones/point-release.yaml
@@ -0,0 +1,142 @@
+- timeline: -42
+  tasks:
+  - task: Create a release tracking Discourse thread for the release in mention.
+    description: |
+      This should include:
+      * On top, a short summary of the current state of the release
+      * Sections for release blocker and upgrade blocker bugs
+      * Section for bugs to watch for
+  - task: Review the release's release notes for any "Known Issues" which still need fixing and work with teams to get them fixed.
+  - task: Coordinate with the kernel team to ensure HWE kernels are updated to the new target release
+    description: See https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack#Update_Schedule-2
+- timeline: -28
+  tasks:
+  - task: In coordination with QA, verify that all candidate bugs are fixed
+  - task: Refresh (if needed) any cd-boot-image-* packages for the series
+    description: This might be needed whenever any of he boot-related packages got any updates.
+  - task: For the .2 point release, enable the HWE stack for the series
+    description: |
+      Needs doing if this point release includes the switch to enable the HWE stack (usually XX.XX.2)
+    checklist:
+    - Make sure that the variant list in livecd-rootfs's live-build/ubuntu-server/hooks/033-kernel-bits.binary hook includes both ga and hwe to make sure subiquity offers both kernel flavors. Upload and fast-forward into -updates in case it doesn't.
+    - Make sure that the server-ship-live seed includes the new hwe kernel.
+    - Check and mark livecd-rootfs auto/config LB_KERNEL_FLAVOURS to the -hwe-XX.XX variant for every desktop flavor participating.
+  - task: Change cdimage/lib/cdimage/config.py and debian-cd/CONF.sh to use the new release version number
+  - task: Make sure that that we are building the daily images with -proposed enabled
+  - task: Update the manifest to reflect publishing status of images based on input from product leads
+  - task: Build CD images and smoke-test in some convenient environment to check for obvious failures
+  - task: Liaise with teams, QA, community, certification and all involved teams to arrange for testing resources
+    description: We need to make sure that we have QA coverage for every flavor (desktop, server, pi, riscv, kubuntu etc.)
+- timeline: -21
+  tasks:
+  - task: Notify translations-team to prepare updates for point release
+  - task: Contact QA and certification as appropriate to request testing for hardware recertification
+      Make sure to get early feedback on certification testing from the daily images.
+  - task: Check to see if python-apt has been uploaded recently (upload if needed)
+  - task: Check to see if ubuntu-release-upgrader have been uploaded recently (upload if needed)
+    description: If not, upload a new version after running pre-build.sh as that generates the updated lists of mirrors.
+  - task: Ensure that the stable/ubuntu-XX.YY.Z branch has been published for the subiquity snap
+- timeline: -14
+  tasks:
+  - task: Include the latest translation updates into -proposed for the point release
+    description: |
+      Detailed information about the process can be found here: https://git.launchpad.net/langpack-o-matic/tree/doc/operator-guide.txt
+  - task: Prepare change summary and release announcement
+    description: |
+      Script to use for preparing the change summary: http://people.canonical.com/~vorlon/release-updates.py
+      * Sort and/or re-divide updates into rough categories (see previous summaries)
+      * Remove administrative-only bugs (e.g. kernel release tracking)
+      * Try to reduce each entry to just a description of the change; remove redundant bug references and information about where the change came from (people can go to the raw changelog if they care)
+      * This can involve substantial amounts of editing; make sure you have a good editor and/or a clear grasp of regular expressions
+  - task: Make sure all critical package updates are by now done and landed in -updates or -security
+  - task: Check phased-updates for any packages in -updates which have stopped phasing, or are still phasing
+    description: |
+      Decide whether to fully phase them or revert to the previous version of the package.
+      https://people.canonical.com/~ubuntu-archive/phased-updates.html
+  - task: Review the release's release notes for any "Known Issues" which are now fixed and remove them.
+  - task: Disable -proposed for the series daily image builds (to build images as close to the final product as possible)
+  - task: Ask Certification and QA to start performing preliminary image testing on the daily images as much as possible from now til release
+    description: |
+      With the goal of dentifying any release critical bugs that have not been noticed earlier.
+  - task: Coordinate with the SRU team to be more careful on which packages get promoted to -updates, keeping the incoming point-release in mind
+    description: >
+      Keep in mind that due to the fact that even release-critical bugs require an aging and verification period as per the usual SRU policy,
+      this is the final 'safe' moment whenever release facing updates can be accepted without risking the delay of the point release.
+- timeline: -7
+  duedate: 4
+  tasks:
+  - task: Release translation updates (language-packs) into -updates
+    description: |
+      Detailed information about the process can be found here: https://git.launchpad.net/langpack-o-matic/tree/doc/operator-guide.txt
+  - task: Notify web team of the upcoming point release
+    description: |
+      * Determine who from the team the publishing contact will be.
+      * Include summary list of actual file names of ISOs that will make up releases.
+      * Include detailed information about which image file names will change on the mirrors for the point release, and which ones will not.
+      * Discuss release stability and handoffs on release date.
+  - task: Upload a new base-files package to -proposed to bump the lsb_release description
+    description: >
+      Do not change the DISTRIB_RELEASE value, which is used programmatically by third-party software.
+      If the etc/os-release file exists, update VERSION and PRETTY_NAME, don't update VERSION_ID.
+  - task: Push base-files through to -updates and ensure that it is fully phase
+  - task: Once testing is verified to be complete, move packages to -updates
+    description: >
+      This should vary depending on how much testing of the daily -proposed images has been done - ideally we want to flush the whole -proposed
+      pocket to not invalidate the earlier testing.
+      If anything is moved to -updates and on installation media also ensure to fully phase it.
+  - task: Analyze the package diffs between last point-release and the current daily image for each participating flavour
+    description: ...while stripping versions to make sure no changes are pulling in a bunch of new/unexplained packages.
+  - task: Turn off cron jobs that will auto update into -updates until final images are tested
+  - task: Send out an e-mail notifying developers of the -updates pocket freeze for the duration of the point-release
+  - task: Build candidate release images and populate into iso tracker
+    description: |
+      (double check that those images are NOT building with -proposed enabled). Re-spin when appropriate.
+    checklist:
+    - Before running builds, make sure cdimage is up-to-date with archive contents and run anonftpsync on ancientminister
+    - Also remember about building source images along with those (e.g. DIST=focal cron.source), re-spinning when appropriate
+    - Remember about building core images as well (as per UbuntuCore/ReleaseProcess)
+  - task: Create a snapshot of the archive
+    description: |
+      `ubuntu-archive@snakefruit:~$ point-release-snapshot focal focal.3-security-updates-snapshot`
+      ...which will copy the relevant indices to a subdirectory of ~ubuntu-archive/point-releases/
+      Remember to re-create the snapshot whenever new candidate images are built!
+- timeline: 0
+  tasks:
+  - task: Check with IS whether the previous point release needs to be moved off before prepublishing due to mirror space constraints
+  - task: If this point-release is an LTS with an OEM stack, contact the Certification Team for a formal sign off of the images
+  - task: Pre-publish images
+    description: Running `./publish-image-set --prepublish` will print the necessary commands.
+  - task: Copy .manifest to .manifest.full, and prune all images from previous releases from the .manifest file to allow timely mirror probing
+  - task: Run sync-mirrors on ancientminister to push out the pre-published file structure
+  - task: Release images as final, and move the previous images to old-releases.ubuntu.com
+    checklist:
+    - Find which previous images on cdimage.ubuntu.com for this release are going to be replaced by this image set, and archive them to old-images
+    - Publish images, `./publish-image-set.py` will print the necessary commands
+    - Update version numbers in cdimage/www/simple/HEADER.html and cdimage/www/simple/.htaccess
+    - Archive releases.ubuntu.com images from the previous point release to old-releases by running archive-point-release
+    - Copy .manifest to .manifest.full again, pruning all images from previous releases from the .manifest file to allow timely mirror probing
+    - Run sync-mirrors on ancientminister to push out the published file structure
+    - If you moved images to old-releases, remember to run sync-old-releases as well
+    - Notify Web team to update the iso URLs on the ubuntu.com website
+    - Remember to publish core images as well
+  - task: Ping bdmurray to update meta-release file on http://changelogs.ubuntu.com/
+  - task: Regenerate the Raspi Installer JSON file to include the latest images and checksums
+    description: Ping waveform for this.
+  - task: Work with release and web publishing team to monitor mirror pickup
+    checklist:
+    - Verify download from ubuntu.com
+    - Check that the torrents are working
+    - Verify download from one of the mirrors
+  - task: Send the announcement mail
+    checklist:
+    - ubuntu-announce
+    - Update Discourse Tracking bug
+  - task: Notify press release team if needed
+- timeline: 1
+  tasks:
+    - task: Restore the .manifest.full file on releases.ubuntu.com
+    - task: Deactivate the just released "point release" milestone target
+    - task: Re-enable -proposed for daily builds on cdimage
+    - task: Re-enable daily builds
+    - task: Send out update to people running previous LTS (after migration testing completed)
+    - task: Gather feedback info for future improvements to process