-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Android Release Checklist
Kamil Jozwiak edited this page Apr 25, 2022
·
2 revisions
Feel free to copy this into an issue if you want to keep track of items per-milestone. Be super sure that is replaced with the version you wish to use.
- Double check the previous release/milestone and ensure everything has been QA'd
-
Note: If there's issues that need to be checked, create a
master
GH issue that lists the issues that need to be QA'd
-
Note: If there's issues that need to be checked, create a
- Ensure that the RC can be launched via the GPS internal test channel (basically verifying that
.aab
updates are working) - Consult with the security team to ensure that all security issues have been included.
- Release using the
critical
feature (forces users to update/restart) if there's a zero day vulnerability being exploited
- Release using the
- Consult with PR team (@catherinecorre) and provide heads up on release timing, screenshots, other deliverable's.
- Download the latest version of ClassyShark3xodus and ensure that zero trackers are found within Brave.
- Once scanned, ensured that selecting
Settings
->Sub Totals
also displays zero trackers
- Once scanned, ensured that selecting
Good Example (Brave) |
Good Example (Brave) |
Bad Example (Firefox) |
---|---|---|
- Mark closed issues in github as
release-notes/exclude
orrelease-notes/include
. - Commit release notes to CHANGELOG_Android.md in the
brave-browser
master
branch - Stage release notes to https://github.com/brave/brave-browser/releases/