Merge ~andersson123/ubuntu-release-tools/+git/templates:a-u-c-release-cards-more-verbose into ~ubuntu-release/ubuntu-release-tools/+git/templates:main

[Tim Andersson]

[Brian Murray (brian-murray)]

I would prefer that the actions are all checklist items so that other people can carry on with the card if necessary e.g. seed-new-release and download-all-results should both be checklist items.

review: Needs Fixing

[Tim Andersson (andersson123)]

amended, please re-review

[Brian Murray (brian-murray)]

I've merged this but separated seed-new-release and download-all-results into two separate checklist items. Additionally, I modify the auto-sync images RT line so that we submit an RT for each database because we might still be using scalingstack?

diff --git a/jira-milestones/devel-release/new-cycle-opening.yaml b/jira-milestones/devel-release/new-cycle-opening.yaml
index a39ae54..421973a 100644
--- a/jira-milestones/devel-release/new-cycle-opening.yaml
+++ b/jira-milestones/devel-release/new-cycle-opening.yaml
@@ -26,10 +26,24 @@ timelines:
       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 Release Management team to open up autopkgtest.ubuntu.com for the new series
+    description: |
+      Any autopkgtest admin can carry out the tasks in this checklist. They should be done in the order specified in this card.
+      More details here: https://autopkgtest-cloud.readthedocs.io/en/latest/administration.html#opening-up-a-new-series
+      r.e. seed-new-release:
+      This script should take about half a day.
+      seed-new-release copies over recent successes or migration-reference/0 runs for every package to the new release container in swift, from the previous release.
+      Once seed-new-release is finished, run autopkgtest-cloud/charms/focal/autopkgtest-web/webcontrol/download-all-results to place these "new" results in swift into the db.
+
+      r.e. hacking the new release into /usr/share/distro-info/ubuntu.csv:
+      This is done by using autopkgtest-cloud/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/tools/update_ubuntu_csv on the bastion. The script is self explanatory.
+    checklist:
+      - run seed-new-release and download-all-results
+      - Hack the new release into /usr/share/distro-info/ubuntu.csv
+      - Build adt images on all datacentre/arch combinations
+      - Add the new release to the service-bundle/juju config (and deploy said config)
+      - Run tests for the new release on every architecture, and check that the results are sensible.
+      - Submit an RT for adding auto-sync images for all datacentre/arch combinations. Example ticket here 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.