On Mon, 2015-02-23 at 09:11 +0100, Dirk Bächle wrote: […] > > I have basically no objections, but instead of bloating up the testing > workflow even more, we should keep it at a sane level. It > should be allowed for a patch+test to turn one or several buildbots red. But > then, fixing this problem has highest priority. > Finally, we should make sure that all buildbots are green before pushing a > new release out. We didn't do this last time, and I think > we learned our lesson from that. ;)
Clearly this is much lighter weight. For me it only really works if you can back out of the changeset causing the red to go back to the previous green so you can move to a different pull request. Relatively straightforward with Git, seemingly quite painful with Mercurial. On the other hand I am not one of the gatekeepers… -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
