Merge ~ubuntu-release/ubuntu-release-tools/+git/templates:sru-unfreeze-asap into ubuntu-release-tools:main

[Brian Murray]

We should unblock the SRU team as soon as possible.

Unless there is some reason to keep the release frozen for another 12ish hours I think we should allow the SRU team to get back to work right away.

Unmerged commits

e6502ac... by Brian Murray on 2024-02-29

point-release: move disabling the sru freeze to timeline 0

667425f... by Brian Murray on 2024-02-28

point-release: check the pointy torrents!

f49dc37... by Brian Murray on 2024-02-27

Modify the request for FFe filing to be more specific

2a76595... by Brian Murray on 2024-02-26

Feature Freeze announcement - ask for FFes ASAP

003221c... by Łukasz Zemczak on 2024-02-15

Add cards for enabling and disabling the sru-release freeze lock during point-release work.

ff014c7... by Brian Murray on 2024-02-01

eol checklist: clarify where to move things in old-images

6299192... by Brian Murray on 2024-01-31

eol: point to an RT regarding removing the images from glance

bbb7293... by Brian Murray on 2024-01-31

e-o-l: use quotes to prevent weird bolding which hide details

666730e... by Brian Murray on 2024-01-25

Send EoL mail to ubuntu-security-announce too

86aaac3... by Steve Langasek on 2024-01-31

Don't run cron.source which has now been removed per ubuntu-release@lists

