Two weeks before release day:

1. Announce internally that any last minute changes should be done as soon as possible.
2. File the megatask for the upcoming release's blockers.
3. Go through the release blocker list for this cycle and punt non-RC tasks to next cycle.
4. Inform the Calamares upstream contact that we plan on doing a release in two weeks. Discuss whether any important patches should be cherry-picked, and get those uploaded as soon as possible. Ask them nicely to ping you in the next two weeks if anything important comes up.
5. Talk to the Lubuntu Documentation Team about what needs to be wrapped up for next release. Nicely remind them that the release is in two weeks.

A week before release day:

1. Update the downloads page and the homepage for the new release in a draft, so they can be published on release day.
2. Do one final check of the testing checklist and send out a call for testers.
3. Start drafting a blog post for the release.
4. Gather known bugs from Launchpad and the ISO QA tracker (possibly automate this) to put on the blog post.

After ISOs have been released:

1. Publish the blog post and the downloads/homepage drafts.
2. Post on social media:
3. Twitter or Mastodon (publishing to one published to the other).
4. r/Lubuntu and r/Ubuntu.
5. Facebook page and Facebook group.
6. IRC topics for #lubuntu, #lubuntu-devel, and #lubuntu-offtopic on freenode.
7. Announce on the lubuntu-users and lubuntu-devel mailing lists.
8. Scan social media and see if anyone is pointing out any reproducible bugs that we can file.

After the codename is announced and base-files is uploaded:

1. File a task about a new wallpaper and slideshow for the upcoming release.
2. Change update.cfg in lubuntu-meta and the branding as well as the desktop file in calamares-settings-ubuntu.
3. Make sure repo-list is up-to-date and run setup-phab in this repo. The production values can be found in the internal setup document.
4. Someone with access to GitHub should update the default branches for the mirrored repositories.
5. Update the CI to enable builds for the new release:
6. In ci.conf: 1. Add the new codename to the releases list. 1. Change default_branch to the branch you just created above. 1. Evaluate overrides for the aforementioned variables and season to taste.
7. Run jobgenerator and then look over the builds triggered. Did you miss a step?
8. Add the new release to the Britney job so builds can migrate.
9. If lintian and devscripts have not been updated, cherry-pick the lintian patch adding the new release as known if there is one, and no-change rebuild devscripts.
10. Lintian needs a patch because all of the Ubuntu releases are hardcoded in vendors/ubuntu/main/data/changes-file/known-dists.
11. devscripts needs a no-change rebuild because it gets the value grabbed by dch -r on build time. This is in line 47 of scripts/Makefile.
12. Evaluate our packages. What needs to be updated to the latest upstream release? What did we carry over to this release?