# Release management template

> Free release management template from SprintProof: https://sprintproof.com/templates/release-plan-template#release-management
> Copy it once for your product, then update the calendar and the log for every release.
> For one specific release, use the release plan template: https://sprintproof.com/templates/release-plan-template

Product / service:
Document owner (release manager):
Last reviewed:
Applies to: (all production releases of … / which repos, apps and services)

---

## 1. Purpose and scope

- What this process covers: (apps, services, environments)
- What it does not cover: (e.g. marketing site, internal tools)
- Where releases are tracked: (Jira, Linear, GitHub releases, this doc)

## 2. Release types

| Type | What it may contain | Who approves | Lead time | Release notes? |
|---|---|---|---|---|
| Major | New features, breaking changes, migrations | | | Yes, user-facing |
| Minor | New features without breaking changes | | | Yes |
| Patch | Bug fixes only | | | Short changelog |
| Hotfix | Fix for a live incident, nothing else | | Same day | Incident note + changelog |

Version numbering: (e.g. MAJOR.MINOR.PATCH)
What counts as a breaking change for us:

## 3. Cadence and release calendar

Cadence: (e.g. continuous for patches, scheduled minor releases every …)
Freeze rule: (when scope stops changing before a scheduled release)
Blackout dates: (holidays, peak periods, other teams' launches)

| Release | Type | Scope summary | Release manager | Code freeze | Target date | Status | Release plan link |
|---|---|---|---|---|---|---|---|
| | | | | | | Planned / In test / Released / Rolled back | |
| | | | | | | | |

## 4. Roles and responsibilities

| Role | Name | Responsible for |
|---|---|---|
| Release manager | | Runs the checklist, calls go/no-go, owns the calendar |
| Product owner | | Scope, release notes, who is told |
| Engineering lead | | Code freeze, merges, deployment, rollback |
| QA / test owner | | Test plan, regression, sign-off in staging |
| Security / data owner | | Security review, data and migration checks |
| Support / docs owner | | Help articles, support briefing, known issues |
| Approver(s) | | Final yes for Major releases (and others as set in section 2) |

## 5. Environments and promotion path

| Environment | Purpose | Who can deploy | Data | Exit check before promoting |
|---|---|---|---|---|
| Development | | | Test data | |
| Staging | Release candidate, production-like | | Anonymised / seeded | |
| Production | | | Live | |

Feature flags: (which tool, who can turn flags on, how flags are removed later)

## 6. Release readiness checklist

Every line has an owner and a yes/no answer. A release ships only when every line is Yes or marked N/A with a reason.

| # | Check | Owner | Yes / No / N/A | Note |
|---|---|---|---|---|
| 1 | Scope is frozen and matches the release plan | | | |
| 2 | All items meet their acceptance criteria | | | |
| 3 | Automated tests pass in CI | | | |
| 4 | Regression tests pass in staging | | | |
| 5 | Security review done for new endpoints, permissions and data | | | |
| 6 | Database migrations tested, with a written rollback or a forward fix | | | |
| 7 | Feature flags set and owners named | | | |
| 8 | Monitoring, alerts and dashboards ready for the new parts | | | |
| 9 | Performance checked for the parts that could be slow | | | |
| 10 | Release notes written and reviewed | | | |
| 11 | Help docs and support briefing ready, known issues listed | | | |
| 12 | Legal, privacy or store review done (if needed) | | | |
| 13 | Rollback plan written and owner on call during release | | | |
| 14 | Go/no-go approver has signed off | | | |

## 7. Go/no-go

When: (e.g. the day before a scheduled release, or before every Major)
Who attends:
Decision rule: (e.g. go only if checklist lines 1–14 are Yes or N/A)
Where the decision is written down:

| Release | Date | Decision (Go / No-go) | Decided by | Open items |
|---|---|---|---|---|
| | | | | |

## 8. Deployment and rollback

Deployment steps:
1.
2.
3.

Rollout: (all at once / flag to internal users first / percentage rollout / by region)

Rollback trigger: (what you watch, and the condition that means "roll back now")
Rollback steps:
1.
2.
Who decides on a rollback:
Maximum time before deciding: (agreed by the team)

## 9. Communication

| Audience | What they need | Channel | Owner | When |
|---|---|---|---|---|
| Team | Release time, freeze, who is on call | | | Before freeze |
| Support | What changes, known issues, what to say | | | Before release |
| Customers | Release notes, anything they must do | | | At release |
| Stakeholders | What shipped, what slipped | | | After release |

Release notes template:
- What's new
- What changed
- What was fixed
- Anything you need to do

## 10. Post-release review

Hold it within (… days) of every Major release and after any rollback or hotfix.

- What shipped vs what was planned:
- Target date vs actual date:
- Incidents, rollbacks or hotfixes:
- Checklist lines that were skipped or failed, and why:
- What we change in this template:

## Release log

| Release | Version | Type | Date | Result (Shipped / Rolled back / Hotfixed) | Review link |
|---|---|---|---|---|---|
| | | | | | |
