Playtest or Release Checklist

• Have the patches been reviewed?

  • The default should be "no merge"; justify why your patches are worth including, which is more than just "no nits".
  • Each patch should have been tested by its author, on at least the platform they run. If the patch is fixing something platform-specific on some other platform, it must have been tested there, otherwise you're just making stuff up.
  • Check for interactions between features. Many of these have been wrong, at least historically -- build/sell sell/capture etc.
  • Check for copypasta with simian and/or eyeballs.

• Does it build?

  • Check on both Windows and Mac/Linux.
  • There should be no warnings.
  • RALint should be clean, or at least no worse than at the previous tag.

• Does it work?

  • Everything should work, in all mods that will be included -- at least no worse than the previous tag.
  • Yes, this step sucks to verify.

• Has the CHANGELOG been updated?

• If there are master server changes [or any other infrastructure changes], have those been deployed first?

  • All infrastructure changes MUST be backwards-compatible; there are various old client versions still in use, which you must not break.

• If that's all good:

  • Tag the commit you intend to release. checkout openra/bleed git tag playtest-yyyymmdd / git tag 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
  • Login to the build server, and deploy it.

    $ ssh -A build@build.open-ra.org
    
    $ cd openra-package/
    $ ./checkout-and-build.sh playtest-yyyymmdd

If it's a playtest, you're done. If it's a release:

• Announce the release in a news post on the website

• Announce the release on twitter @openRA, linking to the news post