Launch quality program
A shared operating brief for the final two weeks before Atlas 4.8 ships. Decisions, owners, evidence, and the live task database stay connected here.
- Status
- On track
- Target
- August 14, 2026
- Owners
- MRSKJL
- Progress
- 5 of 8 complete
What must be true at launch
The release is ready when the highest-risk user journeys are verified on real devices, support has a clear escalation path, and owners can explain every remaining exception.
Decision rule
Unknown behavior blocks the release. A known limitation may ship only with an owner, user-facing language, and a dated follow-up.
Unknown behavior blocks the release. A known limitation may ship only with an owner, user-facing language, and a dated follow-up.
Decisions already made
- Keep the rollout staged at 10%, 35%, then 100%.
- Use the existing account recovery path; defer the redesigned flow.
- Publish the migration guide before the production promotion.
Open question
Can the Android keyboard regression be contained to the new compose surface, or does it affect the existing editor as well?
TaskStatusOwnerDue
DoneMaya R.Aug 7
DoneSoren K.Aug 8
ReviewJordan L.Aug 10
In progressInez P.Aug 11
DoneAri K.Aug 6
DoneMaya R.Aug 6
DoneSoren K.Aug 5
QueuedJordan L.Aug 14
Evidence freeze
Every blocking check has a linked run, owner, and timestamp.
Release candidate
Final mobile build enters the staged rollout rehearsal.
Go / no-go review
Owners explain exceptions and confirm support coverage.
Production promotion
Begin at 10%, observe, then promote through the agreed thresholds.