I finally caught up...I can now say something not too out of context... +1 SVN, if it can be accomplished.
I'm very interested in seeing a good alternative arise, and this project could help SVN come into it's own. jim -----Original Message----- From: Noel J. Bergman [mailto:[EMAIL PROTECTED] Sent: Wed 8/13/2003 5:00 PM To: [EMAIL PROTECTED] Cc: Subject: RE: SVN? (was: geronimo-dev Digest 12 Aug 2003 21:59:40 -0000 Issue 39) Jeremy Boynes asked: > Greg Stein wrote: > > "sorry. no more CVS. it is a bitch to maintain. switch to SVN." > Should be be planning for this, and perhaps move now whilst we are small? Another thing to consider, but again Greg is the expert, is that this is a huge umbrella with a lot of sub-projects. Right now there is one module. Moving between modules in CVS isn't a whole lot of fun, even if doable. SVN has a different model, which would make partitioning acces rights, and moving things around a WHOLE LOT easier. This project seems almost ideal to give Subversion a whirl, considering how the project structure interacts with key differences between CVS and Subversion. > How hard would it be to move the javax.* stuff to a separate module > and put it in SVN? I believe that it just takes a request to infrastructure to set things up, and then some quick lessons for everyone. Subversion is already running, and has a couple of sub-trees. --- Noel
<<winmail.dat>>
