WikiReleaseTeam/Release log/Boilerplate

This is the internal log mglaser uses to produce tarballs

Versions to be released
It's best to have each REL branch in a separate checkout. Switching between branches will surely produce confusion.
 * 1.19.x
 * 1.21.x
 * 1.22.x

Fix security bugs
Patches and respective backports must be available as patch files and reviewed.

Howto: git reset --hard origin/master git apply --check path/to/patch git am path/to/patch Status: PATCH - REVIEWED - LOCAL GIT

Bug x

 * master
 * brances

Release notes
Status: LOCAL GIT
 * branches

Prepare Announcement
Status: OK
 * branches

Produce the tarball
From here on, combined security and maintenance releases are time critical, as this discloses the security issues.

Push to gerrit and merge
Howto: git review Status: GERRIT - MERGED Link to gerrit Links to gerrit
 * master
 * branches

Tag versions
Howto (git checkout BRANCH, git pull, git tag) Status OK git tag -a 1.21.9 -m "Security and maintenance release 1.21.9" git push --tags
 * branches

Watch Jenkins
Jenkins tarball build jobs are triggered by new tags

https://integration.wikimedia.org/ci/view/MediaWiki/job/mediawiki-core-release/

Note: Login to rerun jobs

Status: JOB  - OK
 * branches

Get tarball and patch file
Status OK
 * branches

Final checks
Howto: Status: OK
 * install works
 * test folder is not included
 * extension versions are right
 * empty patch files: put a notice
 * branches

Sign tarball and patch files
Status: OK
 * branches

Upload to DL-server
Status: OK
 * branches

Send announcement
Status OK
 * branches

Post release
This is no longer time critical.

Update mediawiki.org
Status OK
 * branches