Software release process flowchart

Software release process flowchart

A worked example to adapt. Rename steps, add branches and owners to match how your team actually works.

flowchart TD
  s(["Release scope agreed"])
  br["Cut release branch"]
  qa["Regression testing"]
  d1{"Blocking bugs found?"}
  fix["Fix and re-test"]
  notes["Write release notes"]
  go{"Go/no-go approved?"}
  roll["Staged rollout"]
  d3{"Errors above threshold?"}
  back["Roll back and fix forward"]
  e(["Full release"])
  s --> br
  br --> qa
  qa --> d1
  d1 -->|Yes| fix
  fix --> qa
  d1 -->|No| notes
  notes --> go
  go -->|Go| roll
  go -->|No-go| fix
  roll --> d3
  d3 -->|Yes| back
  d3 -->|No| e
  back --> qa

About this software release process flowchart

Release management is about controlled risk. This flowchart shows the gates a release passes: regression testing with a fix loop, a go/no-go decision, and a staged rollout watched against an error threshold with a rollback path.

It fits teams shipping scheduled releases of web, desktop or mobile apps. Teams doing continuous delivery can use the CI/CD pipeline flowchart instead.

Step by step

1. Branch. Cut a release branch from the agreed scope.
2. Test. Run regression tests; blocking bugs loop through fix and re-test.
3. Approve. Release notes are written and the go/no-go meeting decides.
4. Roll out. Release to a small share of users first.
5. Watch. If errors pass the threshold, roll back, fix and return to regression testing; otherwise release to everyone.

How to make it in flow-chart.io

1. Start from the example. Edit the text in the generator box above so it names your own release stages and environments, then press Generate. The free preview needs no sign-up.
2. Add the branches. Add the decision points that matter for you, for example app store review? or feature flag rollout?. Each decision becomes a diamond with labeled outcomes.
3. Assign owners. Save the diagram to the editor (free account) and rename steps to show who does what: engineering, QA, product and on-call.
4. Share or export. Share a read-only view link: people with the link can view the diagram but not edit it. Downloads as PNG, SVG or PDF are part of Flow Pro (see pricing).

Tips

• Agree the rollback threshold before rollout starts.
• Keep the go/no-go criteria written down.
• Practice the rollback, not only the release.

Frequently asked questions

What is a staged rollout?

Releasing to a small percentage of users first and widening the release as metrics stay healthy.

How is this different from a CI/CD pipeline?

A CI/CD pipeline automates build, test and deploy on each change. A release process adds human gates such as go/no-go and release notes.

Can I generate my own release flow?

Yes. Edit the steps in the generator box and press Generate.

Related