Just to note, we've been red on smoke tests for last several weeks since the 5/21. My experience is that it will only get worse if people don't own up to the quality of their own landings. Landing stuff that works is great. Landing stuff that breaks all other stuff... not so much. ;)
Doug was asking this for stability into the work week. The alternative is to lock a good build and patch that build with fixes we need for our first launch (first impressions), similar to what we do for MWC. In general though, asking QA to help out with seriously risky patches, may also help (so long as they have the bandwidth to help test). On Wed, Jun 10, 2015 at 11:17 AM, Fabrice Desré <fabr...@mozilla.com> wrote: > On 06/10/2015 11:11 AM, Benjamin Francis wrote: > > > We should definitely work hard to get B2G master into such a stable > > state. Asking people to stop landing patches is one way to do that, > > although arguably not the most productive, especially since we are > > currently refactoring the whole of Gaia! :) > > I agree. keep landing. Ironically, the latest serious breakages in > nightly builds have been platform gfx changes, not gaia ones... > > Fabrice > -- > Fabrice Desré > b2g team > Mozilla Corporation > _______________________________________________ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g >
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
