All - the cutover to mozilla-b2g18 has been completed. B2G's Gecko checkin repository is now hg.mozilla.org/releases/mozilla-b2g18. Please make your commits there.
The last commit from mozilla-beta sync'd to mozilla-b2g18 was 3bf8ca7f948c (http://hg.mozilla.org/releases/mozilla-b2g18/rev/3bf8ca7f948c). If you landed on mozilla-beta after that, you'll need to double commit to mozilla-b2g18. The gecko-18 branch on git.mozilla.org/releases/gecko.git is now tracking mozilla-b2g18, but may take a bit to catch up. --Hal On 2012-12-11 18:18 , Alex Keybl wrote: > Hal is now putting the finishing touches on mozilla-b2g18, and will email > once completed. Until he emails, please do not land B2G fixes on mozilla-beta > or mozilla-b2g18. Once he emails, the rules below will apply. Thanks all! > > -Alex > > On Dec 11, 2012, at 4:10 PM, Alex Keybl <[email protected]> wrote: > >> To limit risk to Firefox 18 desktop/mobile, we're branching mozilla-beta to >> a new repo, mozilla-b2g18, once we go to build with Firefox 18 beta 4. I'll >> email when the switch is made later this evening. >> >> B2G Engineers: >> * After I email again later this evening, all B2G-specific >> blocking-basecamp+ Gecko changes must land on mozilla-central, >> mozilla-aurora, and mozilla-b2g18 (*not* mozilla-beta) >> * Fixes that are resolving regressions affecting FF18 need to be nominated >> for approval on mozilla-beta as well (use approval-mozilla-beta?) >> * Changes that aren't b-b+ must go through >> approval-mozilla-aurora/approval-mozilla-b2g18 triage >> * If you have any questions about moving your local builds from mozilla-beta >> to mozilla-b2g18, please contact Hal Wine >> >> Sheriffs: >> * Any new patches landed on mozilla-beta in the FF18 timeframe will also >> need to be landed to mozilla-b2g18 (should just be a merge). After FF18 >> ships, this responsibility will fall upon individual engineers (as with the >> ESR10/17 branches) >> >> All: >> * Once a Gecko change has landed on mozilla-b2g18, please set the upcoming >> status-b2g18 flag accordingly >> * You'll also notice the creation of tracking-b2g18 and blocking-b2g. Both >> of these flags are for post-1.0 work, and you can ignore them for now. >> * We are *not* yet moving to approvals only for all B2G bugs, given the low >> regression rate recently and our desire to get out of your way. If that >> changes before C4 (2013), we'll make sure to let you know. >> >> https://etherpad.mozilla.org/b2g-convergence-landing has been updated to >> reflect this information. >> https://bugzilla.mozilla.org/show_bug.cgi?id=820574 is tracking the creation >> of new flags mentioned above. You can find the mentioned hg repo at >> https://hg.mozilla.org/releases/mozilla-b2g18/. >> >> -Alex >> _______________________________________________ >> dev-gaia mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-gaia _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
