You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
Update versionName in build.gradle for the next milestone (preliminary version number)
String freeze
Make sure all issues with label "strings needed" have strings assigned and the label updated to "strings approved"
Pre-land all strings for features that have not been implemented yet
Export strings and open PR in the L10N repository
Feature complete
Create a branch for the current milestone. After that master is tracking the next milestone. Usually done on the Monday after feature complete on Friday.
L10N sign-off
Import latest strings from L10N repository (into the milestone branch)
If l10n has said that locales should be removed from shipping, remove those locales from the milestone branch. Otherwise, release should include all locales.
Submission
Tag first RC version in Github. For 1.0 the tag would be v1.0-RC1
Build release versions of Klar and Focus
Create Bugzilla bug for signing and uploading the builds
Let release engineering sign the builds and upload the signed builds to Bugzilla
Let release management upload the builds to the Alpha channel (internal distribution)
If the builds passed a smoke test let release management promote the build to the beta channel (public distribution)
Check Google Play for new crashes. File issues and triage.
If bugs are considered release blocker then fix them on master and the milestone branch (cherry-pick / uplift)
If needed tag a new RC version (e.g. v1.0-RC2) and follow the submission checklist again.
Release
Release management promotes the build from beta to the release channel. For minor releases this can happen at any time during the day. Major releases often need to be synchronized with other marketing activities (e.g. blog postings). Releases are rolled out to 99% of the population (otherwise the rollout can't be stopped).
After the release
After some days release management sets the roll out to 100%
Check whether there are new crashes that need to be filed.
Tag the last and released RC version additionally with the tag of the release (v1.0-RC2 -> v1.0)
See Focus for Android Train Schedule
Sprint start
String freeze
Feature complete
L10N sign-off
Submission
During Beta
Release
After the release
The text was updated successfully, but these errors were encountered: