Owner Superman

Android Release Process (dummy)

We ship weekly. The process is deliberately boring.

Branches

  • main is always releasable.
  • Release branches are cut on Mondays: release/YYYY-WW.
  • Hotfixes are branched from the most recent release tag and merged back to main.

Steps

  1. Cut release/YYYY-WW from main.
  2. Bump versionName and versionCode.
  3. CI builds a signed bundle and uploads it to internal testing.
  4. QA runs the regression checklist.
  5. Promote to closed testing for a day.
  6. Promote to production with a 10% staged rollout, widening over 48 hours if metrics look clean.

What counts as “clean”

  • Crash-free sessions above 99.7%.
  • ANR rate within 10% of the previous release.
  • No P0 or P1 bugs opened in the first 24 hours.

If any of those fail, we halt the rollout and decide: roll back, hotfix, or accept.