Software Release Management

A versioning scheme, branching model and written release process, go or no-go reviews, honest changelogs, rehearsed rollbacks and the communication that tells people what changed.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Software Release Management, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Software Release Management

Planning and running software releases, versioning, release branches, changelogs, rollbacks and the communication around each release.

  1. Inventory of every component you release
  2. Choosing semantic or calendar versioning
  3. Release branching model decision
  4. Release roles and responsibilities charter
  5. Changelog file and commit message convention
  6. Written release runbook from merge to announcement
  7. Rollback plan for each release type
  8. Build once and promote the same artefact
  9. Release cadence and calendar decision
  10. Weekly go or no-go release review
  11. Release notes for every version
  12. Release captain rotation
  13. Hotfix lane and emergency release procedure
  14. Code freeze and stabilisation window
  15. Backport and patch release routine
  16. Post-release verification checklist
  17. Live versions dashboard
  18. Release health log
  19. Monthly release retrospective
  20. Release communication to support, sales and customers
  21. Semantic versioning rules in practice
  22. Tags, signed tags and release branch mechanics
  23. Writing release notes people actually read
  24. Sequencing database changes across releases
  25. Staged rollouts and halt criteria
  26. Lessons from public release failures
  27. Change management frameworks for releases
  28. Automated changelog and version bump
  29. Moving from monthly releases to a weekly train
  30. Choosing a release orchestration tool
  31. Separating deploy from release with feature flags
  32. Shortening the time from release cut to production
  33. Pre-approved standard changes for routine releases
  34. First major version launch
  35. Deprecating and sunsetting an old version
  36. Peak-season change freeze plan
  37. Coordinated multi-team launch release
  38. Rollback drill
  39. Releasing as a solo engineer
  40. Taking over release management from a departing owner
  41. First repeatable release process for a startup team
  42. Change advisory board submissions
  43. Releasing to on-premise and self-hosted customers
  44. Release controls in a regulated environment
  45. Long-term support branch policy
  46. Version compatibility matrix across services
  47. Signed release artefacts and provenance
  48. Release candidate and beta channel programme
  49. Release risk scoring for each change set
  50. End-of-life policy and yearly support review

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Inventory of every component you release

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most teams can name their main app but not the worker image, the CLI, the SDK on a package registry and the database migration bundle that ship alongside it, each with its own version and owner.

First tasks

  • List every repository that produces something users or other teams install
  • Record where each component is published, from registries to app stores to servers
  • Check the live version of each component in production and write it down
  • Flag components with no clear owner and raise them at the next team meeting

Choosing semantic or calendar versioning

Version numbers are a promise to the people who depend on you: semantic versioning promises that a major bump means breaking changes, while calendar versioning promises nothing about compatibility but tells everyone how old a build is. Libraries and APIs usually need the first, products shipped on a train often suit the second, and mixing them by accident confuses everyone.

First tasks

  • Read the semantic versioning specification and one calendar versioning example
  • Group your components by who consumes them
  • Write the breaking change rule for libraries and public APIs
  • Publish the versioning decision in the engineering handbook

Release branching model decision

Whether you release straight from trunk with tags, cut a short-lived release branch, or keep long-running maintenance branches decides how hotfixes flow, how often merge conflicts appear and how many versions you can patch at once. Teams that never chose usually end up with a half-remembered GitFlow nobody follows.

First tasks

  • Sketch how your team actually branches and tags today
  • Compare trunk with tags, short release branches and maintenance branches
  • Write the rule for where a fix is merged first
  • Update branch protection on each releasable repository to match

Make it yours.

Install Software Release Management, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.