STAGE 07 / CHAPTERS 21-22
Release version 1.0
Rehearse the operating response, protect existing records, and open the checked version under explicit conditions.
THE WORK TO DO
- 01
Send an alert through the actual contact route, including acknowledgment and backup coverage. Rehearse recovery with current records and external effects.
- 02
Identify the release candidate, configuration, transfer point, and compatible return path. Prevent competing writes during the transition.
- 03
Run opening checks, watch the first hours, and keep unfinished actions and existing customer commitments visible.
WHAT YOU LEAVE WITH
A release record, checked operating procedures, assigned coverage, and follow-up work.
BEFORE MOVING FORWARD
Both the identified version and its operating route pass the checks required for opening.
The team's first recovery takes four hours against a one-hour target. After correction, the same complete rehearsal takes 48 minutes.
WHO DOES WHAT / STAGE 07
Make the opening decision with operating evidence.
Client
Decides whether the agreed opening conditions are met.
Tech Lead
Brings technical readiness and remaining issues.
Tester
Identifies the verified candidate and unresolved checks.
DevOps Engineer
Executes the release, recovery, and response preparation.
Senior Administrator
Owns the studio handover and unfinished customer work.
THE HANDOFF
Accepted candidate + operating readiness → controlled opening
The Client makes the opening decision from the evidence. The release owner deploys the agreed candidate; technical and studio responders take over their assigned work.
Work with: Project Manager, Backend Developer, Frontend Developer, Security Engineer, Support Specialist.
Additional expertise when the work needs it: Site Reliability Engineer, Data and Database Specialist, Mobile Developer.
See the team across all eight stages →