Andrea Aime wrote: > We can try a few options, before calling the trunk on trunk experiment > failed and go back to the old way of doing things. > One would be to build a sort of "hall of shame" with a score that > goes up for each developer that breaks the build. > Another is stronger, but I guess it would work: if some commit breaks > the build, and does not get fixed within a few hours, revert it > without mercy. I like the second option the best .. but then we get in a situation like last week - where Cory had days worth of work on his box and I could not help him. Suppose this is the case for making a short lived branch. > Unfortunately this does not work for geoapi changes... See above ... > All in all, I'd say just revert changes that break the build, we have > a versioning system, people that break the build for long times will > go thru the pain of resurrecting their changes and fixing them. > If the changes people are doing are so big that they make the build > consistently break, then I'd say a branch is needed. Cheers, Jody
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
