Repository navigation
Description
I went through the 3.12.0 release process and grabbed most of the points that hadn't been closed off for this, as a starting point. I've also added my comments in.
- Assign this issue to the release shepherd who is in charge of managing this checklist.
We managed without one.
- Check if the list of translators in tools/create-translation-issues.sh. Make sure issue text is up-to-date. Add any URLs that will need localisation into the "New/Changed screenshots" section.
I'm not clear what the process is: even if it's through Weblate, I don't know enough about it.
- Check for conflicting accelerator keys (see tools/checkkeys.pl)
Postponed to fix post-release?
Maybe we can get a workflow that will do this? Build, deploy and start up the website in a container, then run the link check against it, taking down the website container when complete.
- Do a smoke test of the upgrade notification (do this very quickly)
Tried from 3.12.0rc1 and didn't get a notification. Tried again from 3.11.0 and did get the notification. Bug raised. (Yes, it does say
- Run the previous release (not an intermediate) build of GUI Client and Server
but we should still notify older intermediate releases).
[ ] Upload the artifacts to SourceForge and set defaults.
Do we have any tracking of SourceForge traffic? (This hasn't been done yet.)
- Trigger the update notification by updating both Update Check Servers with the new version (@pljones for update02, email corrados for update01)
Well, I did update2 - I'll send an email as well.
- Update this template in https://jamulus.io/contribute/Release-Process with any improvements if needed.
I did a few as we went along. We probably should review it, though.
- Determine if a release retrospective is needed, create on Discussions if required
Hence this post.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity