If I might add one more, the process of promoting components from sandbox to proper will be easier with svn move or copy.
One thing I'd like to see going forward is that a component is moved out of the sandbox upon promotion. I know it is just an empty directory, but digester and codec still appear here: http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/. Also, I don't want to ever see "waiting for bayard's lock in /blah/blah" (not singling Henri out) I would like to forget ever knowing about cvs lock files. (http://www.network-theory.co.uk/docs/cvsmanual/cvs_88.html) Tim > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Friday, November 26, 2004 11:05 PM > To: Jakarta Commons Developers List > Subject: RE: Migrate to SVN? > > > Can you comment on the admin-side advantages of svn ? > > Elimination of the need for shell accounts, and the ability to shift load > from the core infrastructure team to the PMCs. Trivial project movement. > And since we sometimes have to ... <<cough>> ... help recover from people > playing around with ",v" files, I would not discount the issue of > refactoring not creating any issues for infrastructure. > > Those are a few off-hand. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