diff --git a/announcements/beta-freeze b/announcements/beta-freeze
new file mode 100644
index 0000000..8de5245
--- /dev/null
+++ b/announcements/beta-freeze
@@ -0,0 +1,33 @@
+To: [e-mail]
+Reply-To: [e-mail]
+Subject: <CODENAME> (to be <VERSION>) Beta Freeze
+
+As of a short while ago, <CODENAME> has entered the Beta Freeze, with a goal of
+releasing Beta images sometime late Thursday. *From now until the Beta is
+released, please only upload updates for packages on any release images if you
+/need/ to get them into the Beta itself.* Please hold off with everything else
+until after we release on Thursday.
+
+The queue freeze will last from now until the final release next month, which
+means that all seeded packages will now need a spot-check and review in the
+queue from a release team member before they are let into the archive.
+
+As with the previous releases, we have a bot in place that will accept uploads
+that are unseeded and don't affect images. Don't take this as an open
+invitation to break Feature Freeze on those components, this is just to reduce
+the burden on the release team, so we only review the uploads that need very
+serious consideration. If you find the bot is blocking an upload that you think
+should have been auto-accepted, let us know and we'll sort it out.
+
+We will be spinning a set of Beta candidates in the next 12 hours or so.  We
+then encourage people to start testing ASAP for their favourite flavour(s) as
+they come off the line.
+
+Happy bug-hunting from now until the final release, and please do help out and
+test images, etc, where you can and let us know what's broken in your
+environment(s).
+
+As a reminder, the Beta images will appear on the ISO Tracker here:
+http://iso.qa.ubuntu.com/qatracker/milestones/<NUMBER>/builds
+
+On behalf of the Ubuntu Release Team,
diff --git a/announcements/beta-milestone-reminder b/announcements/beta-milestone-reminder
new file mode 100644
index 0000000..3a9238b
--- /dev/null
+++ b/announcements/beta-milestone-reminder
@@ -0,0 +1,14 @@
+To: [e-mail]
+Reply-To: [e-mail]
+Subject: <CODENAME> (<VERSION>) Beta milestone reminder
+
+Hello everyone!
+
+This is a gentle reminder about the nearing Beta milestone for <CODENAME>
+(<VERSION>) next week, along with the usual Beta Freeze on Monday.
+Please make sure to get as much as possible into the release pocket
+before that time - the Beta is usually a great occasion to test how
+things are looking before the release.  The closer the Beta is to our
+final product, the better.
+
+Thanks!
diff --git a/announcements/beta-release b/announcements/beta-release
new file mode 100644
index 0000000..d81c7b2
--- /dev/null
+++ b/announcements/beta-release
@@ -0,0 +1,142 @@
+To: [e-mail]
+Subject: Ubuntu <VERSION> (<FULL NAME>) Final Beta released
+
+The Ubuntu team is pleased to announce the Beta release of the Ubuntu
+<VERSION> Desktop, Server, and Cloud products.
+
+Ubuntu <VERSION>, codenamed "<FULL NAME>", 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, introducing new features and fixing bugs.
+
+<UPDATE FLAVOR NAMES ACCORDINGLY>
+This Beta release includes images from not only the Ubuntu Desktop,
+Server, and Cloud products, but also the Kubuntu, Lubuntu, Ubuntu
+Budgie, UbuntuKylin, Ubuntu MATE, Ubuntu Studio, Ubuntu Unity,
+and Xubuntu flavours.
+
+The Beta images are known to be reasonably free of showstopper image
+build or installer bugs, while representing a very recent snapshot of
+<VERSION> that should be representative of the features intended to ship
+with the final release expected on <MONTH> <DAY>, <YEAR>.
+
+Ubuntu, Ubuntu Server, Cloud Images:
+  <ADJECTIVE> Beta includes updated versions of most of our core set of
+  packages, including a current <KERNEL VERSION> kernel, and much more.
+
+  To upgrade to Ubuntu <VERSION> Beta from Ubuntu <PREVIOUS VERSION>, follow these
+  instructions:
+
+  https://help.ubuntu.com/community/<ADJECTIVE>Upgrades
+
+  The Ubuntu <VERSION> Beta images can be downloaded at:
+
+  https://releases.ubuntu.com/<VERSION>/ (Ubuntu and Ubuntu Server on x86)
+
+  This Ubuntu Server image features the next generation Subiquity server
+  installer, bringing the comfortable live session and speedy install of
+  the Ubuntu Desktop to server users.
+
+  Additional images can be found at the following links:
+
+  https://cloud-images.ubuntu.com/daily/server/<LOWERCASE ADJECTIVE>/current/ (Cloud Images)
+  https://cdimage.ubuntu.com/releases/<VERSION>/beta/ (Non-x86)
+
+  As fixes will be included in new images between now and release, any
+  daily cloud image from today or later (i.e. a serial of <YYYYMMDD> or
+  higher) should be considered a Beta image. Bugs found should be filed
+  against the appropriate packages or, failing that, the cloud-images
+  project in Launchpad.
+
+  The full release notes for Ubuntu <VERSION> Beta can be found at:
+
+  https://discourse.ubuntu.com/t/<LOWERCASE-FULL-NAME>-release-notes
+
+Kubuntu:
+  Kubuntu is the KDE based flavour of Ubuntu. It uses the Plasma desktop
+  and includes a wide selection of tools from the KDE project.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/kubuntu/releases/<VERSION>/beta/
+
+Lubuntu:
+  Lubuntu is a flavor of Ubuntu which uses the Lightweight Qt Desktop
+  Environment (LXQt). The project’s goal is to provide a lightweight
+  yet functional Linux distribution based on a rock-solid Ubuntu base.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/lubuntu/releases/<VERSION>/beta/
+
+Ubuntu Budgie:
+  Ubuntu Budgie is community developed desktop, integrating Budgie
+  Desktop Environment with Ubuntu at its core.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntu-budgie/releases/<VERSION>/beta/
+
+UbuntuKylin:
+  UbuntuKylin is a flavor of Ubuntu that is more suitable for Chinese
+  users.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntukylin/releases/<VERSION>/beta/
+
+Ubuntu MATE:
+  Ubuntu MATE is a flavor of Ubuntu featuring the MATE desktop
+  environment.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntu-mate/releases/<VERSION>/beta/
+
+Ubuntu Studio:
+  Ubuntu Studio is a flavor of Ubuntu that provides a full range of
+  multimedia content creation applications for each key workflow: audio,
+  graphics, video, photography and publishing.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntustudio/releases/<VERSION>/beta/
+
+Ubuntu Unity:
+  Ubuntu Unity is a flavor of Ubuntu featuring the Unity7 desktop
+  environment.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntu-unity/releases/<VERSION>/beta/
+
+Xubuntu:
+  Xubuntu is a flavor of Ubuntu that comes with Xfce, which is a stable,
+  light and configurable desktop environment.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/xubuntu/releases/<VERSION>/beta/
+
+Regular daily images for Ubuntu, and all flavours, can be found at:
+  https://cdimage.ubuntu.com
+
+Ubuntu is a full-featured Linux distribution for clients, servers and
+clouds, 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 technical support is available from Canonical Limited and
+hundreds of other companies around the world. For more information
+about support, visit https://ubuntu.com/support
+
+If you would like to help shape Ubuntu, take a look at the list of ways
+you can participate at:
+https://ubuntu.com/community/participate
+
+Your comments, bug reports, patches and suggestions really help us to
+improve this and future releases of Ubuntu. Instructions can be found
+at:
+https://help.ubuntu.com/community/ReportingBugs
+
+You can find out more about Ubuntu and about this Beta release on our
+website, IRC channel and wiki.
+
+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/beta-release-lts b/announcements/beta-release-lts
new file mode 100644
index 0000000..a919df2
--- /dev/null
+++ b/announcements/beta-release-lts
@@ -0,0 +1,143 @@
+To: [e-mail]
+Subject: Ubuntu <VERSION> (<FULL NAME>) Final Beta released
+
+The Ubuntu team is pleased to announce the Beta release of the Ubuntu
+<VERSION> LTS Desktop, Server, and Cloud products.
+
+<VERSION> LTS, codenamed "<FULL NAME>", 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, introducing new features and fixing bugs.
+
+<UPDATE FLAVOR NAMES ACCORDINGLY>
+This Beta release includes images from not only the Ubuntu Desktop,
+Server, and Cloud products, but also the Kubuntu, Lubuntu, Ubuntu
+Budgie, UbuntuKylin, Ubuntu MATE, Ubuntu Studio, Ubuntu Unity,
+and Xubuntu flavours.
+
+The Beta images are known to be reasonably free of showstopper image
+build or installer bugs, while representing a very recent snapshot of
+<VERSION> LTS that should be representative of the features intended to ship
+with the final release expected on <MONTH> <DAY>, <YEAR>.
+
+Ubuntu, Ubuntu Server, Cloud Images:
+  <ADJECTIVE> Beta includes updated versions of most of our core set of
+  packages, including a current <KERNEL VERSION> kernel, and much more.
+
+  To upgrade to Ubuntu <VERSION> LTS Beta from Ubuntu <PREVIOUS VERSION> or Ubuntu <PREVIOUS LTS VERSION>
+  LTS, follow these instructions:
+
+  https://help.ubuntu.com/community/<ADJECTIVE>Upgrades
+
+  The Ubuntu <VERSION> LTS Beta images can be downloaded at:
+
+  https://releases.ubuntu.com/<VERSION>/ (Ubuntu and Ubuntu Server on x86)
+
+  This Ubuntu Server image features the next generation Subiquity server
+  installer, bringing the comfortable live session and speedy install of
+  the Ubuntu Desktop to server users.
+
+  Additional images can be found at the following links:
+
+  https://cloud-images.ubuntu.com/daily/server/<LOWERCASE ADJECTIVE>/current/ (Cloud Images)
+  https://cdimage.ubuntu.com/releases/<VERSION>/beta/ (Non-x86)
+  https://cdimage.ubuntu.com/netboot/<VERSION>/ (Netboot)
+
+  As fixes will be included in new images between now and release, any
+  daily cloud image from today or later (i.e. a serial of <YYYYMMDD> or
+  higher) should be considered a Beta image.  Bugs found should be filed
+  against the appropriate packages or, failing that, the cloud-images
+  project in Launchpad.
+
+  The full release notes for Ubuntu <VERSION> LTS Beta can be found at:
+
+  https://discourse.ubuntu.com/t/<LOWERCASE-FULL-NAME>-release-notes/
+
+Kubuntu:
+  Kubuntu is the KDE based flavour of Ubuntu. It uses the Plasma desktop
+  and includes a wide selection of tools from the KDE project.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/kubuntu/releases/<VERSION>/beta/
+
+Lubuntu:
+  Lubuntu is a flavor of Ubuntu which uses the Lightweight Qt Desktop
+  Environment (LXQt).  The project’s goal is to provide a lightweight
+  yet functional Linux distribution based on a rock-solid Ubuntu base.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/lubuntu/releases/<VERSION>/beta/
+
+Ubuntu Budgie:
+  Ubuntu Budgie is a community developed desktop, integrating Budgie
+  Desktop Environment with Ubuntu at its core.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntu-budgie/releases/<VERSION>/beta/
+
+UbuntuKylin:
+  UbuntuKylin is a flavor of Ubuntu that is more suitable for Chinese
+  users.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntukylin/releases/<VERSION>/beta/
+
+Ubuntu MATE:
+  Ubuntu MATE is a flavor of Ubuntu featuring the MATE desktop
+  environment.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntu-mate/releases/<VERSION>/beta/
+
+Ubuntu Studio:
+  Ubuntu Studio is a flavor of Ubuntu that provides a full range of
+  multimedia content creation applications for each key workflow: audio,
+  graphics, video, photography and publishing.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntustudio/releases/<VERSION>/beta/
+
+Ubuntu Unity:
+  Ubuntu Unity is a flavor of Ubuntu featuring the Unity7 desktop
+  environment.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/ubuntu-unity/releases/<VERSION>/beta/
+
+Xubuntu:
+  Xubuntu is a flavor of Ubuntu that comes with Xfce, which is a stable,
+  light and configurable desktop environment.
+
+  The Beta images can be downloaded at:
+  https://cdimage.ubuntu.com/xubuntu/releases/<VERSION>/beta/
+
+Regular daily images for Ubuntu, and all flavours, can be found at:
+  https://cdimage.ubuntu.com
+
+Ubuntu is a full-featured Linux distribution for clients, servers and
+clouds, 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 technical support is available from Canonical Limited and
+hundreds of other companies around the world.  For more information
+about support, visit https://ubuntu.com/support
+
+If you would like to help shape Ubuntu, take a look at the list of ways
+you can participate at:
+https://ubuntu.com/community/participate
+
+Your comments, bug reports, patches and suggestions really help us to
+improve this and future releases of Ubuntu.  Instructions can be found
+at: https://help.ubuntu.com/community/ReportingBugs
+
+You can find out more about Ubuntu and about this Beta release on our
+website and wiki.
+
+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/call-for-testing-langpacks b/announcements/call-for-testing-langpacks
new file mode 100644
index 0000000..130c427
--- /dev/null
+++ b/announcements/call-for-testing-langpacks
@@ -0,0 +1,44 @@
+Hello translators!
+
+<ADDITIONAL UPDATE CONTEXT>
+
+Updated language packs are available in <CODENAME>-proposed as version
+<LANGPACK VERSION>. They will be moved to <CODENAME>-updates on <LANGPACK RELEASE DATE>
+for all languages except those languages where we identify issues with
+the proposed language packs.
+
+As a prevention measure you can help out by installing the language
+packs for your language from <CODENAME>-proposed and report here any issues
+you see which might be related to the updated translations. Then the
+language-packs for that language won't be moved to <CODENAME>-updates until
+the issues have been considered and/or resolved.
+
+The names of the language packs which have been copied to <CODENAME>-proposed are:
+
+    language-pack-XX
+    language-pack-XX-base
+    language-pack-gnome-XX
+    language-pack-gnome-XX-base
+
+where 'XX' is the language code.
+
+The purpose of a manual test is to make sure that the system keeps
+working normally and that there are no noticeable translation errors
+which stand out. So basically: log in into an Ubuntu desktop session
+and make sure that the core features behave as expected. Example check
+points:
+
+* Open the Activities overview, enter some search terms (for example
+home, netw, update).
+
+* Check the menu on the top right of the screen.
+
+* Start the file browser (Files>Home Folder). Check your home folder
+location, the menu items and the side bar.
+
+* Start Update Manager: check out it runs and has sensible UI.
+
+If you find issues, please report them here by <LANGPACK RELEASE DATE>.
+
+Thank you!
+
diff --git a/announcements/eol-imminent b/announcements/eol-imminent
new file mode 100644
index 0000000..3d1cce4
--- /dev/null
+++ b/announcements/eol-imminent
@@ -0,0 +1,30 @@
+To: [e-mail], [e-mail]
+Reply-To: [e-mail]
+Subject: <VERSION> (<CODENAME>) reaches End of Life on <EOLDATE>
+
+Ubuntu announced its <VERSION> (<CODENAME>) release almost 9 months
+ago, on <RELEASEDATE> and its support period is now nearing its
+end. Ubuntu <VERSION> will reach end of life on <EOLDATE>.
+
+At that time, Ubuntu Security Notices will no longer include
+information or updated packages for Ubuntu <VERSION>.
+
+The supported upgrade path from Ubuntu <VERSION> is via Ubuntu <VERSION+1>
+Instructions and caveats for the upgrade may be found at:
+
+https://help.ubuntu.com/community/<ADJECTIVE>Upgrades
+
+Ubuntu <VERSION+1> continues to be actively supported with security updates
+and select high-impact bug fixes. Announcements of security updates
+for Ubuntu releases are sent to the ubuntu-security-announce mailing
+list, information about which may be found at:
+
+https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce
+
+Since its launch in October 2004 Ubuntu has become one of the most
+highly regarded Linux distributions with millions of users in homes,
+schools, businesses and governments around the world. Ubuntu is Open
+Source software, costs nothing to download, and users are free to
+customise or alter their software in order to meet their needs.
+
+On behalf of the Ubuntu Release Team,
diff --git a/announcements/eol-reached b/announcements/eol-reached
new file mode 100644
index 0000000..43df8b1
--- /dev/null
+++ b/announcements/eol-reached
@@ -0,0 +1,35 @@
+To: [e-mail], [e-mail]
+Reply-To: [e-mail]
+Subject: <VERSION> (<CODENAME>) reached End of Life on <EOLDATE>
+
+This is a follow-up to the End of Life warning sent earlier to confirm
+that as of <EOLDATE>, Ubuntu <VERSION> is no longer supported. No more
+package updates will be accepted to <VERSION>, and it will be archived to
+old-releases.ubuntu.com in the coming weeks.
+
+Ubuntu announced its <VERSION> (<CODENAME>) release almost 9 months
+ago, on <RELEASEDATE> and its support period is now nearing its
+end. Ubuntu <VERSION> will reach end of life on <EOLDATE>.
+
+At that time, Ubuntu Security Notices will no longer include
+information or updated packages for Ubuntu <VERSION>.
+
+The supported upgrade path from Ubuntu <VERSION> is via Ubuntu <VERSION+1>
+Instructions and caveats for the upgrade may be found at:
+
+https://help.ubuntu.com/community/<ADJECTIVE>Upgrades
+
+Ubuntu <VERSION+1> continues to be actively supported with security updates
+and select high-impact bug fixes. Announcements of security updates
+for Ubuntu releases are sent to the ubuntu-security-announce mailing
+list, information about which may be found at:
+
+https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce
+
+Since its launch in October 2004 Ubuntu has become one of the most
+highly regarded Linux distributions with millions of users in homes,
+schools, businesses and governments around the world. Ubuntu is Open
+Source software, costs nothing to download, and users are free to
+customise or alter their software in order to meet their needs.
+
+On behalf of the Ubuntu Release Team,
diff --git a/announcements/feature-freeze b/announcements/feature-freeze
new file mode 100644
index 0000000..cb7b5b1
--- /dev/null
+++ b/announcements/feature-freeze
@@ -0,0 +1,27 @@
+To: [e-mail]
+Reply-To: [e-mail]
+Subject: <CODENAME> (to be <VERSION>) now in Feature Freeze
+
+As per the release schedule, <CODENAME> is now in Feature Freeze.
+
+Ideally, you will all now be focusing on bug fixing and not on getting new
+features into the release. However, if necessary, please follow the process
+for freeze exceptions:
+
+  https://wiki.ubuntu.com/FreezeExceptionProcess
+
+Additionally, please file your Feature Freeze Exceptions in the next week so
+that the Release Team has visibility into further changes for the release and
+can make a preliminary review of the exception request.
+
+As is the custom, packages that have been uploaded to <LOWERCASE CODENAME>-proposed prior
+to the feature freeze deadline, but have gotten stuck there, remain
+candidates for fixing between now and release.
+
+Remember that version strings don't matter for Feature Freeze. If you
+upload a new upstream release and it has no new features then you don't need
+an exception. If you add a debian/patch that adds a new feature, or enable one
+via build flags then you do. We care about the content of the archive, not
+about precisely how things got there.
+
+Happy bug squashing!
diff --git a/announcements/final-freeze b/announcements/final-freeze
new file mode 100644
index 0000000..074e857
--- /dev/null
+++ b/announcements/final-freeze
@@ -0,0 +1,39 @@
+To: [e-mail]
+Subject: <FULL NAME> (<VERSION>) Final Freeze
+
+The final freeze for <FULL NAME> has now been reached and we are heading into
+the final stretch of the release cycle with the release of Ubuntu <VERSION>
+next week.
+
+The current uploads in the queue will be reviewed and either accepted or
+rejected as appropriate by pre-freeze standards, but anything from here on
+should fit two broad categories:
+
+1) Release critical bugs that affect images, installers, or otherwise
+   can't be fixed easily post-release.
+
+2) Bug fixes that would be suitable for post-release SRUs, which we may
+   choose to accept, reject, or shunt to -proposed for 0-day SRUs on a
+   case-by-case basis.
+
+Both categories of uploads should reference bug reports in Launchpad from their
+changelog as the Ubuntu Release team may decide that the upload should follow
+the SRU process. If you suspect or want the upload to be an SRU bug please
+include the SRU template in the bug description. Additionally, if you do not
+think the SRU should age for a full seven days please provide reasoning why in
+the bug report.
+
+For unseeded packages that aren't on any media or in any supported sets,
+it's still more or less a free-for-all, but do take care not to upload
+changes that you can't readily validate before release. That is, ask
+yourself if the current state is "good enough", compared to the burden of
+trying to fix all the bugs you might accidentally be introducing with your
+shiny new upload.
+
+We will shut down cronjobs and spin some RC images over the next couple of
+days (maybe even on Friday) once the archive and proposed-migration have
+settled a bit, and we expect everyone with a vested interest in a flavour (or
+two) and with a few spare hours here and there to get to testing to make sure
+we have another uneventful release next week. Last minute panic is never fun.
+
+On behalf of the Ubuntu Release Team,
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..db2c839
--- /dev/null
+++ b/announcements/open-for-development
@@ -0,0 +1,21 @@
+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 see the release schedule page for information about any major changes
+and for all milestone dates.
+
+Please check your uploads in a <CODENAME> chroot. See [1] or [2] for details on
+how to set up such a development chroot.
+
+You can subscribe to the <CODENAME>-changes mailing list [3] to receive the 
+changelog entry of package uploads to the archive for <CODENAME>.
+
+[1] https://wiki.ubuntu.com/SimpleSbuild
+[2] https://wiki.ubuntu.com/DebootstrapChroot
+[3] https://lists.ubuntu.com/mailman/listinfo/<CODENAME>-changes
diff --git a/announcements/ui-freeze b/announcements/ui-freeze
new file mode 100644
index 0000000..f393a91
--- /dev/null
+++ b/announcements/ui-freeze
@@ -0,0 +1,15 @@
+To: [e-mail]
+Reply-To: [e-mail]
+Subject: <CODENAME> (to be <VERSION>) now in UI Freeze
+
+Effective NOW, we are officially under the User Interface Freeze for <CODENAME>:
+
+    https://wiki.ubuntu.com/UserInterfaceFreeze
+
+In order to help ensure our documentation is accurate for the release,
+please notify the documentation team and translation teams of any
+further changes to artwork, text strings, or UI designs that will be
+made between now and the release, and please make such changes only
+where necessary.
+
+On behalf of the Ubuntu Release team,
diff --git a/announcements/update-disruptions-schedule b/announcements/update-disruptions-schedule
new file mode 100644
index 0000000..81e42c1
--- /dev/null
+++ b/announcements/update-disruptions-schedule
@@ -0,0 +1,21 @@
+To: [e-mail], [e-mail],
+ [e-mail], [e-mail],
+ [e-mail]
+Subject: Planned and potentially disruptive changes for <CODENAME>
+
+Hello everyone!
+
+The release team provides a special timeline-table for disruptive
+transitions, big/major library/stack updates etc. for every release
+as part of the release schedule. This gives everyone a better
+understanding of when to expect problems and disturbances in the archive
+(as transitions are very disruptive for everyone).
+
+Would you please write down any big upcoming changes on the "Planned and
+potentially disruptive archive-wide activities" table on the current
+devel release schedule?
+
+<LINK TO SCHEDULE>
+
+Thank you!
+
diff --git a/jira-milestones/devel-release/beta-release.yaml b/jira-milestones/devel-release/beta-release.yaml
new file mode 100644
index 0000000..942fe1a
--- /dev/null
+++ b/jira-milestones/devel-release/beta-release.yaml
@@ -0,0 +1,180 @@
+milestone: "{series} Beta Release"
+timelines:
+- timeline: -10
+  tasks:
+  - task: Notify developers by mailing ubuntu-devel-announce
+    description: |
+      Things to mention
+       * Pointer to beta milestone page (in launchpad)
+       * Reminder of beta freeze
+       * Request to avoid and eliminate PackageInconsistencies
+       * Toolchain freeze begins
+  - task: Target any relevant bugs to the Beta milestone
+  - task: Review component mismatches and file any necessary main inclusion reports
+    checklist:
+    - https://ubuntu-archive-team.ubuntu.com/component-mismatches.svg
+    - https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.svg
+  - task: Clear the NBS list
+    description: |
+      Every kernel upload will create more NBS lists so keep this open until we are prepublishing
+  - task: Update metapackages for all releasing flavors
+    description: |
+      For all participating flavors download the corresponding -meta source package and run `./update`.
+      N.B. you need to have the germinate package installed to be able to use `./update`.
+      If changes are found then you need to upload the source package to the archive.
+      N.B. you need to have a version of debootstrap >= the version last used on the metapackage
+  - task: Contact the certification team to check if any critical certification bugs remain to be resolved
+    description: |
+      Ping in the MatterMost channel "~Device Certification" about any outstanding issues that need fixing for the release.
+  - task: Notify IS to remind mirrors to check free disk space
+    description: Include estimate of disk space requirements for pre-publishing the beta release.
+  - task: Notify ubuntu-translation-coordinators to coordinate a fresh set of language packs which will be exported, uploaded, and built in time for beta
+  - task: Ask design team for new default wallpaper
+  - task: Get in touch with all Ubuntu flavor leads to make sure everything is ready for Beta/Release
+    description: Check if the flavors are still participating and making sure appropriate test resources are available for milestone testing.
+- timeline: -7
+  tasks:
+  - task: Notify Ubuntu and flavour contacts to create and update their Upgrade docs
+    description: |
+      For Ubuntu the maintainer of ubuntu-release-upgrader is the point of contact.
+      The Ubuntu flavour contacts can be found in "#ubuntu-flavors" on IRC
+      Previously those were at https://help.ubuntu.com/community/{{{$release}}}Upgrades .
+  - task: Review problems and file targeted bugs for those which need resolution for the Beta
+    checklist:
+    - https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Consistency
+    - Live filesystem build failures
+    - Oversized ISOs
+  - task: Check whether translation templates (.pot files) are up-to-date
+    checklist:
+    - ubiquity
+    - ubiquity-slideshow-ubuntu
+    description: |
+      ubiquity documentation at https://wiki.ubuntu.com/Ubiquity/,
+      "Updating the translations"
+- timeline: -6
+  tasks:
+  - task: Prepare the release notes for Beta
+    description: Ensure that there is a discourse page for the release notes, that it has the usual structure and that there is a wiki.ubuntu.com redirect to it.
+  - task: Contact the Ubuntu product manager for input for the Beta release notes
+  - task: Prepare the ISO tracker for the milestone
+    description: |
+      Add a new milestone to the ISO tracker using http://iso.qa.ubuntu.com/admin/config/services/qatracker/milestones
+       * Ensure "Automatically publish" is selected (so no need to change isotracker configuration on cdimage)
+       * Confirm the new milestone is listed at http://iso.qa.ubuntu.com
+       * Confirm that it has all the images listed on the ReleaseManifest
+      Make it the default_milestone in ~cdimage/.isotracker.conf on cdimage-master, make sure that it is
+  - task: Check with the Ubuntu QA about the results of manual and automatic installation smoke tests and upgrade smoke tests
+    description: |
+      Or be proactive and check some of them yourself
+       * https://platform-qa-jenkins.ubuntu.com/view/upgrade/
+       * https://platform-qa-jenkins.ubuntu.com/view/iso%20desktop/
+       * https://platform-qa-jenkins.ubuntu.com/view/server-$LETTER/
+  - task: Discuss with IS anticipated sizes of ISO images and determine if any mirroring issues
+    description: |
+      Look at the size_limit function in
+      https://git.launchpad.net/ubuntu-cdimage/tree/lib/cdimage/tree.py for all the
+      maximum sizes for the devel release.
+- timeline: -3
+  tasks:
+  - task: Put the archive into pre-release freeze state
+    description: Requires pinging IS.
+  - task: "Ping someone who can set the topic to Beta Freeze on the #ubuntu-devel and #ubuntu-release irc channels"
+    description: "In #ubuntu-devel this needs to be done by an IRC operator e.g. bdmurray, paride, sil2100, or vorlon. In #ubuntu-release this can be done by any ubuntu member. 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."
+  - task: email ubuntu-devel-announce regarding the Beta Freeze
+    description: The email will need to be accepted by a moderator.
+  - task: Enable the cronjob for auto-accepting unseeded uploads on ubuntu-archive-toolbox
+    description: |
+      Requires someone who can 'sudo -u ubuntu-archive' on ubuntu-archive-toolbox to uncomment the auto-accept cronjob
+  - task: Add a freeze block
+    description: |
+      In a local checkout of hints-ubuntu, run generate-freeze-block <list of flavours> > freeze
+      generate-freeze-block comes from lp:ubuntu-archive-tools
+      e.g. generate-freeze-block ubuntu ubuntukylin kubuntu xubuntu ubuntu-budgie ubuntu-mate ubuntu-unity lubuntu ubuntu-server ubuntustudio ubuntu-base ubuntucinnamon edubuntu > freeze
+  - task: Selectively accept package uploads to resolve targeted bugs
+  - task: Double-check the archive state
+    checklist:
+    - https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Consistency
+    - Live filesystem build failures
+    - Pending main promotions
+  - task: Check archive rebuild test results
+    description: Ping the Toolchain team member responsible for this.
+  - task: Stop all live filesystem and cdimage cron jobs
+  - task: Modify debian-cd/CONF.sh by setting OFFICIAL to "Beta"
+  - task: Produce full set of images
+    description: |
+      This can be done by visiting the milestone page in the ISO tracker and selecting
+      products and or images and clicking the "Update rebuild status" button after ensuring
+      "Request a rebuild" is selected in the dropdown box.
+  - task: Notify Ubuntu QA team to begin release validation
+  - task: Notify Certification team to begin hardware certification
+    description: Ping Jonathan Cave and Paul Larson regarding this
+  - task: If the series is an LTS, ask Certification QA to begin testing on certified hardware
+  - task: Request input for the beta announcement from the leads of the flavors
+      The Ubuntu flavour contacts can be found in "#ubuntu-flavors" on IRC
+- timeline: -2
+  tasks:
+  - task: Update the release notes with the changes for this release
+    description: |
+     * Work with development leads to make sure that highlights of changes since last milestone, are overviewed.
+     * Work with QA team(s) to make sure that any caveats and warnings present in the image are documented.
+  - task: Prepare the release announcement email
+    description: For cloud images, remember to write to use the daily images equal or newer than the images we have built for other flavors.
+  - task: Review beta-targeted bugs and take final decisions on what to fix and what to defer
+    description: Find the bugs by searching for bugs targetted to the milestone e.g. ubuntu-23.10-beta
+- timeline: -1
+  tasks:
+  - task: Update release notes with the bugs found from testing that are not going to be fixed
+  - task: Pre-publish the CD images
+    description: |
+      ./publish-image-set --milestone "$RELEASE $MILESTONE" --prepublish (from lp:ubuntu-archive-tools) will print the necessary commands.
+      N.B. you need a ~/.isotacker.conf to be able to run publish-image-set on your local system
+      In case simplestream generation misbehaves, run the commands with `export SIMPLESTREAMS=0`.
+- timeline: 0
+  tasks:
+  - task: Review the testing status of images and ensure all have been tested before being released
+    description: This means checking the ISO tracker
+  - task: Archive any previous milestone images to old-images
+  - task: Disable mirror syncing on cdimage-master
+    description: ... 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 need to edit cdimage/www/simple/HEADER.html and cdimage/www/simple/.htaccess by hand to add an entry for the new beta release.
+      In case simplestream generation misbehaves, run the commands with `export SIMPLESTREAMS=0`.
+  - task: copy .manifest to .manifest.full
+    description: In cdimage/www/simple/ copy .manifest to .manifest.full, pruning all images from previous releases from the .manifest file to allow timely mirror probing
+  - task: Re-enable mirror-syncing
+    description: ...by removing /srv/cdimage.ubuntu.com/etc/STOP_SYNC_MIRRORS
+  - 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: "Update the topic on #ubuntu-devel and #ubuntu-release"
+    description: |
+      Let people know what type of freeze we are currently in or not in
+      "In #ubuntu-devel this needs to be done by an IRC operator e.g. bdmurray, paride, sil2100, or vorlon. In #ubuntu-release this can be done by any ubuntu member. 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."
+  - task: For a "Final Beta" send the release announcement to ubuntu-announce
+  - task: Post announcement to Launchpad
+    description: |
+      (ubuntu-drivers members have posting rights)
+       * Use ubuntu-announce email subject as Headline
+       * Use the mailing list archive URL for the ubuntu-announce email as the URL
+  - task: Change default_milestone in ~cdimage/.isotracker.conf back to "Daily"
+  - task: Mark the milestone Released on the ISO tracker
+    description: This is done in the milestone section of the administrative interface
+  - task: Deactivate beta milestone in Launchpad
+    description: |
+      Use deactivate-milestones from ubuntu-archive-tools to deactivate the milestone
+  - task: Turn live filesystem and cdimage cron jobs back on
+- timeline: 1
+  tasks:
+  - task: Modify debian-cd/CONF.sh by setting OFFICIAL to "Daily"
+  - task: Call for translations
+    checklist:
+    - Send to [e-mail]
+    - Reminder of deadlines for both langpackable and non-langpackable translations
+    - Include current translation statistics
+  - task: If this will be an LTS release, notify ubuntu-devel-announce of any special post-release support plans, such as point releases
+  - task: If any changes were made to this document in this run, check whether the changes also apply to the other release process documents as well
+  - task: Remove the freeze block from britney.
+  - task: Change daily builds to comment out any architectures that have not been tested during this point (that we are not releasing)
diff --git a/jira-milestones/devel-release/feature-freeze.yaml b/jira-milestones/devel-release/feature-freeze.yaml
new file mode 100644
index 0000000..5b58585
--- /dev/null
+++ b/jira-milestones/devel-release/feature-freeze.yaml
@@ -0,0 +1,17 @@
+milestone: "{series} Feature Freeze"
+timelines:
+- timeline: 0
+  tasks:
+  - task: Send out Feature Freeze notification e-mail to ubuntu-devel-announce
+    description: Remember to request moderation of the e-mail by the list moderators.
+  - task: "Update the topic on #ubuntu-devel and #ubuntu-release"
+    description: |
+      "In #ubuntu-devel this needs to be done by an IRC operator e.g. bdmurray, paride, sil2100, or vorlon. In #ubuntu-release this can be done by any ubuntu member. 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."
+  - task: Stop auto-syncs from Debian as part of Debian Import Freeze
+    description: |
+      To implement this freeze, somebody with access to the ubuntu-archive user on ubuntu-archive-toolbox.internal should comment out the auto-sync entry in its crontab.
+  - task: Notify release team members to start periodically scanning for FFe bugs
+    description: >
+      Keeping a look-out on 
+      https://bugs.launchpad.net/bugs/+bugs?field.searchtext=FFe&search=Search%20Bug%20Reports&field.scope=all&field.scope.target=&orderby=-id&start=0 
+      is a good way to start.
diff --git a/jira-milestones/devel-release/final-release.yaml b/jira-milestones/devel-release/final-release.yaml
new file mode 100644
index 0000000..357e38c
--- /dev/null
+++ b/jira-milestones/devel-release/final-release.yaml
@@ -0,0 +1,195 @@
+milestone: "{series} Final Release"
+timelines:
+- timeline: -14
+  tasks:
+  - task: NonLanguagePackTranslationDeadline, ensure uploads with updated translations downloaded from Rosetta are done
+    description: "For DDTP update procedures, see: https://bazaar.launchpad.net/~mvo/apt-ddtp-tools/trunk/view/head:/UbuntuChecklist"
+    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
+    description: |
+      Bootstrap entries are added to the script to build i386 binaries
+      before they can be seeded.  Bootstraps should finish within a cycle with
+      no carry-overs.
+    checklist:
+    - find bootstrap entries in the script
+    - remove them
+    - rerun the script
+    - verify that there are no changes to the seed as a result
+    - if there are changes to the seed, figure out why
+    - commit
+  - 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: |
+      Ask the web team to review Release Manifest.
+  - task: Check ubuntu-release-upgrader for discrepancies with seeded snaps
+    description: |
+      The release upgrade process should install any snaps which are seeded in the release being upgraded to. Check that the deb2snap.json file contained in ubuntu-release-upgrader has the same snaps as the seeds.
+  - 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: -9
+  tasks:
+    - 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: Check to see if python-apt has been uploaded recently
+      description: If not, upload a new version after running pre-build.sh as that generates the updated lists of mirrors.
+    - task: Check to see if ubuntu-release-upgrader have been uploaded recently
+      description: If not, upload a new version after running pre-build.sh as that generates the updated lists of mirrors.
+- 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: 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
+      description: |
+        The report can be found at https://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html and the goal is to ensure there are no packages listed in the unsubscribed section. The report is created on cranberry (with data from package-subscribers from ubuntu-archive-tools) under the ubuntureports user but bdmurray is the best point of contact.
+- timeline: -3
+  tasks:
+    - task: Update base-files and 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: Add a freeze block
+      description: |
+        In a local checkout of hints-ubuntu, run generate-freeze-block <list of flavours> > freeze
+        generate-freeze-block comes from lp:ubuntu-archive-tools
+        e.g. generate-freeze-block ubuntu ubuntukylin kubuntu xubuntu ubuntu-budgie ubuntu-mate ubuntu-unity lubuntu ubuntu-server ubuntustudio ubuntu-base ubuntucinnamon edubuntu > freeze
+    - task: Ensure that the ISO tracker lists the new milestone with the "publish from manifest" flag set
+    - task: Produce a full set of images
+      description: |
+        This can be done by visiting the milestone page in the ISO tracker and selecting
+        products and or images and clicking the "Update rebuild status" button after ensuring
+        "Request a rebuild" is selected in the dropdown box.
+    - task: Check the volume labels on ISO's for all architectures (cdimage/debian-cd/CONF.sh, OFFICIAL variable)
+      description: |
+        Sample command that works as non-root on cdimage-master (note that you will have to change the release names as appropriate):
+        `$ for img in */daily*/current/*.iso; do case $img in *jammy*|*focal*) continue ;; esac; echo $img; xorriso -dev $img -osirrox on -extract /.disk/info /tmp/diskinfo >/dev/null 2>&1 && cat /tmp/diskinfo && echo && rm -f /tmp/diskinfo ;done`
+        Ensure there are no out-of-date images whilst going through the diskinfo content.
+    - task: Clear the NBS list
+      description: |
+        Every kernel upload will create more NBS lists so keep this open until we are prepublishing
+    - task: Notify Hardware Certification team to begin certification testing (devices, OEM)
+      description: |
+        We need to make sure all certified devices are tested. This means not only the devices like Pi, but also OEM devices (desktops, laptops).
+    - task: Notify Ubuntu QA to begin ReleaseValidationProcess
+    - task: Prepare the release announcement
+      description: |
+        Once the document based on the existing template is ready, we reach out to PM (generally, Oliver Smith (@local-optimum)) to review the middle section to ensure everything is still relevant.
+    - 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
+- 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.
+        In case simplestream generation misbehaves, run the commands with `export SIMPLESTREAMS=0`.
+    - 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 cdimage-master to push out the pre-published file structure
+    - task: Review on the staging server the feature walk through on the website (web-team)
+      description: |
+        We generally ask the web team to stage the web page on a server and then review the content (ourselves) to ensure it's all expected and good to go.
+    - 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 cdimage-master, 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.
+        In case simplestream generation misbehaves, run the commands with `export SIMPLESTREAMS=0`.
+    - task: "Ping CPC using cpc-help keyword in #ubuntu-release to start the process of building and publishing cloud images"
+    - task: If the new release is an LTS, 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 at https://launchpad.net/ubuntu/+cdmirrors
+        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"
+      description: "In #ubuntu-devel this needs to be done by an IRC operator e.g. bdmurray, paride, sil2100, or vorlon."
+    - 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. The latter by using refresh_os_list.) in the bzr branch. N.B. meta-release-lts and meta-release-lts-proposed are 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: Notify web team to announce on the website
+    - task: Send the release announcement to ubuntu-announce
+    - task: Disable the auto-accept script from ubuntu-archive-toolbox's crontab
+    - task: Notify a Launchpad admin to set the status of this distrorelease to CURRENT, and to change any previous CURRENT distrorelease(s) to SUPPORTED
+      description: Be sure to check if there's no packages still in the middle of publishing before proceeding.
+    - task: Deactivate release milestone in Launchpad
+      description: |
+        Use deactivate-milestones from ubuntu-archive-tools
+    - task: Post announcement to News & Announcements section of discourse (forum admins have posting rights)
+      description: |
+        Close the topic so that it cannot be commented on
+    - task: Post announcement to Launchpad
+      description: |
+        (ubuntu-drivers members have posting rights)
+         * Use ubuntu-announce email subject as Headline
+         * Use the mailing list archive URL for the ubuntu-announce email as the URL
+    - 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: Decide if a retrospective / post-mortem is necessary
+      description: |
+        Create a google doc for the post-mortem and arrange meetings as appropriate
+    - 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
diff --git a/jira-milestones/devel-release/new-cycle-opening.yaml b/jira-milestones/devel-release/new-cycle-opening.yaml
new file mode 100644
index 0000000..588e694
--- /dev/null
+++ b/jira-milestones/devel-release/new-cycle-opening.yaml
@@ -0,0 +1,272 @@
+milestone: "{series} Archive Opening"
+timelines:
+- timeline: -14
+  tasks:
+  - task: create OLDRELEASE hints-ubuntu and hints-ubuntu-kernel branches for britney
+    description: >
+      lp:~ubuntu-release/britney/+git/hints-ubuntu
+      lp:~ubuntu-kernel-release/britney/+git/hints-ubuntu
+  - 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, described at
+      https://wiki.canonical.com/InformationInfrastructure/IS/ISO/UbuntuMailingLists?action=show&redirect=InformationInfrastructure%2FSA%2FListCreation#Ubuntu.27s_.3Crelease.3E-changes_lists
+  - task: Create a release schedule in the release category on discourse
+    checklist:
+    - Use generate-release-schedule-markdown CODENAME PREVIOUS_RELEASE_DATE 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: Update the https://wiki.ubuntu.com/Releases table with the new release
+  - 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 (Release Notes, Release Schedule), 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: Notify the autopkgtest infra maintainers to run through https://autopkgtest-cloud.readthedocs.io/en/latest/administration.html#opening-up-a-new-series
+    description: This will take hours so get it started ASAP
+  - task: Notify the Ubuntu QA team to submit an RT about adding images for the new release
+    description: "The Ubuntu QA should do this as it'll be easier for them to prioritize. Example ticket: https://portal.admin.canonical.com/C154790"
+  - task: Notify the Ubuntu QA team to submit a Salesforce ticket about adding images for the new release
+    description: |
+      This is necessary for PS5 which is managed by bootstack. N.B. Brian Murray may the only person who can do this as of October 2023.
+      1. Go to https://canonical.lightning.force.com and login.
+      2. Search `Canonical - IS` and select the account with the same name.
+      3. Under the account header, there are a few quick links like `Related Contacts`, `Account Team`, etc. Select `Assets`.
+      4. In the assets list, select `Operations-Canonical--39991231-UA-BootStackSupport`.
+      5. Under the asset header, select the `Cases` quick link. ([direct link?](https://canonical.lightning.force.com/lightning/r/Asset/02i4K000001XbSvQAK/related/Cases/view))
+      6. In the cases header, select the `New` button.
+      7. A `New Case` modal will pop up. Select the `Support Case` radio option and click the `Next` button.
+      8. Fill in all relevant information, substitute yourself under `Contact Name`, set `Canonical Internal` for `Case Origin`, and finally ensure the `Bootstack Case` option is selected under `Escalation Details`.
+  - task: Edit (cowboy) bin/run-proposed-migration on ubuntu-archive-toolbox 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 ubuntu-archive-toolbox:~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 branches on Launchpad
+    description: >
+      The branch-seeds script in lp:ubuntu-archive-tools can do the hard work here.
+      TODO: step 1 is a whole lot of manual bullshit. Refactor branch-seeds
+      and update-seeds to make this automatic.
+    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 ubuntu-archive-toolbox 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 Driver forward
+  - task: Notify a Tech Board member to copy forward the Release Manager setting between series
+  - 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. Check with a Launchpad admin to confirm that this has finished 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: Reject from accepted queue all custom signing, uefi, and raw-installer uploads
+    description: >
+      Reject all signing, uefi, and raw-installer requests from the
+      accepted queue, using either webui or the queue tool. Initial
+      fresh publication of new series, results in custom uploads copies
+      from previous series into new ones. All of them are useless and
+      wrong. These copies do not consult neither source nor binary
+      publishing history and thus copy signing requests for obsolete and
+      removed binaries. There is no value in having them in the release
+      pocket, and it is impossible to reject them at any other time.
+  - 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
+    description: >
+      Visit https://bugs.launchpad.net/ubuntu/+manage-official-tags
+  - 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@ubuntu-archive-toolbox, 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 (cnf, dist-upgrader-all, and i18n) are missing from dists/NEWRELEASE/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: Run branch-chdist NEWRELEASE on ubuntu-archive-toolbox to initialize chdist configs for the new series
+  - task: Copy the pending syncs which we didn’t want to accept from previous-proposed UNAPPROVED, and then reject them
+  - task: Update lp:~ubuntu-release/britney/britney1-ubuntu/ with the new DEFAULT_SERIES
+  - task: Once autopkgtest is ready, finish the britney initialization
+    checklist:
+    - on ubuntu-archive-toolbox, 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 bin/run-proposed-migration cowboy (an exit 0 to the ubuntu/$DEFAULT_SERIES case branch), 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 ubuntu-archive-toolbox to use the new series, so the chroots can reference it
+  - task: As [e-mail], run /srv/launchpad.net/production/launchpad/scripts/add-missing-builds.py -s NEW-proposed plus -a ARCH for each architecture in NEW
+    description: AAs no longer have access; ask IS.
+  - task: Ask Launchpad developers to update the "devel" snap base (and, if relevant, any unreleased "coreXX" snap base) to refer to the new release
+    description: >
+      The "devel" snap base is set up to refer to the latest series (see
+      https://bugs.launchpad.net/launchpad/+bug/2012405), but this needs to
+      be kept up to date manually. While a new core version is being
+      prepared, the corresponding snap base works similarly (e.g. "core24"
+      created in July 2023 initially pointing to mantic), though this
+      shouldn't be updated past the corresponding LTS.
+    checklist:
+    - 'Launchpad developers can do something like this in `lp-shell production`: `base = lp.snap_bases.getByName(name=\"devel"); base.distro_series = "/ubuntu/NEWRELEASE"; base.lp_save()`'
+  - 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 ubuntu-archive-toolbox (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 /etc/madison-lite/config on ubuntu-archive-toolbox-frontend so that rmadison starts working
+  - task: Notify someone in the 'prod-merges-ubuntu-com' LDAP group to set up merge-o-matic to point to the new distroseries
+    description: >
+      `ssh -t foundations-bastion-ps5.internal sudo -iu prod-merges-ubuntu-com`, `juju ssh ubuntu/1`, 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 distro-info-data is needed to build the livefs builds.
+    checklist:
+    - Update distro-info-data for the new series and once it is in -updates ask an AA to fully phase the update.
+    - 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.
+    - 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://ubuntu-archive-team.ubuntu.com/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"
+  - 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] Delete the packages 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@ubuntu-archive-toolbox'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 listed in the product manifests available from the ISO Tracker (https://iso.qa.ubuntu.com/).
+    checklist:
+    - "Get the list of seeded snaps from the seeds: `readarray -t seeded_snaps < <(grep -ohP '(?<=snap:)[^\s/]*' * 2>/dev/null | sort -u)`"
+    - '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.
+  - 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 "Daily".
+  - task: Adjust cdimage code to be aware of the new release
+    description:
+      Example - https://git.launchpad.net/ubuntu-cdimage/commit/?id=bc6458bae0fb36403534c37c8775367044af1bd1
+  - task: On cdimage-master configure ~cdimage/.isotracker.conf, including default_milestone
+  - task: Notify vorlon or bdmurray to run branch-series OLDSERIES NEWSERIES as [e-mail] (the ISO tracker database)
+    description: >
+      Series names are given as the adjective with initial cap, consistent
+      with the series naming in the ISO tracker.  Confirm that the new series
+      has a manifest in the ISO tracker administrative interface.
+  - task: Target to series (the new release) bugs from the previous release's release notes to be fixed
+  - 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 (so anybody can check but [ldap:[e-mail]] can debug) 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: Update Debian's udd config for the new series
+    description: |
+      The update looks like https://salsa.debian.org/qa/udd/-/merge_requests/48 and will update multiple Debian reports to track Ubuntu's current devel release. Usually done by Mattia Rizzolo.
+  - task: Update lp:ubuntu-manpage-repository/production for the new release codename
+    description: >
+      Add the release, and submit an RT to have the server updated
+      IS's instructions - https://wiki.canonical.com/InformationInfrastructure/ISO/Manpages/Update
+      Example RT - https://portal.admin.canonical.com/C157256/
+  - 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) [Don't bother using the codename because that creates unnecessary work later.]
+  - task: Notify someone with access to the "prod-cnf-extractor-ps5" environment on ubuntu-release-bastion-ps5 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 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: Update meta-release-development to handle the new release
+    description: >
+      Update the appropriate meta-release-development files in the bzr branch.
+      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: Begin Upgrade Testing Process
+    description: "Details can be found here: https://wiki.ubuntu.com/UpgradeTestingProcess"
+  - task: Notify ubiquity maintainer(s) to run debian/rules update, adjust as necessary to account for changes, and upload
+  - task: If the previous release is not LTS, move the daily milestone for this release from "Testing" to "Released"
+    description: http://iso.qa.ubuntu.com/admin/config/services/qatracker/milestones
+  - task: Notify Ubuntu QA ([e-mail]) to set up Utah jobs for the new release
+    description: |
+      The Ubuntu QA team will add the new release to the jenkins-job-builder YAMLs here:
+      https://git.launchpad.net/qa-jenkins-jobs/tree/jobs/iso-testing
+  - 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: Update download links in the ISO Tracker
+    description: |
+      If the previous release was an LTS then the download links for the daily builds of that release need to be updated in the ISO tracker.
+      This is done on iso-qa-ubuntu.internal with `INSERT INTO qatracker_product_download (productid, seriesid, filename, path, type) (SELECT productid, NEWSERIES, filename, path, type FROM qatracker_product_download WHERE seriesid=OLDSERIES);` after finding the NEWSERIES and OLDSERIES by examining URLs at the ISO tracker.
+  - task: Update rls reports on cranberry for the new release
+    description: |
+      Notify Brian Murray, or some other member of ubuntu-reports, to create rls reports on cranberry. Basically, copy the run-kk-reports.sh script (location findable via the crontab) to run-ll-reports.sh and modify the release name and tag in the new script. Copy rls-kk-*.json files to rls-ll-*.json and again replace the release name and tag. Additionally, clear the contents of the tasks dictionary in the json file.
+  - task: Update Ubuntu metrics for the new release
+    description: |
+      Once the new rls reports are created and the images_collecor.py script has run, which it does hourly, you can proceed. In the dashboard settings, navigate to variables and the release variable. Then click update and you should see the new release code name in the "Preview of values". After that navigate to the JSON Model (still in dashboard settings) and change the templating -> list -> current -> text and value to the new release name. (That is the default value for the Ubuntu Release drop down on the main page.)
+  - 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. While you are
+      at it create a discourse post with the release schedule for the next release.
+  - task: Make sure that all incoming milestones for the release are carded and assigned to respective release team members
+  - task: Add automatic upgrade testing profiles
+    description: See https://git.launchpad.net/auto-upgrade-testing-specifications/commit/?id=011aee694e6fa6e29c10cd08f1d5ae02f92a9946 as an example.
+  - task: Send out request to team leads and Ubuntu developers to plan out known disruptive releases for the series on the Release Schedule
+    description: There is a sub-table on the release schedule for planned and potentially disruptive archive-wide activities.
diff --git a/jira-milestones/devel-release/user-interface-freeze.yaml b/jira-milestones/devel-release/user-interface-freeze.yaml
new file mode 100644
index 0000000..e5e5b1c
--- /dev/null
+++ b/jira-milestones/devel-release/user-interface-freeze.yaml
@@ -0,0 +1,11 @@
+milestone: "{series} User Interface Freeze"
+timelines:
+- timeline: 0
+  tasks:
+  - task: Send out User Interface Freeze notification e-mail to ubuntu-devel-announce
+    description: Remember to request moderation of the e-mail by the list moderators.
+  - task: "Update the topic on #ubuntu-devel and #ubuntu-release"
+    description: |
+      Let people know what type of freeze we are currently in or not in
+      "In #ubuntu-devel this needs to be done by an IRC operator e.g. bdmurray, paride, sil2100, or vorlon. In #ubuntu-release this can be done by any ubuntu member. 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."
+  
diff --git a/jira-milestones/end-of-life.yaml b/jira-milestones/end-of-life.yaml
new file mode 100644
index 0000000..9f30389
--- /dev/null
+++ b/jira-milestones/end-of-life.yaml
@@ -0,0 +1,141 @@
+
+- timeline: -45
+  duedate: 3
+  tasks:
+  - task: Send Release End of Life Warning to ubuntu-announce, ubuntu-security-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: -9
+  duedate: 0
+  tasks:
+  - task: Clean up things before setting release to OBSOLETE in Launchpad, as otherwise removals are not actually published
+    checklist:
+    - "NBS: cleanup-NBS-for-EOL"
+    - New queue
+    - "[~ubuntu-sru] Clean up items in the Unapproved queue"
+    - "[~ubuntu-archive] Packages in -proposed (Any packages in -proposed which are just autopkgtest fixes should be removed from -proposed.)"
+    - "[~ubuntu-archive] Check for any updates which are phasing and decide if they should be fully phased or the changes reverted"
+- timeline: 0
+  duedate: 7
+  tasks:
+  - task: DO NOT PROGRESS BEYOND THIS POINT BEFORE THE ABOVE IS DONE
+  - 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"
+    - Update the web server - `ssh -i ~/.ssh/id_rsa_autodeploy_trigger [e-mail] /usr/bin/autodeploy-trigger prod-ubuntu-web-frontends refresh-changelogs` as ubuntu-release@foundations-bastion-ps5
+  - task: Update lp:ubuntu-manpage-repository/production
+    description: >
+      Remove the release, and submit an RT to have the server updated
+      IS's instructions - https://wiki.canonical.com/InformationInfrastructure/ISO/Manpages/Update
+      Example RT - https://portal.admin.canonical.com/C157256/
+  - task: Deactivate any milestones for the release
+    description: >
+      Use `deactivate-milestones` from ubuntu-archive-tools to set all of them to inactive e.g. `deactivate-milestones -s lunar`.
+  - task: Archive the release on old-releases on cdimage-master
+    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, /srv/cdimage.ubuntu.com/www/simple/.manifest, /srv/cdimage.ubuntu.com/www/simple/.manifest.full  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 RELEASE directory to the corresponding (i.e. FLAVOR) /releases/ 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: "[~ubuntu-archive] 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.
+      N.B. The order of operations is important as if you remove the images before the removing the release from the service bundle the images can be recreated.
+    checklist:
+    - Edit mojo/service-bundle in lp:autopkgtest-cloud to remove the release, then run mojo run on the bastion host
+    - Remove the images (in all cloud regions, run something like glance image-list | awk -F '| ' '/adt\/ubuntu-$RELEASE/ { print $2 }' | xargs glance image-delete.
+    - 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-ps5" environment on ubuntu-release-bastion-ps5 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
+    description: >
+      Submit an RT similar to https://rt.admin.canonical.com/Ticket/Display.html?id=161890 telling them the images can be removed.
+  - task: Manually remove the release from ubuntu-archive-toolbox-frontend.internal:/etc/madison-lite/config so it doesn't show up in rmadison output
+  - task: As ubuntu-archive on ubuntu-archive-toolbox.internal, 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 ~/.chdist/RELEASE*"
+  - task: Clear all packages from the partner repository for this release with remove-package (check with PES first)
+    description: The last release this is relevant for is jammy.
+  - task: Send EndOfLifeAnnouncement to ubuntu-announce, ubuntu-security-announce
+  - task: Update the main page of wiki.ubuntu.com by removing the release from the Releases table
+  - task: Update https://wiki.ubuntu.com/Releases for Canonical support
+  - 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: >
+      Ask brian, seb128, or vorlon to do the following - 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: Remove the series name from the official Launchpad bug tags, and remove verification-needed-$SERIES and verification-done-$SERIES where $SERIES is the name of the EoL series
+    description: >
+      Visit https://bugs.launchpad.net/ubuntu/+manage-official-tags
+  - task: Remove automatic upgrade testing profiles
+    description: See https://git.launchpad.net/auto-upgrade-testing-specifications/commit/?id=5cb8276dd9a41df796914a0a82bc7a39572e0d19 as an example
+  - 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/esm-switch.yaml b/jira-milestones/esm-switch.yaml
new file mode 100644
index 0000000..f324bae
--- /dev/null
+++ b/jira-milestones/esm-switch.yaml
@@ -0,0 +1,42 @@
+milestone: "{series} ESM switch"
+timelines:
+- timeline: -45
+  duedate: 3
+  tasks:
+  - task: Send Release End of Life and ESM switch warning to ubuntu-announce, ubuntu-security-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 move the release to ESM
+- 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 for the release before officially going ESM
+    checklist:
+    - NBS: cleanup-NBS-for-EOL
+    - New queue
+    - Unapproved queue
+    - Packages in -proposed (but leave block-proposed autopkgtest-fix SRUs in -proposed)
+    - Check for any updates which are phasing and decide if they should be fully phased or the changes reverted
+  - task: Update lp:ubuntu-manpage-repository/production
+    description: >
+      Remove the release, and submit an RT to have the server updated
+      IS's instructions - https://wiki.canonical.com/InformationInfrastructure/ISO/Manpages/Update
+      Example RT - https://portal.admin.canonical.com/C157256/
+  - 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: 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: Clear all packages from the partner repository for this release with remove-package (check with PES first)
+    description: The last release this is relevant for is jammy.
+  - task: Send EndOfLifeAnnouncement to ubuntu-announce, ubuntu-security-announce
+  - task: Update the main page of wiki.ubuntu.com by removing the release from the Releases table
+  - task: Update https://wiki.ubuntu.com/Releases for Canonical support, add to ESM
+  - task: Remove /srv/cdimage.ubuntu.com/scratch/*/RELEASE to free up disk space
+
diff --git a/jira-milestones/point-release.yaml b/jira-milestones/point-release.yaml
new file mode 100644
index 0000000..6b643db
--- /dev/null
+++ b/jira-milestones/point-release.yaml
@@ -0,0 +1,157 @@
+- 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
+    description: If not, upload a new version after running pre-build.sh as that generates the updated lists of mirrors.
+  - task: Check to see if ubuntu-release-upgrader have been uploaded recently
+    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
+  - task: Notify any flavors about oversized images and check whether they want to remove contents from images or raise the limits
+- 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.
+  - task: Notify any flavors about still oversized images and check whether they want to remove contents from images or raise the limits
+- 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: Set the -updates pocket in SRU freeze
+    description: This can be done by creating a sru-freeze file on the right series branch of lp:~ubuntu-release/britney/+git/hints-ubuntu
+  - 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 cdimage-master
+    - 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@ubuntu-archive-toolbox:~$ 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 cdimage-master 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 cdimage-master 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: 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: Update the appropriate meta-release files
+    description: >
+      Update all the meta-release files (including raspi/os_list_imagingutility_ubuntu.json by using refresh_os_list) in the bzr branch.
+      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: 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
+  - task: Update the https://wiki.ubuntu.com/Releases table with the new release
+  - task: Disable the SRU freeze for the series
+    description: This can be done by removing the sru-freeze file from the right series branch of lp:~ubuntu-release/britney/+git/hints-ubuntu
+- 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