Release Management Foundations
Semantic versioning, branching strategy, changelog generation, release approval workflows, stakeholder communication, and artifact registry management.
Job to be done: When deploys work locally but fail mysteriously in staging or prod due to configuration drift, I want to promote the same artifact through consistent environments with smoke tests and rollback, so I can ship safely without manual fixes.
You will design environment tiers with parity expectations, implement a non-prod CD pipeline that promotes the same immutable artifact across dev and staging, add post-deploy smoke tests, and document fast rollback procedures. Use 12-factor patterns to separate config from code and eliminate environment-specific builds.
What you’ll implement
These are the roadmap epic features, organized as a starter backlog.
Execution guide
Practical guidance aligned to the Execution Kit Definition of Done.
Outcome
Teams deploy safely to non-prod with high environment parity and a clear promotion strategy to prod.
Before to After Transformation
4-hour change windows, manual steps, environment drift, fear of Fridays, incident correlation with releases
# Friday deployment ritual:
1. Send email to stakeholders
2. SSH to prod servers
3. Run deploy.sh manually
4. Watch logs nervously
5. Hope nothing breaks over weekendSame artifact promoted through environments, automated smoke tests, documented rollback, any day is a good deploy day
# Modern promotion flow:
git push origin main
# ✓ CI builds immutable artifact
# ✓ Auto-deploy to staging
# ✓ Smoke tests pass
# ✓ Manual approval for prod
# ✓ Same artifact promoted
# ✓ Rollback: 30 seconds
# DORA improvements:
# - Deployment frequency: weekly to daily
# - Lead time: 7 days to 2 daysSymptoms
Prerequisites
Implementation steps
- Define environment tiers and parity expectations
- Standardize config management (12-factor patterns)
- Create a non-prod deployment pipeline
- Introduce promotion (same artifact) and manual prod gate
- Add smoke tests post-deploy
- Document rollback
- Add progressive rollout in non-prod
- Reduce drift with IaC modules
- Add release notes/changelog automation
Definition of Done
- Non-prod CD pipeline exists
- Same artifact promoted across environments
- Smoke tests run in deployed env
- Rollback is documented and tested
- Practice integrated into team workflow
Metrics
- Lead time commit to staging
- % deploys requiring manual fixes
- % config changes via IaC
- Change failure rate
- MTTR
Failure modes
Ownership
- Provide pipeline patterns
- Provide IaC starter modules
- Adopt promotion flow
- Own service deploy/runbook
What good looks like (by org scale)
- One-click deploy to staging
- Rollback documented
- Promotion pipeline
- Post-deploy smoke tests
- Policy-as-code gates
- Automated evidence capture
References
Resources
Templates and related materials for this kit.
Related capabilities
Capabilities tracked under this epic in the roadmap.
- Semantic Versioning100% of releases follow semver (MAJOR.MINOR.PATCH) with automated changelog generation.
- Release Branch StrategyDocumented branching model applied to >= 80% of repositories with branch protection and merge requirements
- Conventional Changelog GenerationAutomated changelog generation using Conventional Commits for >= 90% of releases
- Release Approval WorkflowRBAC-based release approval requiring >= 2 approvers (tech lead + product owner or SRE) for production releases
- Release Communication ProtocolStandardized release notifications to stakeholders (dev, ops, product, support) for >= 80% of production releases
- Release Artifact RegistryCentralized artifact registry storing >= 90% of release artifacts with version tagging and retention policies
Related kits
Other kits in the same milestone or with similar DORA impact.