New release tasks checklist - reyandme/kam_remake GitHub Wiki

During regular development

These tasks should be taken care of long before Release Candidate.

Dev

  • do important library updates, ie. OverbyteICS

Non-dev

  • game balance changes (of military units) for new release should be agreed upon very early - testing single- and multiplayer balance takes a very long time and is subject to heated discussions
  • gathering maps (SP, MP), which were created or modified during beta cycle. The point is to do as much work as possible, but late fixes can land until RC/final versions, as map updates are low risk.
  • prepare a "human readable" changelog - a basis for later newspost for kamremake.com (and for the video). It should include the most important changes from a player's point of view.

When Release Candidate is nearing

  • Recommendation: code freeze - only accept bugfixes and features for stuff that players really care about
  • Recommendation: quality control - every important fix/feature should be tested by a player who knows the game's behaviour well - to avoid waiting for the release to catch bugs.

Dev

  • Check bug reports (in CrashReporter), pay extra attention to MP desync reports. Make sure there are no widespread bugs in the release. Minor or rare bugs are okay.
  • Update scripting wiki (autogenerated with ScriptingParser)
  • Check game for memory leaks (with FastMM)

Non-dev

  • Last call for translators: Installer, Readme in .md files and game texts
  • Last minute MP, SP map updates
  • Prepare release announcement draft
  • Prepare release banner, which will be used for advertising on socials (see past kamremake.com newsposts for inspiration)
  • Optional (when there's a volunteer and the release is a major one): prepare release video, detailing the most important (and visually pleasing) changes

When Release Candidate is being made

  • Update changelog in todo\Changelog xxx.txt
  • Make a pre-RC build and test it
  • Change the NetProtocol revision (to be sure there are no hard to track issues with it, resulting from different server/client net code)
  • Make DedicatedServer and other utils available separately on kamremake.com
  • Consider releasing update (patch) installer from previous version
  • Add lobby message for new version on Master Server
  • Post release announcement, promote it on socials (Fb, Reddit, etc.)

After release

  • add lobby message for old version, advertising the new one