Release Management (Deep Workflow)

Releases combine coordination and risk management: what ships, when, how we verify, and how we recover.

When to Offer This Workflow

Trigger conditions:

• Scheduled or train-based releases; need predictable cadence
• Hotfix chaos or unclear ownership
• SemVer vs calendar versioning debates

Initial offer:

Use six stages: (1) versioning policy, (2) branching & tags, (3) release candidate & checklist, (4) communication, (5) deploy & verify, (6) post-release & hotfixes). Confirm deployment model (continuous delivery vs batch releases).

Stage 1: Versioning Policy