Who Should Approve a New Release or Hotfix?
π New Feature Release
- Approval Required From:
- β Product Manager β Confirms feature readiness and user value.
- β Tech Lead or Engineering Manager β Confirms code quality and test coverage.
- β Principal DevOps β Confirms CI/CD pipeline passed, infra/security checks completed.
- Optional:
- π‘οΈ Security/Compliance Officer β For sensitive or regulated releases.
- π QA Lead β If manual testing or sign-off is still required in staging.
π₯ Hotfix (Production Bug or Security Patch)
- Approval Required From:
- β Tech Lead or Senior Developer β Verifies fix is minimal, safe, and tested.
- β Principal DevOps β Ensures CI/CD passes, patch is secure and tracked.
- β Product Owner or Incident Commander β Confirms urgency and business impact.
- Note:
- Hotfixes may bypass normal release cycles, but must be logged and post-reviewed (retrospective / RCA).
- If a change advisory board (CAB) exists, they may be notified or consulted post-release.