Release management with approvals and evidence

Manage software releases from development to production: phases with owners, Pre and Production committees, milestones and install evidence.

2 min read

What release management covers

Release management plans, schedules and controls how changes reach production. It coordinates people and environments so a release arrives when promised, works as expected and can be rolled back if needed.

The eleven phases of a deployment

New, Development, Code Review, Test, To Committee, Committee Authorized, Installed Pre, To Committee Prod, Committee Prod Authorized, Installed Prod and Done. Each phase has an owner role and a condition for leaving it.

Release management in DevGob

  • Owners per change: development, testing, release manager and requester.
  • Committed and actual dates for every milestone, on a timeline.
  • A workspace-wide committee agenda and minutes for each session.
  • Install evidence in pre-production and in production.
  • Rollback with a mandatory reason and an automatic severity-1 bug.
  • Duplicate a deployment to repeat a release pattern.

Data changes have their own flow

A change to production data is authorized by different people than a code release. DevGob's Data Change flow keeps the business authorization and the database authorization apart, with a confirmed backup and an execution window.

How DevGob helps

DevGob gives each release a governed path with owners, dates, approvals and evidence, from development to production.

Read it in the documentation

Frequently asked questions

What is a deployment in DevGob?

The governed record of one change on its way to production. Several deployments can hang from the same feature or epic.

Can I see every scheduled release?

Yes: the deployments board by phase, the committee agenda and the milestones in the reports. A dedicated change calendar is on the roadmap.

Who approves a release?

A committee approver, by role, at each gate; the decision is recorded with its minutes number.

Keep reading

CI/CD governance: integrated CI/CD orchestration Keep your CI/CD pipelines and add what they lack: committee approvals, environment gates, install evidence and an audit trail for every release. Software risk management for changes Reduce the risk of every software change: risk level and change type, rollback plans, staged validation and committee approval before production. What is a change advisory board (CAB)? The change advisory board explained: what it reviews, who takes part, how it treats normal, standard and emergency changes, and how to keep it lightweight. Two committees, not one: authorizing pre-production and production Why DevGob splits change authorization into a pre-production gate and a production gate, and what the second committee sees that the first one cannot. Software change auditing and audit evidence Answer any audit about your software changes: who requested, built, tested and approved each one, with a signed evidence package per change.

DevOps with governance, on one record

DevGob plans the work and governs every change on its way to production: backlog, sprints, committee authorizations, install evidence and an audit trail.

Request a workspace Documentation