- Pending issues as subtasks. If any open tickets need to be resolved and/or related changes need to be included in the release, add them as subtasks of this release ticket.
- Update build/*/build.env bump upstream versions by changing build.env files. You can find further instructions in the build.env files themselves.
- Merge all pending changes to main releases are always done from the main branch.
- Verify CI on main is green
- Do a sanity check by manually reviewing a running instance using your build. This can be done locally on your machine or on a public server. You can find built images from your release preparation branch on the GitHub Container Registry tagged with dev-GITHUB_ACTIONS_RUN_NUMBER, e.g., dev-123456789. This tag can be used to set up an instance running your release preparation version.
- Release Dry Run by running the Github Action Create a WBS Release in Dry Run mode. Check the output and review version and changelog generated.
- Prepare communication by creating a release announcement.
- Coordinate with ComCom on timing the publication of the release. Talk to SCoT (ComCom, technical writer) about this.
- Publish the release by running the Github Action Create a WBS Release ATTENTION: This will automatically push images to Docker Hub!
- Update Dockerhub README (from ./build/*/dockerhub.md) if required (e.g. major versions changed).
You`re done. Congratulations!