Difference between revisions of "Release checklist"
From Bitfighter
Watusimoto (Talk | contribs) |
|||
| Line 17: | Line 17: | ||
#* Build package using the PACKAGE target in Visual Studio | #* Build package using the PACKAGE target in Visual Studio | ||
#* Test the installers | #* Test the installers | ||
| + | #*Don't forget portable build! | ||
# Build for OSX (ppc, i386, x86_64) | # Build for OSX (ppc, i386, x86_64) | ||
#* Each architecture is a different DMG | #* Each architecture is a different DMG | ||
Revision as of 23:14, 16 May 2015
- 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
- Don't forget portable build!
- Build for OSX (ppc, i386, x86_64)
- Each architecture is a different DMG
- Test DMGs
- Build for Linux
- Create source package for Linux distros. Use the 'create_tarball.sh' script from the bitfighter tools repo. Note the excludes list inside the script which strips out non-Linuxy stuff
- 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/ (login, click "Flag as out of date" link on right)
- Update Desura page
- Upload all builds to bitfighter.org/files/
- Test downloads
- Put copy of source tarball at static URL to help maintainers:
- On bitfighter.org:
- sudo ln -s /var/www/html/files/bitfighter-019e.tar.gz /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 a message for a particular release (like if a bad client was released)
- [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
-
http://freecode.com/projects/bitfighter/releases(site appears defunct) - http://www.lgdb.org/node/1076/edit
- linuxgames.com
- GameJolt
-
- Update /topic on #bitfighter IRC channel
- Update the Building Bitfighter page
