Difference between revisions of "Release checklist"
From Bitfighter
| Line 1: | Line 1: | ||
* Make sure all code is checked in to HG | * 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: | * Update version.h: | ||
** Change ZAP_GAME_RELEASE to new version | ** Change ZAP_GAME_RELEASE to new version | ||
| Line 7: | Line 9: | ||
* Re-checkin to HG, so version numbers are correct, and everything aligns correctly | * Re-checkin to HG, so version numbers are correct, and everything aligns correctly | ||
* Tag the release in HG | * Tag the release in HG | ||
| − | * Compile the game with the release version | + | * Build for Windows: |
| − | * Run NSI to create windows installer | + | ** Compile the game with the release version |
| − | * Test installer | + | ** Run NSI to create windows installer |
| − | + | ** Test installer | |
| − | * Upload | + | * Build for Mac |
| − | * Upload Mac version to Google code | + | ** Build the DMG target in XCode |
| − | * Run script to build and upload tarball | + | ** 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 | ||
| + | * Build for various Linux distros using openSUSE Build Service (or tell other distros about the new release) | ||
* 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 | ||
Revision as of 17:59, 19 April 2011
- 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
- Tag the release in HG
- 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
- Build for various Linux distros using openSUSE Build Service (or tell other distros about the new release)
- 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
