We have test coverage using emulators, and actual hardware (panda boards) is being set up. Reporting of the results and integration is very lacking, and until those pieces fall into place (e.g. try integration), the developer experience is going to suck a lot if we enforce the rule below (backout). We might want to try a "coordinate" instead of the automatic back out approach. If some change breaks B2G, we will try to negotiate with the patch author whether we can back it out and land it later or back it out and we help fix the B2G regression and then re-land etc. If you break B2G, the feedback is not immediate, and there is almost no fair and reasonable way for general m-c committers to predict and test for B2G regressions (the A team is working really hard on fixing this).
Andreas On Aug 1, 2012, at 9:30 PM, Boris Zbarsky wrote: > On 8/1/12 5:47 PM, Alex Keybl wrote: >> any desktop/mobile change that negatively impacts B2G builds in a >> significant way will be backed out (and vice versa). > > Do we have any sort of B2G test coverage? Ideally on try? > > -Boris > _______________________________________________ > 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
