I can't speak about switchers using the SourceForge site, since it's
only been recently they've offered subversion. Here are various projects
I know about and their histories:
Python - switched to svn from cvs some time ago, (I think) dropping
SourceForge hosting of their repository in the process. I'm not close to
the development process, but as an occasional source-tree grabber and
c.l.py reader, I didn't hear of any issues.
numpy/scipy - switched to svn from cvs several months ago (September?).
there were some initial problems converting the history with the cvs2svn
script, but I think they were worked out, perhaps with the help of the
subversion developers. as far as I know, there have been no issues with
svn itself once the history was converted.
ipython - I think they are very pleased with subversion. They're
maintaining one branch and actively developing next generation ipython
(what will hopefully become v1) in another.
Personally, the biggest win for me with subversion is that I can do "svn
diff" and it's nearly instant -- no network access is needed. It would
also be nice to finally be rid of the asynchronous developer vs.
anonymous access that sourceforge's cvs solution entails.
Eric Firing wrote:
Andrew Straw wrote:
It looks like SourceForge has (finally) adopted site-wide subversion
What do people feel about migrating from CVS to svn? SourceForge
apparently even has an automated tool to do so. They also state that
there will be no more delays between developer access and anonymous
Personally I'm +1 on switching -- matplotlib is the only project I keep
up with that still uses CVS.
I don't mind switching; I installed svn on my main machine some time
ago so I could grab numpy, so I presume that using it for mpl will not
be difficult. Do you know what the experience has been in other
projects that have switched? Everything smooth? Or a week or two of