Source code control systems

See, at work I used to use Visual Sourcesafe, because we’re a Microsoft shop. At home, well, nothing. I had to use CVS to get other people’s project code, but I never really got on with it. Then I discovered Subversion. It seems pretty cool. I use it at home, and we use it at work, along with TortoiseSVN, the Windows Explorer extension that makes it easy to manage your svn working copies.
So, the choice was between CVS and SVN at home, and VSS and SVN at work: pretty easy choice.
Then came loads of other source code control systems. Now which should I be using? Arch seems sort of interesting, in a BitKeeper-ish sort of way; BK must be pretty good, because they’re using it to manage the Linux kernel, and so arch should be reasonable if it works on the same principles. Ned is talking about darcs, which operates without a central server, which seems pretty clever (although what do you do if the bloke with the one working copy isn’t onlne? Sounds a bit like it might have the BitTorrent problem, where there’s got to be at least one person with a full dataset online at all times.)
Which do you use? Do you stick with the old standbys like CVS or SVN, or are you using some of these “next-generation” SCC systems? Why, or why not? Are you doing anything interesting with them other than source control, like, say, Roberto’s weblog backend, or something even cooler?

3 Responses to “Source code control systems”

  1. Used VSS, switched to CVS, played with SourceGear Vault and Subversion, and have now settled on Subversion (including migrating my CVS repository).

    TortoiseSVN is a fantastic GUI (why isn’t there a decent GNOME one?).

    If you want interesting Subversion usage, try Trac which is a combined Wiki/Ticket System/Repository Browser which allows linking between all three.

    There’s also SubWiki which is a Wiki that uses Subversion for its storage.

    Not looked at Arch, but the idea of darcs scares me – I want a central server I can backup!

    Schwuk
  2. I have been using CVS at work and for OSS projects, but began looking alternatives. I was impressed with Arch and tried it out. I eventually got the feeling that something even better might be out there, so I kept looking. Now I’m using darcs and am rather happy with it. Note that you can still use a central server if you want to.

    Mark Stosberg
  3. This is useful, but hard to read… Version Control Systems Comparsion

    pascal

Leave a Reply

OpenID is a decentralised authentication system. If you use LiveJournal or Vox you already have an OpenID; just use the URL of your homepage there. See also how to get yourself an OpenID.