# Software release checklist kanban template

> Release day goes wrong when someone forgets one step. Put the release on a board and the checklist inside the card.

Source: https://cbse.club/templates/release-checklist · Updated 2026-11-03

## Who this board is for

Small engineering teams that ship versioned releases (apps, libraries, firmware, games) and anyone who has ever said “wait, did we update the changelog?”.

## Columns

- **Maybe?**: every new card lands here first, to be triaged.
- **In this release**: Changes merged and planned for the next version.
- **Testing**: Being checked on a staging build.
- **Staged**: Passed testing, waiting for release.
- **Done**: finished cards, with history kept.
- **Not Now**: cards untouched for the auto-postpone period move here automatically.

## How to run it

1. Create one golden card per release with steps: freeze, test, update changelog, tag the build, deploy, smoke test, announce.
2. Add a card for each change going out and move it as it is verified.
3. On release day, work through the release card’s steps in order. The “5/8” counter shows how far along you are.
4. Close the release card and every change card once the release is live.

## Suggested tags

- #release: the release card itself
- #feature, bug, chore: kind of change
- #docs: documentation to update
- #hotfix: urgent patch release

## Tips

- Copy the release card’s steps from the previous release so the checklist improves every time.
- Use the account activity timeline afterwards to write the release notes.

Use this template free: https://cbse.club/templates/release-checklist/use

## Frequently asked questions

### What should a release checklist include?

Typically: code freeze, testing, changelog and version number, build or tag, deployment, a smoke test in production, monitoring, and an announcement. Keep it as steps on a card so it is reused every release.
