Linked by Eugenia Loli on Fri 30th Jan 2004 20:06 UTC
General Development CVS, part of the glue that holds open source development together, shows its age. Many competitors have emerged recently, fixing misfeatures and adding new ideas. Shlomi Fish (of the version control comparison fame) explores several current open source version control systems that may be better than CVS for your needs. Email Shlomi on how to add info for your favorite VCS on his comparison page.
Permalink for comment
To read all comments associated with this story, please click here.
by Shlomi Fish on Sat 31st Jan 2004 10:10 UTC

> Can the subversion server run on Windows?

The Subversion server (either the Apache2 WebDAV-based module or the custom server) can run on Win32 very well, without a UNIX emulation layer.

> However, we really need to move on from a
> centralized model (1 repository per project)
> like CVS/Subversion to a distributed model (1
> repository per developer) like
> Arch/Darcs/monotone.
> Centralized repository is a hassle for
> open souce development model. Imagine Linux being
> developed by CVS/Subversion instead of Bitkeeper; I
> think Linux will still be in 2.2.x releases ;)

Actually, Linus Torvalds started using BitKeeper in the middle of the Linux 2.5.x or 2.4.x tree, so it would have been at least in 2.4.x right now. (;-)) Up to then he was using tarballs and patches. Other than that, the reason Linux requires a distributed model is because Linus Torvalds is a centralist, and wouldn't let anyone else besides himself apply patches to the central Linux repository. Other projects do allow more than one developer to have a commit access, and so they scale much better, without needing to use a distributed VCS. Take KDE or GNOME for an extreme example - they give CVS access to the most small-time contributor, and as such they advance by leaps and bounds.

See also Greg Hudson's analysis of it:

Other than that, you are right that having a distributed version control system offers some great advantages for all kinds of development. Subversion has some tools that can propagate changesets from repository to repository, but so far without conflict mergining. Better distributed operation for Subversion is planned to be added at a certain point in the future. (it will be faster if you contribute!<tm>).