Releases

The Releases view tells you where each release stands, what might block it, and what action is required to move forward safely.

Release View Purpose

Use this view to decide whether to promote, pause, rollback, or close a release. It should combine delivery status, risk signals, and ownership into one timeline.

Release States

Planned -- scoped but not yet deployed.
In Progress -- deployment or rollout actively underway.
Blocked -- cannot continue due to a dependency or failure.
Rolled Out -- delivered to target environment/cohort.
Rolled Back -- reverted to protect reliability.

Release Entry Example

Release: opta-help@2026.03.04.1
State: In Progress
Scope: Status docs + nav wiring
Risk: Low
Blockers: None
Owner: docs-platform
Next Action: validate links in staging, then promote

Pre-release Checks

Validate change scope and rollback path.
Confirm dependent services are healthy.
Ensure on-call/owner assignment is explicit.
Capture go/no-go signal and timestamp.

Rollout Actions

Condition	Action	Owner Response
No regressions in early cohort	Expand rollout	Post timestamped checkpoint
Minor regression with workaround	Hold expansion	Patch and re-verify
Major user-facing breakage	Rollback immediately	Open incident and recovery plan
Unknown state due to missing telemetry	Freeze rollout	Restore observability before proceeding

Post-release Verification

Mark a release complete only after monitoring confirms expected behavior across the intended user scope. A deployment is not finished when shipping ends; it is finished when risk returns to baseline.

Do not close with open blockers

If any critical blocker remains unresolved, keep the release in blocked or rolled-back state and track ownership to closure.

Service Cards