=== Wikibase Suite Release Checklist
[x] **Pending issues as subtasks**
- If any open tickets need to be resolved and related changes need to be included in the release, add them as subtasks of this release ticket. (If this release is triggered by a Mediawiki bugfix release, consider only including bug/security issue fixes and avoid breaking changes.)
[x] **Create branches**
- **For bugfix releases**
- Create a release preparation branch. The release branch already exists. E.g. `mw-1.40`. Create a release preparation branch off of the existing release branch. E.g. `releaseprep-1.40.2` off of `mw-1.40`.
- Backport changes from main if really needed. Bugfix releases should contain as little changes as possible. Make sure that the variables.env file is not changed by incoming changes from main.
- **For major releases**
- Create a new release branch off of main. E.g. `mw-1.44`
- This branch is now equal to main. It will hold all bugfix releases for that major version in the future.
- Create another branch off of that release branch. E.g. `releaseprep-1.44.0`
- This second branch is meant to prepare the first release on that release branch.
[x] **Update `variables.env` on the release prep branch**
- Update `WMDE_RELEASE_VERSION`
- Update MediaWiki Version
- Update all docker `*_IMAGE_URL`s
- Update `WDQS_VERSION`
- Use the script to update remaining version hashes in variables env. `$ ./build.sh update_hashes`
[x] **Update CHANGES.md**
- Add a section in CHANGES.md. Following the example of previous releases, update the different values. The spec will eventually point to variables.env in its state at the time.
[x] **Adjust upgrade test paths**
- Review all versions [here](https://github.com/wmde/wikibase-release-pipeline/blob/95405db45afa697d94fc54d177407241f6fe9c4c/.github/workflows/_build_test.yml#L127) and [here](https://github.com/wmde/wikibase-release-pipeline/blob/95405db45afa697d94fc54d177407241f6fe9c4c/test/suites/upgrade/versions.ts) to make the upgrade test work for relevant older versions to your new version.
[x] **Create a release PR**
- Merging the release preparation branch e.g. `releaseprep-1.44.0` into release branch e.g. `mw-1.44`.
[x] **Test Release Candidate**
- CI should be green
- [Deploy](https://docs.google.com/document/d/1BGxcqt9CHbb-8dfWjK-lZmNoNcD08urb23JqtgoVTeg/edit?pli=1#heading=h.qjz0elg5ctgz) to [test system](https://wikibase-product-testing.wmcloud.org) and give the team a heads up
- Get two reviews for the PR
[ ] **Prepare communication**
- Prepare [communication doc](https://drive.google.com/drive/folders/1kHhKKwHlwq_P9x4j8-UnzV72yq0AYpsZ)
- Ping ComCom and TechWriter to go over the doc
- Agree with ComCom on a timing to publish the release
[ ] **Publish the release**
- Make sure `variables.env` `WMDE_RELEASE_VERSION` has the desired version string
- Merge the release preparation PR into the release branch
- **This will automatically push docker images to docker hub and therefore release the new version**
- Update the latest version on the [docker install instructions](https://www.mediawiki.org/wiki/Wikibase/Docker)
- Make sure the communication is sent
[ ] **Update the example directory**
- TODO: how to do this without triggering a new release?
[ ] **Merge back to main**
- Decide whether there is stuff you want to merge back to main on the release branch.
{F42018754}