It’s just data
Agreed. [Maven | Centipede] for daily development, Gump for advanced warning.
One place I differ, however, is that I think that there is an easier solution than requiring developers to perform extra steps. All it takes is for people to take notifications of gump failures seriously and follow this advice.
Meanwhile, a big thanks for all of your help this week!
I think paying attention to GUMP keeps your build running smoothly against HEAD. However I still believe people should be more deliberate in their changes to the external interface. You can commit whatever you want to CVS, but I think you should make it obvious when you potentially broken compatiblity. GUMP can't catch all the problems that occur when a product changes, only what happens to be captured through unit tests. And I'm told that most programming errors occur at the interces between systems; that's why dependency tracking is so important.
Posted by Morgan atMorgan, you rock. Watch tonight's build and cross your fingers.
Posted by Sam Ruby atw00t
Posted by Morgan atOh wait, two dependencies failed to build. Well there's nothing immediate I can do about xml-fop, but I can go ahead and exile the ojb tag to another build. I'll do that now.
Posted by Morgan at