Release Process
Our app ships on a two-week sprint cycle. A release branch is cut on the first day of the sprint and the app goes live on the last day.
Timeline
| Sprint Day | Day of Week | What Happens |
|---|---|---|
| 1 | Wednesday | Release branch cut from develop. RC builds created for QA. Release ticket and Slack thread created automatically. |
| 1-5 | Wed - Mon | QA runs regression testing against the RC build. Any required fixes are cherry-picked to the release branch. |
| 3-5 | Fri - Mon | QA and Product approvals given through GitHub environment gates. |
| ~7 | Mid-sprint | Release branch merged to main. Production builds submitted to App Store (review) and Play Store (Pre-Prod track). |
| 14 | Tuesday | Go Live: builds promoted to production in both stores. |
Need More Detail?
- Step-by-step operational guide: Release Runbook — workflow chain, checklists, and decision trees
- Something went wrong?: Release Issues — troubleshooting and recovery procedures
- Upcoming release dates: Release Calendar
Go Live runs every Tuesday
The Go Live workflow runs every Tuesday, not just on release Tuesdays. On non-release weeks it has no effect, but if a release is approved and built early, it will go live on the next Tuesday regardless of whether that's the intended date.