Release Steps

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

Before 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, use runtime join, save and load game, perform a runtime join.

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.

• Optional: Update all Version.txt files in planet/ to the new version number.
• Update the Version.txt to the new version number and put the extra version in Version.txt to FALSE. Commit and push push.
• Create a tag for the released changeset with the vX.Y tag (lightweight: git tag vX.Y).
• Then go to the release button and release from the correct branch.

After Release

• Create a stable branch named stable-X for bugfix releases.
• Make announcements in our blog and in our forum.
• Notify an openclonk.org admin to transfer the source package to www.openclonk.org/builds/release/X.Y/openclonk-X.Y-src.tar.bz2.
• Notify an openclonk.org admin to mark this version as released in the bugtracker and add the next version to the roadmap.
• Notify our Linux package maintainers for Debian, Arch, FreeBSD and others that a new version has been released.

Optional

• Update external websites: Game Jolt, wikipedia article,reddit/freegames, YouTube.
• Spread the word! More advertisement!