== B2G Branching ==
Also see [https://releng.etherpad.mozilla.org/214 this etherpad].
=== Aurora is an even numbered Gecko version ===
When an even-numbered gecko version is merging into mozilla-aurora, 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 [https://bugzilla.mozilla.org/show_bug.cgi?id=913992 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 [http://hg.mozilla.org/build/mozharness/file/19ccf160cb4e/configs/b2g mozharness/configs/b2g] will need to have their versions updated, e.g. [http://hg.mozilla.org/build/mozharness/file/19ccf160cb4e/configs/b2g/releng.py#l46 here]:
<pre>
'mozilla-central': '1.3.0',
</pre>
would become
<pre>
'mozilla-aurora': '1.3.0',
'mozilla-central': '1.4.0',
</pre>
* The [http://hg.mozilla.org/build/mozharness/file/19ccf160cb4e/configs/gaia_bumper/gaia_json.py#l15 gaia-bumper config] will grow to three repositories: central, aurora, and the most recent mozilla-b2gXX branch.
* We'll need new [https://bugzilla.mozilla.org/show_bug.cgi?id=916911 b2g branches]
** Rail has a [http://hg.mozilla.org/build/braindump/file/a889899ca778/git-related/b2g-branching/b2g_branch_repos.py 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|VCS Sync duties]]!
* [https://intranet.mozilla.org/Auto-tools/B2G_Automation/Adding_New_Update_URLs|update.boot2gecko.org needs new versioned update channels]
* tag gecko+gaia for security team
=== Aurora is an odd numbered Gecko version ===
See [https://bugzilla.mozilla.org/show_bug.cgi?id=917433 this bug].
The B2G version in Aurora will move to a new mozilla-b2gXX_v1_X repo.
* file the TBPL page bug ahead of time
* don't forget the graphserver entries
* have the hg repo created ahead of time
* The device configs also need updating to point to gecko beta repositories (see bug 957411)
* Don't forget the [[#VCS_Sync_duties|VCS Sync duties]]!
* tag gecko+gaia for security team
=== Gecko L10n is a special case ===
Gaia l10n will be in version-specific hg repos, e.g. https://hg.mozilla.org/releases/gaia-l10n/v1_2
Gecko l10n will be in: * [http://hg.mozilla.org/l10n-central l10n-central] - new version. On dec 9 this will be 1.4* [http://hg.mozilla.org/releases/l10n/mozilla-aurora releases/l10n/mozilla-aurora] - stabilizing version. On dec 9 this will be 1.3* [http://hg.mozilla.org/releases/l10n/mozilla-beta releases/l10n/mozilla-beta mozilla-beta] - maintenance version. On dec 9 this will be 1.2* [http://hg.mozilla.org/releases/l10n/mozilla-beta releases/l10n/mozilla-release mozilla-release] - EOL version. On dec 9 this will be 1.1 However, b2g gecko l10n only changes repos on even-numbered gecko's in Aurora... meaning b2g gecko l10n migrates every 2 train migrationsprobably remain static until we solve {{bug|967282}}.
== VCS Sync duties ==
