On Tue, 15 Mar 2005 08:30:22 -0500, Sean Schofield <[EMAIL PROTECTED]> wrote: > I do agree with Martin that if we do this, we should really use > subversion.
Nonbinding +1 :-) > I know that we are not ready for subversion yet so maybe > that means we should hold off. > > I think there might be some advantages to the subproject idea but IMO > we have a lot of other basic stuff to get under control before we > contemplate any major changes. We still have a lot of other important > items on the table: documentation, mailing list change, additional > material for the website, nightly builds, upcoming release, etc. > > Keep in mind that Struts has a *much* bigger user base and a lot more > committers. Also they switched to Subversion for just this reason. > The Struts team has people committing 24/7 and they are probably > better equipped to handle a bunch of subprojects than we are right > now. > >From a day to day perspective, developers dealing with subprojects is no different than one happens now ... it's only when you want to roll up your sleeves and release something that it matters. But SVN is definitely the way to go if you want to reorganize the repository -- once you've started using "svn copy" and "svn move" (instead of mass "cvs delete" and "cvs add", which -- oh by the way -- loses the log history), you'll never look back. > My .02 > > sean Craig
