"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > But to me, anything that hits 'next' that breaks Git this badly is > a regression. Why? Because I run my production repositories off > next, that's why. Of course I do this to exercise next more fully... > to prevent this sort of stuff from getting to master. ;-) I'm almost always on 'next'. I switch to run 'master' a few days before -rc0 and a few days after the final feature release I switch back to 'next'. The tip of 'next' may not be perfect, but it should not be so broken that it is beyond a quick repair to inconvenience users that rely on 'next' working. And it helps us catch problems before the topics hit 'master'. Because the tip of 'master' gets tagged only once every 6 weeks or so, its tip is not an official release at any other times, but we effectively have the usual pre-release QA continuously running on the stuff that hits 'master'. That's what 'next' is all about. And that's how we can keep our 'master' a lot more robust than the development branches of other open source projects. - 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
