Release management
Release management is the discipline of planning, scheduling, coordinating and controlling the movement of software from a finished build to its users, so that each release goes out at a known time, in a known state, with a known way back. It owns the release calendar, the readiness criteria, the go/no-go decision, the deployment and the rollback plan, and it spans engineering, QA, operations and the business.
The longer version
The work has a shape that repeats per release. Scope is fixed: which changes are in this release and which are not. A schedule is set, with the code freeze, the test window, the UAT window and the deployment slot. Readiness is tracked against written criteria. The go/no-go decision is made and recorded. The deployment is executed, usually by the pipeline, with a rollback plan held ready. And the release is confirmed in production with a smoke test before the notes go out. A release manager, or the product owner on a smaller team, owns the whole sequence.
Release management is distinct from deployment and from continuous delivery. Deployment is the technical act of putting a build on an environment; a release is the decision to expose that build to users, and the two are separated by feature flags on teams that deploy continuously. Continuous delivery is the engineering practice that keeps every build releasable; release management is the governance around which of those builds is released, when, and to whom. On a team with a mature pipeline, most of the mechanics are automated and what remains is the scope, the calendar and the decision.
The monthly release train is the bottleneck version: a freeze that starts a week before, so that every fix waits and every release is large, risky and full of changes nobody remembers. The vanished version is the opposite: a team deploying many times a day with no record of what is in production, no release notes, and no answer when support asks whether a customer's bug shipped yesterday. The discipline survives frequent releases when it is reduced to what still matters: what changed, when, who decided, and how to undo it.
Common questions
What does a release manager do?
Fixes the scope of each release, sets and defends the calendar, tracks readiness across QA, operations, support and the business, chairs the go/no-go decision, coordinates the deployment and the rollback plan, and confirms the release landed. On a small team the product owner carries the role; on a large one it is a job, often shared with operations.
What is the difference between release management and deployment?
Deployment is the technical act of putting a build onto an environment, which a pipeline does in minutes. Release management is the governance around it: deciding what goes in, when it ships, whether it is ready, who says so, and how to reverse it. With feature flags a build can be deployed without being released, which is why the two words are kept apart.
Is release management still needed with continuous delivery?
Reduced, not removed. Continuous delivery automates the mechanics, so the freeze, the manual deployment and much of the ceremony go away. What remains is knowing what is in production, deciding when a feature is exposed to users, writing the notes, and being able to undo a change. Teams that drop all of it discover the gap the first time support asks what shipped yesterday.
What are the stages of release management?
Scoping, where the changes in the release are fixed; scheduling, which sets the freeze, the test window, any UAT window and the deployment slot; readiness tracking against written criteria; the go/no-go decision; deployment, with the rollback plan held ready; verification in production by a smoke test; and communication, meaning the release notes and the support briefing. The sequence repeats per release, whether releases are monthly or daily.
What is the difference between release management and change management?
Change management is the wider governance over any change to a production system, including configuration, infrastructure and vendor updates, and it approves whether a change may happen. Release management is the discipline for one kind of change, the delivery of a software build to users, and it plans how and when that delivery happens. A release is one change record among many, and the release manager works inside the change process rather than instead of it.
Bug reports that arrive ready to triage.
Collect replay, console, network and browser context with the Free plan.