Difference between revisions of "Release checklist"
From Bitfighter
| Line 1: | Line 1: | ||
| − | * Make sure all code is checked in to | + | * Make sure all code is checked in to HG |
| − | * Update | + | * Update version.h: |
| − | * If new | + | ** Change ZAP_GAME_RELEASE to new version |
| − | * Re-checkin to | + | ** Change BUILD_VERSION to next commit number (found by running 'hg summary') |
| − | * Tag the release in | + | ** 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 | ||
| + | * Tag the release in HG | ||
* Compile the game with the release version | * Compile the game with the release version | ||
* Run NSI to create windows installer | * Run NSI to create windows installer | ||
Revision as of 17:52, 19 April 2011
- Make sure all code is checked in to HG
- 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
- Tag the release in HG
- Compile the game with the release version
- Run NSI to create windows installer
- Test installer
- Upload new version to Google code
- Upload Mac version to Google code
- Run script to build and upload tarball to Google code
- Add new release to all releases page
- Update download page to show new release
- Test download
- If necessary, add a new line in the master server config file
- Update auto-update file (files/getDownloadUrl.php)
- Add story to main page on website announcing new release
- Announce new version via email
- Rebuild any servers that need rebuilding
