So, three issues to know about re: svn: 0. Subclipse: If you use Subclipse - know tha the test repository uses a self-signed cert, you may need to hit the test repository with svn command-line and permanently accept the cert from my machine before you can use subclipse. I was able to checkout the current from Subclipse, so it does honor svn:externals.
1. Scheduling: If we go forward with this migration, we need to do this when everyone is available both so we can migrate successfully and so that we can have a proper 72 hour vote window. Doing this right before a holiday weekend is not the best idea, and I think we could use some more time to work out other issues like security and site publishing. The earliest I can see is a vote thread next week starting on the 27th or 28th, ending on the 30th. That leaves us with the posssibility of a five to six hour migration on new years' eve or day which might work out well. Was thinking this qualifies again as a "release" majority vote. (To address Torsten's question of waiting to commit until the SVN migration is done, I'd say don't wait for this. Adding another component doesn't create any more work, and I know I wouldn't want to slow down that work at all. Plus, this migration isn't a guaranteed thing.) 2. Binary Files: If you keep jars or other binaries in CVS and these binaries were not added with -kb, the cvs2svn process may have mangled you binaries. I don't think this is going to be a big problem, as most of the well used commons components do not version jars. Just be aware of this issue. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
