Your expectation that we'll still be taking major cross-platform changes to Gecko that late in the 17 cycle does not line up with the planning being done in the B2G dev team. If at any point it becomes clear that we need to pull B2G v1's Gecko off the trains for the sake of other products' qualIty, we'll create a separate branch entirely. We agreed that based upon current planning, it made more sense to be reactive than proactive here.
-Alex Justin Dolske <dol...@mozilla.com> wrote:On 8/1/12 2:47 PM, Alex Keybl wrote: > ... and on 11/19 work will move to the mozilla-esr17 branch. I don't really understand this, perhaps I am missing something? ESR and a v1.0 product seem inherently at odds. EG, I would assume that B2G will be making substantial and even high-risk changes right up to the day of release (and afterwards, should a 1.1 thing be needed). That's obviously different than ESR's primary goal, and even aurora/beta. I would have guessed B2G would want to create something like a "mozilla17-b2g" branch -- a stable (wrt non-B2G changes) Gecko 17 base, pulling in changes from aurora-17 / beta-17 as those trains run. But also allowing any changes B2G wants without worrying about impact to other products. Justin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
