Release checklist
From Bitfighter
- Make sure all code is checked in to HG
- Update checkIfThisIsAnUpdate() in main.cpp and add any update tasks
- Update Mac/Linux launch scripts with any update tasks
- Update version.h:
- Change ZAP_GAME_RELEASE to new version
- Change BUILD_VERSION to next commit number (found by running 'hg summary')
- If new client-server is incompatible with the old, update CS_PROTOCOL_VERSION
- If new client-master is incompatible with the old, update MASTER_PROTOCOL_VERSION
- Re-checkin to HG, so version numbers are correct, and everything aligns correctly NOTE THAT THE TAG WILL COUNT AS A VERSION!
- Tag the release in HG. Use format "bitfighter-016"
- Build for Windows:
- Compile the game with the release version
- Run NSI to create windows installer
- Test installer
- Build for Mac
- Build the DMG target in XCode
- Test DMG
- Upload to Google Code
- Upload Windows version to Google code
- Upload Mac version to Google code
- Run script found in bitfighter-tools repo to build and upload source tarball
- Test downloads
- Build for various Linux distros using Open Build Service (or tell other distros about the new release.) Link: https://build.opensuse.org/package/show?package=bitfighter&project=games
- Rebuild any servers that need rebuilding
- If necessary, add a new line in the master server config file (master.ini - it will reload itself automatically)
- Update auto-update file (/var/www/html/files/getDownloadUrl.php) on master server
- Update bitfighter website
- Add new release to all releases page
- Update download page to show new release
- Add story to main page on website announcing new release
- Post announcement in forums
- Announce new version via email
- Post the update to gaming web sites
