Difference between revisions of "Release checklist"
From Bitfighter
| Line 5: | Line 5: | ||
# Update version.h: | # Update version.h: | ||
#* Change ZAP_GAME_RELEASE to new version | #* Change ZAP_GAME_RELEASE to new version | ||
| − | #* Change BUILD_VERSION to (current commit number + | + | #* Change BUILD_VERSION to (current commit number + 1) (found by running 'hg summary') |
#* If new client-server is incompatible with the old, update CS_PROTOCOL_VERSION | #* 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 | #* If new client-master is incompatible with the old, update MASTER_PROTOCOL_VERSION | ||
| − | #* '''Important:''' Make sure version.h parsing works in | + | #* '''Important:''' Make sure version.h parsing works in CMake. It will output to the console when it is run. |
# Re-checkin to HG, so version numbers are correct, and everything aligns correctly NOTE THAT THE TAG WILL COUNT AS A VERSION! | # Re-checkin to HG, so version numbers are correct, and everything aligns correctly NOTE THAT THE TAG WILL COUNT AS A VERSION! | ||
| − | # Tag the release in HG. Use format "bitfighter- | + | # Tag the release in HG. Use format "bitfighter-019d" |
| − | # Build for Windows: | + | # Build for Windows (32-bit is NSI, 64-bit is MSI): |
| − | #* Compile the game | + | #* Compile the game as a '''Release''' version |
| − | #* | + | #* Compile 'bfup' |
| − | #* Test | + | #* Build notifier; use script in notifier/pyinstaller/ |
| − | # Build for | + | #* Build package using the PACKAGE target in Visual Studio |
| − | #* | + | #* Test the installers |
| + | # Build for OSX (ppc, i386, x86_64) | ||
| + | #* Each architecture is a different DMG | ||
#* Test DMG | #* Test DMG | ||
| − | # | + | # Build for Linux |
| − | #* | + | #* Standalone build |
| − | #* | + | #* Various Linux distros: |
| − | #* | + | #** Use Open Build Service (or tell other distros about the new release.) Link: https://build.opensuse.org/package/show?package=bitfighter&project=games |
| + | #** Flag old package as being out of date on Arch: https://aur.archlinux.org/packages/bitfighter/ | ||
| + | #* Create source package for other Linux distros. Make sure to remove OSX/Windows libraries to reduce size | ||
| + | # Upload all builds to bitfighter.org/files/ | ||
#* Test downloads | #* Test downloads | ||
| − | # Put copy of tarball at static URL to help maintainers: | + | # Put copy of source tarball at static URL to help maintainers: |
#* On bitfighter.org: | #* On bitfighter.org: | ||
#** sudo wget https://bitfighter.googlecode.com/files/bitfighter-018a.tar.gz -O /var/www/html/files/bitfighter-latest.tar.gz | #** sudo wget https://bitfighter.googlecode.com/files/bitfighter-018a.tar.gz -O /var/www/html/files/bitfighter-latest.tar.gz | ||
#* File will be available from http://bitfighter.org/files/bitfighter-latest.tar.gz | #* File will be available from http://bitfighter.org/files/bitfighter-latest.tar.gz | ||
| − | |||
| − | |||
| − | |||
| − | |||
# Rebuild any servers that need rebuilding | # Rebuild any servers that need rebuilding | ||
# Update master.ini: | # Update master.ini: | ||
Revision as of 14:16, 31 December 2014
- Make sure all code is checked in to HG
- Disable any experimental features in development
- Update checkIfThisIsAnUpdate() in main.cpp and add any update tasks
- Make sure dedicated server compiles
- Update version.h:
- Change ZAP_GAME_RELEASE to new version
- Change BUILD_VERSION to (current commit number + 1) (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
- Important: Make sure version.h parsing works in CMake. It will output to the console when it is run.
- Re-checkin to HG, so version numbers are correct, and everything aligns correctly NOTE THAT THE TAG WILL COUNT AS A VERSION!
- Tag the release in HG. Use format "bitfighter-019d"
- Build for Windows (32-bit is NSI, 64-bit is MSI):
- Compile the game as a Release version
- Compile 'bfup'
- Build notifier; use script in notifier/pyinstaller/
- Build package using the PACKAGE target in Visual Studio
- Test the installers
- Build for OSX (ppc, i386, x86_64)
- Each architecture is a different DMG
- Test DMG
- Build for Linux
- Standalone build
- Various Linux distros:
- Use Open Build Service (or tell other distros about the new release.) Link: https://build.opensuse.org/package/show?package=bitfighter&project=games
- Flag old package as being out of date on Arch: https://aur.archlinux.org/packages/bitfighter/
- Create source package for other Linux distros. Make sure to remove OSX/Windows libraries to reduce size
- Upload all builds to bitfighter.org/files/
- Test downloads
- Put copy of source tarball at static URL to help maintainers:
- On bitfighter.org:
- sudo wget https://bitfighter.googlecode.com/files/bitfighter-018a.tar.gz -O /var/www/html/files/bitfighter-latest.tar.gz
- File will be available from http://bitfighter.org/files/bitfighter-latest.tar.gz
- On bitfighter.org:
- Rebuild any servers that need rebuilding
- Update master.ini:
- [host] section:
- Update latest_released_client_build_version
- Update latest_released_cs_protocol (if needed)
- [motd_clients] section:
- Add a new line for the old build version
- [host] section:
- Update auto-update file (/var/www/html/files/getDownloadUrl.php) on master server
- Sign the Mac files with our private key for the Sparkle updates
- Update versions/dates in the php file (add sparkle signatures)
- Update bitfighter website
- Add new release to all releases page
- Update download page to show new release
- Add story to main page on website announcing new release
- Update luadoc/doxygen
- Post announcement in forums
- Announce new version via email
- Post the update to gaming web sites
- Update /topic on #bitfighter IRC channel
- Update the Building Bitfighter page
