On Tue, 5 Nov 2002 13:31, Greg Stein wrote: > Ooh... now I really get to do some Subversion evangelism :-)
;) > Okay... so here is my suggestion. Let's use Subversion's "externals" > concept. This is very similar to CVS modules in that it aggregates multiple > locations into a logical view. Unlike CVS, however, users can maintain > these views (rather than asking a CVS admin to edit CVSROOT/modules), and > the externals respond properly at "update" rather than just "checkout" > time. nice. One thing you may not realize is that adopting Subversion may mean a little hand holding until people get used to it or until there is something like http://www.red-bean.com/cvsbook/ out for it ;) > > * All of the non-Apache people wanted per-component announce lists. > > Too bad for them :-) (IMO) Apache Commons is the release and announcement > vehicle, so all the info comes directly from A-C rather than the > components. The ASF needs to be the releaser-of-code to ensure that it > retains full liability for future problems; for the ASF to release the > code, that means the formal release is an activity sanctioned/monitored by > the PMC. True. But after that sanctioning I think it would be nice to have the announcement distributed on a per-component basis (aswell as through other channels). -- Cheers, Peter Donald -------------------------------------------------- The fact that nobody understands you doesn't mean you're an artist. --------------------------------------------------
