We'd discussed this, but due to current dev status and scheduling, drivers now feel that there's a good chance of needing to branch B2G's Gecko before it's on mozilla-release to limit risk to desktop/mobile, which would nullify any delays meant to keep B2G tied to the next ESR.
In terms of longterm ESR stability/security maintainability, we'll benefit from the fact that IonMonkey and other major changes are landing after the 17 branch. Landing Gecko fixes on Firefox branches, ESR, and now B2G is of course the downside here. -Alex On Sep 4, 2012, at 12:49 PM, Kyle Huey <m...@kylehuey.com> wrote: > On Tue, Sep 4, 2012 at 12:34 PM, Alex Keybl <ake...@mozilla.com> wrote: > I'd like to provide everybody with an update about this plan. "B2G v1" > platform work is continuing on mozilla-central as we speak, and therefore > will not be a part of FF17 (currently on Aurora) given the risk of uplifting > new work. Unfortunately, this also means that ESR17 will not be the longterm > support branch for B2G v1. > > Are we considering "holding" the ESR until B2G is ready to go? Continuing to > support ESR10 for a while longer may be less painful than supporting ESR17 > and also Gecko 18 or 19 or whatever at the same time. > > - Kyle _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
