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.
-Alex On Aug 1, 2012, at 2:47 PM, Alex Keybl <ake...@mozilla.com> wrote: > Release drivers for the B2G project recently got together to discuss > committing to a specific Gecko version for B2G v1**, and we've all agreed on > Gecko 17 making the most sense from the point of view of technical > requirements, resourcing, testing, and timelines. Platform changes for B2G > have been occurring on mozilla-central, and builds of B2G will continue to > pull in mozilla-central's Gecko until the 8/27 merge. > > At that time, Gecko 17 will move from mozilla-central to mozilla-aurora. > 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. > Intermediate deliverables would be built using Gecko from mozilla-aurora. And > contributed "B2G v2" platform work could continue on mozilla-central. > > On 10/7, we'll similarly move active B2G v1 platform development to > mozilla-beta, and on 11/19 work will move to the mozilla-esr17 branch. A > notice referencing this dev.platform post will be sent to the enterprise list > shortly for comment, as some of the ESR goals in [1] will need to change > slightly. > > We've discussed concerns around actively developing a 1.0 product while the > underlying version of Gecko moves through the trains (mostly from a B2G > regressing desktop/mobile/ESR point of view). The large majority of > cross-platform architectural changes will occur before FF17 comes off of m-c, > and most of the fixes in support of B2G that happen after that date will be > B2G-specific. For that reason, we mostly see benefit to the cross-pollination > of testing that will occur between B2G and other Gecko 17 supported platforms. > > One thing to keep in mind is that B2G is now an equal citizen on branches > carrying FF17. Except in extreme circumstances, any desktop/mobile change > that negatively impacts B2G builds in a significant way will be backed out > (and vice versa). > > Please let us know if you have any questions, or if anything could use > further clarification. Please also see [2] for a similar conversation > happening around Gaia v1 convergence if interested. Thanks! > > -Alex Keybl > Release Manager, Mozilla > > > ** Please note that "B2G v1" just denotes the first version of the B2G > project available on publicly available hardware > [1] https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal > [2] > https://groups.google.com/group/mozilla.dev.gaia/browse_thread/thread/008812000dccb65c# > _______________________________________________ > 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
