Jeff King <peff@xxxxxxxx> writes: > On Thu, May 15, 2008 at 11:16:27AM +0100, Mike Ralphson wrote: > >> Which branch(es) would it be most useful on which to have this >> automated build/test cycle? > > I would think maint, master, and next, but with next as the least > important. I think Junio generally tests maint and master before > publishing, but presumably not always next (as there was test breakage > in next earlier today). I'd prefer heterogeneous automated test coverage to be on 'next' and 'master'. If the coverage extends to 'maint' that would be nicer, but on the other hand, I rarely apply anything remotely questionable directly on top of maint (instead, I'd fork from maint and merge the result first to next or master), so if we can catch master and next, we should be Ok. Before any push-out, I ran tests on all four integration branches on Debian (etch) and FC (I think it is FC5), both x86-64. But sometimes 'pu' is shipped with known breakage in tests. I can not push out with broken tests in 'maint', 'master' or 'next' (automated procedure on my end prevents me from doing so). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
