We've started doing Jakarta projects over to SVN, but we've been doing the easy stuff first to get into the hang of it.
I think a pretty fair target for Jakarta is to be fully in SVN by the end of next year; unless there are reasons to move quicker. One thing to work out with Commons is whether we should move the whole lot in one go; should do commons-proper then sandbox later; or do individual components one at a time as it fits their release cycles etc. Hen On Thu, 25 Nov 2004 14:07:39 -0500, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > > > 6) should I just delete the /jakarta-commons-sandbox/email directory, or > > > leave the folder and a note pointing to the promotion? What about the > > > website as well? I think for [configuration] we just deleted both. > > > The ideal scenario would be to use "cvs delete" on all the sandbox > > files, so that the original history is maintained there, but nobody > > who checks out the sandbox (with "-dP" at least) will be bothered by > > the files. > > The IDEAL situation would be to convert Jakarta Commons to SVN. Can we > PLEASE consider doing so? > > A lot of projects, including the HTTP Server project, have been migrating, > as can be seen from http://svn.apache.org/viewcvs. Jakarta and XML are > definitely the laggards now. > > --- 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]
