We make 2 production app releases each week. Before each production release, there is a corresponding internal version in a release branch for us to catch any bugs to fix. We also have additional internal nightly builds for faster distribution of changes to employees/testers.
Also see:
| TUE | WED | THU | FRI | SAT | SUN | MON | |
|---|---|---|---|---|---|---|---|
| **Night-time | |||||||
| 2am PT / | |||||||
| 5am ET** | Start creating Nightly Build 1 | Start creating Internal Build A | Start creating Nightly Build 2 | Start creating Nightly Build 3 | Start creating Internal Build B | ||
| What changes are included in the build? | Everything on master. | Everything pushed in code before building is included in Internal Build. | Everything on master. | Everything on master. | Everything pushed in code before building is included in Internal Build. | ||
| When is build available? | Available for internal test Tue morning. | Available for internal test Wed morning. | Available for internal test Thu morning. | Available for internal test Fri morning. | Available for internal test Sat morning. | ||
| **Evening | |||||||
| 5pm PT / | |||||||
| 8pm ET** | Start creating Public Build A | Start creating Public Build B | |||||
| What changes are included in the build? | Dev has opportunity to include one-off bug fixes before Public Build is submitted. | Dev has opportunity to include one-off bug fixes before Public Build is submitted. | |||||
| When is build available? | Start rolling out to users Thu/Fri (depends on approval speed) | Start rolling out to users Tue/Wed (depends on approval speed) |
The “Finch Dev” calendar has the release schedule marked on the calendar as well. Ask #dev-idk if you want access.
Usually it takes 3 days for 50% of DAUs, 4 days for 70% of DAUs.