Le 08/11/2013 17:32, Thomas Zimmermann a écrit : > Hi > > On 08.11.2013 17:20, Julien Wajsberg wrote: >> I'd say, if b2g-inbound is red, it will be closed and backed out, and >> you shouldn't be able to land your gaia patch. So it looks ok. >> Once b2g-inbound is green and contains your patch, so will travis. >> >> Feels good to me :) >> > Closing trees and backing out patches does not happen immediately. You > can still land patches on top of a broken b2g-inbound until it's closed. > So we'd have to stop Travis whenever b2g-inbound becomes red just to > guarantee that b2g-inbound has the necessary patch.
My proposal was: we take the latest inbound that does not have test failures and therefore we can be confident the build is fine. That said, I now remember that intermittent failures is a reality, so this may not be that easy. > > Simply merging both repos into one would fix all this easily, because > it'd be obvious which patches belong together. > I still feel this would be bad. I mean, not necessarily bad for us core contributors (although I'm not sure of that either), but it will be bad for occasional contributors. This works for Android because, well, they don't have much external contributions, and tend to discourage this. We want to do the opposite, and I think that having everything in one repo won't help this. -- Julien
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
