WikiReleaseTeam/Release log/Boilerplate

This is the internal log mglaser uses to produce tarballs

Versions to be released

edit

It's best to have each REL branch in a separate checkout. Switching between branches will surely produce confusion.

  • 1.19.x
  • 1.22.x
  • 1.23.x

Preparation

edit

Fix security bugs

edit

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

edit
  • master
  • brances

Release notes

edit

Update release notes and DefaultSettings.php

Status:

LOCAL GIT
  • branches

Prepare Announcement

edit

Status:

OK
  • branches

Produce the tarball

edit

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

Push to gerrit and merge

edit

Howto:

git review

Status:

GERRIT - MERGED
  • master

Link to gerrit

  • branches

Links to gerrit

Tag versions

edit

Howto

(git checkout BRANCH, git pull, git tag)

Status

OK
  • branches

git tag -a 1.21.9 -m "Security and maintenance release 1.21.9" git push --tags

Watch Jenkins

edit

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 <NR> - OK
  • branches

Get tarball and patch file

edit

Status

OK
  • branches

Final checks

edit

Howto:

  • install works
  • test folder is not included
  • extension versions are right
  • empty patch files: put a notice

Status:

OK
  • branches

Sign tarball and patch files

edit

Status:

OK
  • branches

Upload to DL-server

edit

Status:

OK
  • branches

Send announcement

edit

Status

OK
  • branches

Post release

edit

This is no longer time critical.

Update mediawiki.org

edit

Status

OK
  • branches