918034 - b2g branching automation

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[Aki Sasaki (not active)]

B2G branching looks fairly heavyweight at the moment, and will need to happen every ~12 weeks?

There are several parts:

Git branching and manifests.
* We need something to create a branch in all the b2g github repos we control, and update the manifests with the new branch.
* We potentially also have to update the manifests with frozen revisions of external repos.
Details are here: https://groups.google.com/d/msg/mozilla.dev.b2g/JizNVAPFR7A/OcsQnUBKsDAJ
I think the git branching+manifest changes could be done with a mozharness script, but that's not a hard requirement.

Mercurial branching and syncing.
* gecko.git is the main part here; it'll need the new branch synced properly from the appropriate mercurial repository.
* l10n is the other part, and may require its own bug.  We need new gaia-l10n l10n repos every new version; the gecko l10n repository needs to change in vcs-sync every merge day.  (I'm going to be filing a merge day automation bug shortly after this one.)
The merge day stuff can be handled with a mozharness script, but the l10n repo creation etc. requires a bit more cross-team work, so may require docs instead.

I may be missing some stuff here, but we definitely want to automate b2g branching, and we definitely want to get it done before we need to branch for 1.3 (in less than 12 weeks' time).

Comment 1

[Aki Sasaki (not active)]

http://hg.mozilla.org/build/braindump/file/3680e25c4d9a/git-related/b2g-branching/b2g_branch_repos.py suffices for now.  We probably want to improve on it, but that can be tracked elsewhere.