Difference between revisions of "Release checklist"

From Bitfighter
Line 25: Line 25:
 
# 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 (files/getDownloadUrl.php)
+
# Update auto-update file (/var/www/html/files/getDownloadUrl.php)
 
# 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
 
# Post the update to gaming web sites
 
# Post the update to gaming web sites

Revision as of 22:49, 31 January 2012

  1. Make sure all code is checked in to HG
  2. Update checkIfThisIsAnUpdate() in main.cpp and add any update tasks
  3. Update Mac/Linux launch scripts with any update tasks
  4. 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
  5. Re-checkin to HG, so version numbers are correct, and everything aligns correctly
  6. Tag the release in HG
  7. Build for Windows:
    • Compile the game with the release version
    • Run NSI to create windows installer
    • Test installer
  8. Build for Mac
    • Build the DMG target in XCode
    • Test DMG
  9. 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
  10. 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
  11. Add new release to all releases page
  12. Update download page to show new release
  13. Test download
  14. If necessary, add a new line in the master server config file
  15. Update auto-update file (/var/www/html/files/getDownloadUrl.php)
  16. Add story to main page on website announcing new release
  17. Announce new version via email
  18. Rebuild any servers that need rebuilding
  19. Post the update to gaming web sites