Release Process

Creating a new Release Branch

1. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.
2. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.

For example:

| FILE | CURRENT VERSION | RELEASE VERSION | |--------------------|--------------------|-----------------| | AndroidComponents | 73.0.20210223143117| 73.0.0 |

For reference, the AC release checklist can be found at https://mozac.org/contributing/release-checklist. Instead of updating the AC version manually, you could also wait for automation to update the ac version.

1. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.
2. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.
3. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.
4. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.

Automation should take over after you land your PR into the upstream releases_v[version] branch. You can verify by clicking on the branch in the UI, and looking for the green/yellow dot that will list links to the running build tasks.

After the Beta release

Update the versionName from build.gradle(Module:focus-android.app) to the next Focus beta release version.This should be the [version + 1]. For example, if the release cut was for 90, we're looking to prepare the latest nightly for 91. For example:

| FILE | CURRENT VERSION | RELEASE VERSION | |--------------------|--------------------|-----------------| | build.gradle | 90 | 91 |

Renew telemetry

After the Beta cut, another task is to renew/remove all soon to expire telemetry probes. What we're looking for is to create a list of telemetry that will expire in [release_version add 2]. See Firefox Release Calendar for the current Release version. There is a script that will help with finding these soon to expire telemetry.

1. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.

- [release_version add 2]expirylist.csv - [release_version add 2]renewalrequest.txt

1. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.

- Renew the metric (for how long? Add 12 versions?) - Choose not to renew (but not delete) - Choose to remove the metric - Renew the metric and set to never expire (this should only be for business critical metrics)

1. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.
2. It takes ~30 seconds to run. If you think this hook takes too long, you can remove the unit test line and it becomes almost instant.

- When will this collection now expire? - Why was the initial period of collection insufficient?

Ask for Help

If you run into any problems, please ask any questions on Slack in #releaseduty-mobile.

References:

• https://github.com/mozilla-mobile/focus-android/tree/releases_v96.0
• https://github.com/mozilla-mobile/focus-android/pull/6012