Before the release

  • Make sure version number is correct or update version in .buildconfig.yml.
  • Update CHANGELOG
    • Use milestone and commit log for identifying interesting changes.
    • Add the milestone to any related issue that doesn’t have it.
  • Close milestone
    • Milestone should be 100% complete. Incomplete issues should have been moved in planning meeting.

Release

  • Create a branch with the format releases/[major_version].0, for example, releases/49.0.
  • Create a new tag/release on GitHub.
    • Tag: v2.0 (v prefix!)
    • Release 2.0
  • Wait for taskcluster to complete successfully.
  • Check that new versions are on maven.mozilla.org:

Minor releases

Making a minor release has a couple extra steps to do before a regular release:

  • Create a branch with the format releases/[major_version].0, for example, releases/49.0.
  • Cherry-pick the changes to the new branch.
  • Create the tag and release from this branch instead.

After the release

  • Send release message to the Matrix channel: 
    **Android Components 0.17 Release (:ocean:)**
Release notes: https://mozilla-mobile.github.io/android-components/changelog/
Milestone: https://github.com/mozilla-mobile/android-components/milestone/15?closed=1
  • Update version number in repository
  • Create the next milestone