ReleaseEngineering/Merge Duty/Central will become an odd numbered Gecko version

Overview

When a mozilla-central is an even numbered Gecko version and will become an odd numbered Gecko version, the B2G version on mozilla-central will migrate into mozilla-aurora, and a new B2G version will start on mozilla-central. For B2G 1.3, when Gecko 28 merges into mozilla-aurora, mozilla-central will become 1.4 and mozilla-aurora will be 1.3.

This means we'll have to turn on B2G builds+tests for mozilla-aurora. See bug 913992 for an example.

• We'll need a new Gaia hg repository, e.g. https://hg.mozilla.org/integration/gaia-1_2/
  • This will have to be added to vcs-sync
• We'll probably need new Gaia l10n hg repositories, e.g. https://hg.mozilla.org/releases/gaia-l10n/v1_2
  • These will have to be added to vcs-sync
• The versions in the releng*.py files in mozharness/configs/b2g will need to have their versions updated, e.g. here:

'mozilla-central': '1.3.0',

would become

'mozilla-aurora': '1.3.0',
'mozilla-central': '1.4.0',

• The gaia-bumper config will grow to three repositories: central, aurora, and the most recent mozilla-b2gXX branch.
• We'll need new b2g branches
  • Rail has a script

• The device configs in aurora need updating to point to the new b2g manifest branch. e.g. http://hg.mozilla.org/releases/mozilla-aurora/rev/b1c4f85913d1 (see bug 950166 for example)
• The device configs also need updating to point to gecko aurora repositories and the new gaia l10n repositories (see bug 957411)
• the mozilla-central b2g version will need bumping, e.g. http://hg.mozilla.org/mozilla-central/rev/289d0d34ded7 This should be done by RelMan, but worth the double check.
• Don't forget the VCS Sync duties!
• needs new versioned update channels
• tag gecko+gaia for security team

Two weeks before

• File a bug for new Gaia and Gaia l10n hg repositories
• Add new Gaia and Gaia l10n to vcs-sync

Release Merge Day

• bump the mozilla-release version in buildbot-configs
  • Historically, we also need to look for MERGE DAY comments in buildbot-configs.
• mozilla-beta -> mozilla-release migration

One week before

• Prep for merging the B2G version from central -> Aurora. This will go live on Merge Day.
• Prep for Creating new b2g git branches. This is a staging run to make sure you don't hit any weird issues on Merge Day. Ideally you re-do this on Merge Day so the branches aren't created too early, or from too-early revisions.

Merge Day

• Create new b2g git branches
• Merge the b2g version from central to aurora
• ReleaseEngineering/Merge_Duty/Steps#EOL_a_B2G_branch, if appropriate.

Post merge day

dev.b2g newsgroup post

Like this:

We have created the v1.3 branch in all git repos. The master branch is now reserved for 1.4 development. For more information, see the page below which always contains the latest information.
https://wiki.mozilla.org/Release_Management/B2G_Landing#v1.3.0

Update this documentation

The next person on merge duty will appreciate it!