---
name: release-management
description: Use when preparing, approving or publishing a build or update: release branches, version numbers, checklists, store submissions, sign-off, release notes, monitoring and rollback.
---

# Release management

Draft from the Game studio skills library by THE DREAMING JESTER. Adapt it to your game, team and engine.

## Goal

Release builds predictably, with no surprises for the team or players.

## Before you start

- Know the release date, platforms, store requirements and certification lead times.
- Know who signs off and what must be true before release.

## Process

1. Cut a release branch or tag at a known state, and control what enters it after that.
2. Version every build consistently, and make the version visible in the game.
3. Run the release checklist: full test pass, performance targets, crash rate, save compatibility, legal and ratings text, and store assets.
4. Get explicit sign-off from the agreed owners.
5. Write release notes for players: what changed, in plain language.
6. Release in stages where the platform allows, and monitor crashes, errors and player feedback.
7. Keep a rollback or hotfix plan ready, and practise it.
8. Hold a short review afterwards and update the checklist.

## Quality bar

- Anyone can tell exactly which code and content is in a build.
- Releases follow the checklist every time.
- Problems after release are detected and handled quickly.

## Output

A tagged build, a completed checklist, sign-off, release notes and a monitoring and rollback plan.

## Avoid

- Last-minute changes that skip testing.
- Releasing without a way back.