Field note
Choosing a release window when the train never stops
For teams with continuous delivery, a release readiness review still needs a freeze language—here is how we write change windows that match rolling deploys.
Continuous delivery teams sometimes skip readiness reviews because “we deploy all the time.” The risk does not disappear; it moves into feature flags, migration order, and customer communications that still need a clock.
Freeze language that fits rolling deploys
Instead of “no deploys Friday,” try:
- No schema migrations without a paired rollback script reviewed by two owners
- No flag defaults flipped for the top revenue journey after 16:00 Taiwan time
- On-call must include someone who can disable the flag path without a full revert
A release readiness review translates those rules into a go / conditional-go note for a named date—even when the pipeline itself never sleeps.
A small ritual that helps
Forty-eight hours before the customer-facing moment (launch email, rate change, region open), walk the checklist with the people who will be awake—not only the architects who designed it. If the night shift cannot parse a step, rewrite the step before you rewrite the architecture.