Release Management: prepare, deploy, and recover
Six lessons, 30 questions, and six cases on scope, artifacts, readiness, progressive exposure, recovery, handover, and component retirement.
Objectives and progression
A six-module technical course with fictional production situations. Learn to coordinate dependencies and scope, promote reviewed artifacts, check authorization controls, interpret a canary, calculate recovery limits, and transfer capability to support. Includes data rollback limits, documented pipeline behavior, primary references, and an internal assessment of 24 decisions in 60 minutes.
Audience: APS L2/L3, infrastructure, SRE, systems administration teams, and technical managers.
Prerequisites: Application, monitoring, and production-support fundamentals; no bank-specific internal process assumed.
300 estimated study minutes
- Coordinate what changes, who depends on it, and when functionality becomes available.
- Ensure the approved package matches what will be deployed and recovered.
- Use observable criteria to decide whether the release may proceed.
- Increase exposure only when observation supports the next stage.
- Choose recovery compatible with current state and available time.
- Deliver operational capability and retire old dependencies using evidence.
Modules
- Scope and coordination
- Artifacts and traceability
- Readiness and authorization
- Exposure and observation
- Recovery and compatibility
- Handover and lifecycle
Continue learning
References and version
Release management practices 2026-09; scoped GitLab GitHub CodeDeploy and EF Core documentation
- Progressive exposure health gates emergency protocols and decommissioning · 2026-09-30
- Reproducible builds versioned artifacts and release traceability · 2026-09-30
- Representative canary evaluation and feature exposure · 2026-09-30
- Automated testing and outcome-based rollback conditions · 2026-09-30
- Deployment concurrency stale jobs and protection controls · 2026-09-30
- Environment protection approvals and secret availability · 2026-09-30
- Rollback redeployments and limits on script side effects · 2026-09-30
- Release contents operational coordination and API compatibility · 2026-09-30
- Migration ordering exact reviewed scripts and rollback data limits · 2026-09-30
- Launch coordination dependencies capacity and operational processes · 2026-09-30
- Incremental replacement coexistence and decommission prerequisites · 2026-09-30
- Contextual operational readiness across the service lifecycle · 2026-09-30
- Deploy freeze configuration and CI_DEPLOY_FREEZE enforcement · 2026-09-30
- Resource group serialization versus execution ordering · 2026-09-30
What you will explore
0 / 6Scope and coordination
Coordinate what changes, who depends on it, and when functionality becomes available.
Artifacts and traceability
Ensure the approved package matches what will be deployed and recovered.
Readiness and authorization
Use observable criteria to decide whether the release may proceed.
Exposure and observation
Increase exposure only when observation supports the next stage.
Recovery and compatibility
Choose recovery compatible with current state and available time.
Handover and lifecycle
Deliver operational capability and retire old dependencies using evidence.