Difference between revisions of "Release checklist"
From Bitfighter
Watusimoto (Talk | contribs) (updated list) |
|||
| Line 4: | Line 4: | ||
* If necessary, add a new line in the master server config file | * If necessary, add a new line in the master server config file | ||
* Re-checkin to SVN, so version numbers are correct, and everything aligns correctly | * 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 | * Compile the game with the release version | ||
* Run bitfighter.exe with -createsampleini option to create an updated sample INI file | * Run bitfighter.exe with -createsampleini option to create an updated sample INI file | ||
Revision as of 06:47, 2 June 2009
- 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
- If necessary, add a new line in the master server config file
- 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 bitfighter.exe with -createsampleini option to create an updated sample INI file
- Edit NSI file to update version number
- Run NSI to create windows installer
- Test installer
- Upload new version to website
- Add new release to all releases page
- Update download page to show new release
- Test download
- Add story to main page on website announcing new release
- Announce new version
