> I assume there's not much reason to be running the B2G emulator tests on beta 
> anymore? If so we should probably temporarily hide them so we don't need to 
> continue checking in test/automation changes there.

That's fine with me - please file a bug.

-Alex

On Dec 12, 2012, at 7:59 AM, Andrew Halberstadt <[email protected]> 
wrote:

> On 12/11/2012 07:10 PM, Alex Keybl 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
>> 
> 
> I assume there's not much reason to be running the B2G emulator tests on beta 
> anymore? If so we should probably temporarily hide them so we don't need to 
> continue checking in test/automation changes there.
> 
> _______________________________________________
> dev-b2g mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-b2g

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to