On Thu, 2004-02-26 at 21:02, Noel J. Bergman wrote: > > what's the checklist of TODOs to handle before dumping CVS? > > I'm in favor of migration, but have all of the client tools caught up? Have > the Eclipse plug-ins caught up with current Eclipse?
In the process of I believe. Greg should be more up to date on this. > FWIW, there are projects already using it, including: > > - James jSieve > - Depot > - Directory > - SpamAssassin > - Commons serf > - Xerces-p > > and every project that *has* switch raves about how great it is to be freed > of the problems of CVS. Other projects have talked about using it, but > despite the clear benefits, even to their specific needs, they are afraid of > the unknown. > > Huge improvements over CVS asside, I'd much rather use tools > > built on top of [Apache] software. The dogfood has arrived, > > time for chow. > > Is SVN being proposed for Incubation? I hadn't heard. SVN is built on top of APR, and also implements an Apache module (mod_dav_svn), so it already uses a lot of ASF code. That said, it would totally rock if SVN would come to the ASF. > Sounds like Fitz is working to get out the last kinks in cvs2svn.py, which > will be a good thing. > > Joshua Slive wrote: > > > And a few security issues. This was discussed a while back on > > infrastructure, but I don't remember all the details. > > Probably lack of HTTPS, which has since been corrected. Need to seperate HTTP and HTTPS, so that any commit attempt over an unencrypted connection fails without asking for auth. (this to protect passwords). > > we currently don't have a good way of managing the users and > > passwords for SVN/DAV access. > > Just run svnpasswd. Sander --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
