Release Steps: Difference between revisions

Maikel (talk | contribs)
Maikel (talk | contribs)
No edit summary
Line 26: Line 26:
* Basic tests: download, check installer content, run game, play game, play network game.
* Basic tests: download, check installer content, run game, play game, play network game.
* Make announcements in our blog and in our forum.
* Make announcements in our blog and in our forum.
* Update external websites: [http://www.desura.com/games/publish/openclonk/execute Desura], [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt].
* Update external game portals: [http://www.desura.com/games/publish/openclonk/execute Desura], [http://gamejolt.com/games/platformer/openclonk/44187/ Game Jolt].
* Update external websites: [https://www.reddit.com/r/freegames/ reddit/freegames], [https://www.youtube.com/user/OpenClonkProject YouTube].
* Notify our Debian package maintainer that a new version has been released.
* Notify our Debian package maintainer that a new version has been released.
* Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.
* Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.

Revision as of 20:59, 10 March 2015

This page contains all steps to release a new version of OpenClonk and is meant for developers to check whether all conditions have been considered.

Pre Release

Steps to do before the release, and after the feature freeze.

  • If releasing from a stable branch: make sure all relevant commits have been cherry-picked from master.
  • Fix all bugs related to this release, which can be found in the bugtracker's roadmap.
  • Go the release button and perform a dry release to create a release candidate.
  • Test this release candidate with few simple tests: download, check installer content, run game, play game, play network game.

Release

If it is made sure that the current master branch or the current stable branch does not contain any bugs one can initiate the release procedure.

  • Update all Version.txt files in planet/ to the new version number and commit/push.
  • Update the Version.txt to the new version number and commit/push.
  • Then go to the release button and release from the correct branch.

Post Release

After the release has been uploaded do the following:

  • Tag the released changeset with the vX.Y tag.
  • Check if installers for all operating systems are existing (contact Mortimer for Mac).
  • Basic tests: download, check installer content, run game, play game, play network game.
  • Make announcements in our blog and in our forum.
  • Update external game portals: Desura, Game Jolt.
  • Update external websites: reddit/freegames, YouTube.
  • Notify our Debian package maintainer that a new version has been released.
  • Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.