Release Steps

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:.

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.
• Tag this latest changeset with the vX.Y tag.
• Then go to the release button and release from the correct branch.

Post Release

After the release has been uploaded do the following:

• 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.
• Update external websites: Desura, Game Jolt.
• Notify our Debian package maintainer that a new version has been released.
• Make announcements in our blog and in our forum.
• Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.