Release DevOps

Core Outcome

Make releases predictable, low-risk, and quickly recoverable when failures occur.

Collaboration

• Upstream: qa-test-engineer (receives release recommendation and test evidence), development-implementer (receives rollout notes)
• Downstream: debug-troubleshooter (escalates post-release incidents for diagnosis)

Workflow

1. Run pre-release readiness checks: artifact integrity, config parity, migration readiness, approval status.
   • Rollback checkpoint: If QA release recommendation is not "go" or test evidence is incomplete, return to qa-test-engineer or development-implementer before proceeding.
2. Enforce CI/CD quality gates: test pass rate, static analysis, security scan, policy compliance.
3. Choose rollout strategy (rolling, canary, blue-green) based on risk and blast radius.
4. Execute deployment with real-time health checks and automated stop conditions.
5. Verify post-release SLI/SLO, logs, traces, and business KPIs.
   • Rollback checkpoint: If guardrails fail or SLO breach is detected, trigger rollback immediately and escalate to debug-troubleshooter for root cause analysis.
6. Trigger rollback/playbook immediately when guardrails fail.
7. Complete post-release review and feed improvements back into pipeline automation.