Playtest or Release Checklist

• Assuming you aliased the upstream repository with openra git fetch openra then git checkout bleed && git reset --hard openra/bleed. Warning: this overwrites your own bleed branch.
• Tag the commit you intend to release. git checkout openra/bleed && git tag playtest/release-yyyymmdd
• Push the tag to OpenRA/OpenRA, and advance either the next or master branch as appropriate for the release type:
  • git push openra playtest-yyyymmdd bleed:next
  • or git push openra release-yyyymmdd next:master

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. Travis will automatically start building and deploying the packages at GitHub releases.

• Download the package and head over to Publish on Desura. Create a new MCF file from a clean OpenRA installation, upload it and submit it for approval. See Publishing releases on Desura for detailed instructions on the process.

Announce

• Update the website with the news: https://github.com/OpenRA/OpenRAWeb/pulls including the current playtest/release tags and the in-game notifier.
• Link it on https://www.facebook.com/openra which gets automatically aggregated at http://twitter.com/openra
• Copy the announcement on http://www.moddb.com/games/openra/ which also updates IndieDB, but not Desura.
• Post it on http://www.reddit.com/r/openra/
• Post it on https://plus.google.com/b/100332364931123881367/+OpenRAnet/posts