Release checklist

X.Y.Z is the version, for example 6.0.3.

• Actions -> l10n-pot -> Run workflow, a week before the tag so that translators have time. It rebuilds po/mcommander.pot and, if the strings changed, pushes the l10n/pot branch and prints a link in the job summary. Open that pull request and merge it: Weblate reads the template from master and puts the new strings into the po files by itself.

• Actions -> l10n-pull -> Run workflow: it brings the translations from Weblate into the l10n/weblate branch and prints a link in the job summary. Open that pull request and merge it, do not squash it, the commits carry the names of the translators.

• Rename the open milestone Future release to vX.Y.Z.

• Actions -> Create release notes -> Run workflow: milestone vX.Y.Z, all three boxes clear.

• Read the notes on the Summary page of that run: every merged pull request of the milestone is there, the wording is right, and the short summary says what the release is. The same text is in the release-notes artifact.

• Actions -> Create release notes -> Run workflow: milestone vX.Y.Z, tick Also commit the CHANGELOG.md section to the default branch.

• Create the release tag:

  git checkout master && git pull --ff-only
  git tag -a vX.Y.Z -m "vX.Y.Z"
  git push origin vX.Y.Z
  

• Actions -> Create release notes -> Run workflow: milestone vX.Y.Z, tick Also publish: notes into the release, summary onto the milestone and Also publish the page to the wiki.

• Releases -> the vX.Y.Z draft -> Publish release.

• Homebrew: in blue-panels/homebrew-tap set url and sha256 of Formula/mcommander.rb to the new archive and open a pull request. When both test-bot jobs pass, do not press Merge: run Actions -> brew pr-pull with the pull request number. It uploads the bottles, writes the bottle block and merges the pull request.