Release checklist
This page is currently a draft.
|
This page is in the process of being updated.
Steps for branching MW vX[edit]
Timing | Type | Step | Example |
---|---|---|---|
Preparatory steps | |||
A few weeks before branching | Communications | Send a pre-branch reminder e-mail for MW vX | REL1_34 pre-branch announcement |
Before branching | Task management | Populate the MW vX release blocker's tag with release task tree | 1.36.0 release tree |
Before branching | Task management | Create a release blocker tag for MW vX+1 | MW-1.37-release project |
Before branching | Configuration | Configure CI to understand what to do with the new MW vX branches before they exist | Configuration of CI REL1_36 pipelines |
Before branching | Preparation | Update CREDITS in MW master using maintenance/updateCredits.php
|
Update credits ahead of the 1.37 release |
~ | Git | Cut the MW vX (REL…) branch via the MediaWiki release tools branch.py script
|
REL1_36 branching task |
Just after branching | Git | Prepare the master branch as MW vX+1 alpha, including the new RELEASE-NOTES file | REL1_36 preparation commit |
Just after branching | Documentation | Edit Module:Version to set isthereabeta to true .
|
REL1_36 branch on-wiki doc. config |
Just after branching | Documentation | Edit Release notes to add the new vX+1 branch as master, and the branch date of MW vX | REL1_38 branch point on-wiki doc |
A few minutes after branching | Communications | Send an announcement e-mail | REL1_36 branch announcement |
After branching | Configuration | Configure ExtensionDistributor that there's a new candidate snapshot branch | REL1_36 addition as a beta |
Release candidate steps (repeat until satisfied) | |||
~Two weeks after the branch/last RC | Task management | Agree there are no obvious major issues. | N/A |
Just before RC releasing | Git | Prepare the release branch as MW vX rc.Z | Prep. 1.36.0-rc.0 commit |
Just before RC releasing | Release | Build & sign the artefacts using the MediaWiki release tools make-branch script
|
N/A |
- | Release | Upload the built artefacts to releases.wikimedia.org | 1.36 release directory |
A few minutes after RC releasing | Communications | Send an announcement e-mail | 1.36.0-rc.0 availability announcement |
Release steps | |||
A week or so after the last RC | Task management | Agree there are no blockers left, and feedback on the release candidate is adequate. | N/A |
Just before releasing | Documentation | Fill in the RELEASE-NOTES file with all changes landed since the release candidate. | 1.36.0 notes fix-up |
Just before releasing | Git | Prepare the release branch as MW vX | Prep 1.36.0 commit |
Just before releasing | Release | Build & sign the artefacts using the MediaWiki release tools make-branch script
|
N/A |
- | Release | Upload the built artefacts to releases.wikimedia.org | 1.36 release directory |
Just after releasing | Communications | Send an announcement e-mail | 1.36.0 release announcement |
A few minutes after release | Documentation | Edit Module:Version to add the branch point and set isthereabeta to false .
|
1.36.0 release on-wiki doc. config |
A few minutes after release | Documentation | Edit Template:MediaWiki News to add the release announcement | 1.36.0 release on-wiki advert |
A few minutes after release | Documentation | Add a section for the first security release to the RELEASE-NOTES file | 1.36.1 documentation start commit |
A few minutes after release | Documentation | Archive the old RELEASE-NOTES file in the master branch | 1.36.0 release notes archival |
A few minutes or maybe two years after release | Documentation | Archive the Phabricator project tag of the previous, now unsupported release | 1.38.x archival |
After releasing | Configuration | Configure ExtensionDistributor that MW vX is a full release, not a candidate snapshot | REL1_36 promotion to stable |