Yeah, my take is that at this point the desire to improve B2G performance (comment 61) >> the risk of subtle breakage, especially given the number of people with eyes on B2G v1 ahead of release. If anybody's got specific areas that we can QA on the phone, please do comment in the bug and we can get a QA Contact assigned. Worst case scenarios for B2G post-release would be helpful as well.
-Alex On Oct 30, 2012, at 1:41 PM, Justin Lebar <justin.le...@gmail.com> wrote: > On Tue, Oct 30, 2012 at 4:31 PM, Dave Townsend <dtowns...@mozilla.com> wrote: >> This plan really worries me. [...] I'm worried that we'll just break the >> platform b2g runs on in subtle ways that we might not notice before shipping. >> It's pretty concerning to have a fundamental change to how components and >> modules are loaded on a new platform where to my knowledge we don't yet have >> good automated testing (please please someone prove me wrong on this). > > I think we all share your concern; you'll see a fair bit of discussion > about this in the bug. > > But this change gets a huge memory win on a highly-memory-constrained > device, and we don't have an alternative which would be ready in time. > > https://bugzilla.mozilla.org/show_bug.cgi?id=798491 > > On Tue, Oct 30, 2012 at 4:31 PM, Dave Townsend <dtowns...@mozilla.com> wrote: >> On 10/30/12 12:08, Alex Keybl wrote: >>>> >>>> We have explored various >>>> techniques to lower the overhead of a compartment, but unfortunately >>>> those >>>> fixes that would help at all are either too risky for or cannot be >>>> completed in time for Gecko 18. We have decided instead to consolidate >>>> all >>>> JSMs and JS components into a single compartment in B2G. >>> >>> >>> >>> In case people missed this part specifically, I just want to point out >>> that the change in bug 798491 are targeted for FF18 (Aurora). See comment 75 >>> for philikon's early risk evaluation. From our read of the bug, although >>> this represents major code change, we do not expect major desktop/Android >>> regressions, especially with a day or two of bake time on m-c to start. >>> >>> -Alex >> >> >> This plan really worries me. I agree that it is unlikely we'll see >> desktop/android regressions. I'm more worried that we'll just break the >> platform b2g runs on in subtle ways that we might not notice before >> shipping. It's pretty concerning to have a fundamental change to how >> components and modules are loaded on a new platform where to my knowledge we >> don't yet have good automated testing (please please someone prove me wrong >> on this). >> >> >> _______________________________________________ >> 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 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
