Difference between revisions of "Release checklist"
From Bitfighter
| Line 7: | Line 7: | ||
* Run NSI to create windows installer | * Run NSI to create windows installer | ||
* Test installer | * Test installer | ||
| − | * Upload new version to | + | |
| + | * 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 | * Add new release to all releases page | ||
* Update download page to show new release | * Update download page to show new release | ||
* Test download | * Test download | ||
* If necessary, add a new line in the master server config file | * If necessary, add a new line in the master server config file | ||
| + | * Update auto-update file | ||
* Add story to main page on website announcing new release | * Add story to main page on website announcing new release | ||
* Announce new version via email | * Announce new version via email | ||
* Rebuild any servers that need rebuilding | * Rebuild any servers that need rebuilding | ||
Revision as of 07:47, 1 December 2010
- Make sure all code is checked in to SVN
- Update ZAP_GAME_RELEASE in game.h, with the SVN version number + 1
- If new version is incompatible with older ones, update ZAP_GAME_VERSION
- Re-checkin to SVN, so version numbers are correct, and everything aligns correctly
- Tag the release in SVN
- 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
- Add story to main page on website announcing new release
- Announce new version via email
- Rebuild any servers that need rebuilding
