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.

Subscribe to devsecopsbook

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe