Creating a release

The release process for the game is entirely automated. All you as a developer need to do is open a pull request from the master branch into the release branch. Once that branch is closed, the CI system will take over.

Anatomy of a Release

A minor release involves of the following steps:

• Run the unit tests
• Validate all XML and JSON files
• Translate the Tiled maps from XML into Lua
• Update the version (minor or bugfix)
• Create the binaries
• Upload binaries to S3
• Update and upload the appcast.json to include the new builds
• Post a tweet and a link on /r/hawkthorne and /r/community

Bugfix Release

A bugfix release is exactly the same, except that we bump the bugfix version instead of the minor version. Also, no posts are created on social media

Development Builds

After every commit on the master branch, we upload a new version of the game. These releases do not get pushed out via the automatic updates. These builds are raw and probably contain bugs, so only use these for development.

• OS X
• Windows
• LOVE