Jason van Zyl wrote: > > Not quite sure what you mean here? I was imagining the tool taking defaults > set out by project release managers and that only experienced developers > would override the defaults.
I prefer what I see with cactus. Cactus has a set of regression tests. If they pass, there is a daily minor release. If not, then the developers list is notified of the failure, and the process repeats the next day. What is posted in that daily minor release is guaranteed to have passes all the tests and to be internally self consistent. Periodically, there is major releases. These are more intended for end users. Again, they take the form of complete bundles that are guaranteed to be internally self consistent. >> As an example of this, take a look at >> http://gump.covalent.net/jars/latest/alljars.zip . At the moment, it may >> be a bit big for some people to swallow, but hopefully in the future some >> people will design profiles which are tailored to specific audiences. > > Again, I'm not quite sure what you're driving at. One download. All the parts contained therein are guaranteed to be self consistent. >> As you can plainly see, I have a long term vision that I am executing on. > >I'm with you there, though my bent in particular are metrics and the >navigation of project in general. I'm also interested in building but I >think that is only one (granted very important) aspect of a project. http://marc.theaimsgroup.com/?l=xml-apache-general&m=100857962129228&w=2 http://www.apache.org/~stefano/forrest/ - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
