> Can you clarify this? It sounds like changes would land on aurora *first*, > and then be forward-ported to mozilla-central. Which, IMO, goes against the > basic principles of how our branches work.
Sure thing. All platform agnostic Gecko changes will continue to only be uplifted once we gain confidence with our test audience on m-c (and higher, depending on where 17 is). All B2G-specific changes (#ifdef B2G, changes to APIs unused in Firefox desktop/mobile, etc.) landing once FF17 leaves mozilla-central will also go through the normal branch approval processes. I expect a large majority of these changes to be landing on 17 and up simultaneously, as internal/external B2G testing will be focused on the 17 branch. Only in the very rare instance where B2G v2 (Gecko changes in 18 and up) has diverged too significantly to easily forward-port a patch, will we land B2G-specific changes on FF17 only. The goal here is to keep B2G devs and QA focused only on the shipping 17 branch wherever possible, as long as it poses little to no risk to future desktop/mobile Firefox versions. -Alex On Aug 1, 2012, at 6:43 PM, Blair McBride <bmcbr...@mozilla.com> wrote: > On 2/08/2012 9:47 a.m., Alex Keybl wrote: >> Active Gecko platform changes in support of B2G v1 will move to >> mozilla-aurora, with changes of course being merged back to m-c as >> well > > > Can you clarify this? It sounds like changes would land on aurora *first*, > and then be forward-ported to mozilla-central. Which, IMO, goes against the > basic principles of how our branches work. > > - Blair _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
