Alpha-Beta-GA Release Strategy
- Eric Sethna
Alpha
iOS Beta App
Closed Track: Add v2 testers via email to this track. Do demo in COM + survey in announcements channel to collect email, mobile OS, CRT state.
Open Track: v1 updates
Testers can flip between build using the “Previous Builds” option in TestFlight
iOS Production App
No changes.
We will continue to ship v1 updates as necessary to production. QA will use the closed track for release testing.
Android Beta App
Alpha track: Add v2 testers via email to this track. Do demo in COM + survey in announcements channel to collect email, mobile OS, CRT state.
Beta track: v1 updates
Android Production App
No changes.
We will continue to ship v1 updates as necessary to production. QA can use APK files for beta app for release testing.
Beta
iOS Beta App
Closed Track: We don’t have to use it unless we want to test new v2 builds before we push them to the open track
Open Track: Publish the beta v2 build to the open track
iOS Production App
No changes.
We will continue to ship v1 updates as necessary to production. QA will use the closed track for release testing.
Android Beta App
Alpha track: We don’t have to use it unless we want to test new v2 builds before we push them to the beta track
Beta track: Publish the beta v2 build
Android Production App
No changes.
We will continue to ship v1 updates as necessary to production. QA can use APK files or the beta track for release testing.
GA
iOS Beta App
No change from beta stage
iOS Production App
Push the v2 build to production. QA will continue to use the closed track for release testing.
Android Beta App
No change from beta stage
Android Production App
Push the v2 build to production. QA can use APK files or the beta track for release testing.