Playtest or Release Checklist

You can create branches and tag releases via the GitHub interface. If you want to do it manually expand the following section.

We'll assume the upstream OpenRA repository is aliased to upstream.

Branching off a new stabilization branch while tagging a new playtest

git fetch upstream
git checkout -b prep-YYMM upstream/bleed
git tag playtest-yyyymmdd
git push upstream playtest-yyyymmdd HEAD

Tagging a new playtest during stabilization

git fetch upstream
git checkout -B prep-YYMM upstream/prep-YYMM
git tag playtest-yyyymmdd
git push upstream playtest-yyyymmdd

Tagging a release

git fetch upstream
git checkout -B prep-YYMM upstream/prep-YYMM
git tag release-yyyymmdd
git push upstream release-yyyymmdd

Warning: The current make version does not use the latest, but the first tag, so we need an extra commit to separate last playtest and new release. Don't forget to update the branches. GitHub Actions will automatically start building and deploying the packages at GitHub releases. The following has to be deployed manually:

Upload the engine to Resource Centre
Deploy documentation
Deploy itch.io Packages

Update the Resource Center

See the file /home/resource/resource-site-update-instructions.md on the server or contact @abcdefg30.

Announce

Update the website and battlefield news with the news, including the current playtest/release tags and the in-game notifier.
Announce on Forum and Discord
Link it on Facebook and Twitter
Copy the announcement on ModDB which also updates IndieDB.
Post on reddit