**Checklist:**[ ] Pending issues as subtasks
(another version of the checklist in T334778)- If any open tickets need to be resolved and related changes need to be included in the release, add them as subtasks of the release ticket.
[] Do any other issues need to be specifically included in this- If this release is triggered by a Mediawiki bugfix release?, if so, add them as children of this taskconsider only including bug/security issue fixes and avoid breaking changes.
[ ] Create a PR
[] Review open backports for Wikimedia controlled Gerrit extensions included in the release, merging where appropriate [[ https://gerrit.wikimedia.org/r/q/status:open+branch:REL1_39(project:mediawiki/extensions/Babel+OR++project:mediawiki/extensions/cldr+OR++project:mediawiki/extensions/CirrusSearch+OR++project:mediawiki/extensions/ConfirmEdit+OR++project:mediawiki/extensions/Elastica+OR++project:mediawiki/extensions/EntitySchema+OR++project:mediawiki/extensions/Nuke+OR++project:mediawiki/extensions/OAuth+OR++project:mediawiki/extensions/Scribunto+OR++project:mediawiki/extensions/SyntaxHighlight_GeSHi+OR++project:mediawiki/extensions/UniversalLanguageSelector+OR++project:mediawiki/extensions/VisualEditor++project:mediawiki/extensions/WikibaseCirrusSearch+OR++project:mediawiki/extensions/WikibaseManifest) | link ]] (check that all extensions are included in the search and the correct REL_x version is used)- For bugfix releases
- It could be that trivial fixes are queued up - The release branch already in release branchesexists. These can be merged ahead of a release so they are included in the release.
- To streamline the process in- Create a release preparation branch off of the future we may choose to drop this stepexisting release branch. E.g. `releaseprep-1.40.2` off of `mw-1.40`.
[] - Create a PR with the following changes:for that branch, merging back into the release branch.
[]- Consider backporting changes to env filesfrom main into it.
[] update commit hashes if needed- Bugfix releases should contain as little changes as possible.
[] add release notes- Make sure that the variables.env file is not changed by incoming changes from main.
[] Test R- For major release Candidates
[] CI should be green- Create a new release branch off of main. E.g. `mw-1.44`
[] run automated tests locally- This branch is now equal to main. It will hold all final releases in the future.
[] deploy artifacts to [[ https://wikibase-product-testing.wmcloud.org | test system ]] and give the PM a heads up
[] Prepare communication doc ([[ https://drive.google.com/drive/folders/1kHhKKwHlwq_P9x4j8-UnzV72yq0AYpsZ | folder ]])- Create another branch off of that release branch. E.g. `releaseprep-1.44.0`
**NOTE**: add the changes we have made to the QuickStatements OAuth. Now it is fixed on the example directory: using a public url instead of a local one. There has been a change in the name of that variable as well- This second branch is meant to prepare the first release on the release branch.
[] Ping ComCom and TechWriter to go over the comm doc- Create a PR to merge `releaseprep-1.44.0` into `mw-1.44`
[ ] Adjust upgrade test paths
[] agree with ComCom on a timing to publish the release- 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.
[ ] Update `variables.env`
[] Publish release candidates ([[ https://github.com/wmde/wikibase-release-pipeline/blob/main/docs/topics/publishing.md | howto ]]): - Update `WMDE_RELEASE_VERSION`
[] dockerhub- Update MediaWiki Version
[] releases.wikimedia.org- Update all docker `*_IMAGE_URL`s
[]- Update and merge PR for docker-compose example in release-pipeline repository`WDQS_VERSION`
- Use the script to update remaining version hashes in variables env. [] Tags`$ ./build.sh update_hashes`
[ ] Update CHANGES.md
- Add a section in CHANGES.md. Following the example of previous releases, update the different values. [] DxocsThe spec will eventually point to variables.env in its state at the time
[ ] Test Release Candidate
[] mw.org- CI should be green
[] docker-compose example references- [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
[ ] Prepare communication
[] Record build meta data- Prepare [communication doc](https://drive.google.com/drive/folders/1kHhKKwHlwq_P9x4j8-UnzV72yq0AYpsZ)
- Ping ComCom and TechWriter to go over the doc
[]- Agree with Communication is sentCom on a timing to publish the release
**Acceptance Criteria:**[ ] Publish the release
[] Docker Images pushed- Make sure `variables.env` `WMDE_RELEASE_VERSION` does not contain "-prerelease" anymore
[] Tarballs released
[optional] **Notes:**- Get reviews for the PR
- new `mw-1.41`- Merge the release preparation PR into the release branch
- Upstream- **This will automatically push docker image is available already https://hub.docker.com/_/mediawiki/s to docker hub and therefore release the new version**
- Work off of the [Release Checklist](https://docs.google.com/document/d/1BGxcqt9CHbb-8dfWjK-lZmNoNcD08urb23JqtgoVTeg/edit#heading=h.qjz0elg5ctgz) and take notes on steps taken and steps skippedUpdate the latest version on the [docker install instructions](https://www.mediawiki.org/wiki/Wikibase/Docker)
- [[ https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/message/OMDFHJ2SKKJH775RW4UTC754OY4TP7UU/ | wikitech-l release announcement + release notes]]Make sure the communication is sent
- [[ https://doc.wikimedia.org/Wikibase/ | Wikibase Documentation ]]
[optional] **Open Questions:**- Update the example directory (TODO: this process is still broken and weird)
- none atm