* Working on my laptop on the train the other morning I cd'd into an old source tree that was checked out from subversion a few years ago. I was brought up short by subversion not being able to tell me the revision history, what with it being unable to connect to the repository server.
* I also recently needed to checkout an old version of Rails using a rake task I wrote a few years ago, and discovered that Rails subversion repository has gone away. The revision history has moved across to github, but scripts will have broken and existing subversion checkouts will have lost their history.
If you go with a centralised VCS, you will get burned at some point by being unable to connect to a repository, either temporarily or permanently.
might be relevant: http://stackoverflow.com/questions/3320001/source-control-sy...
Thanks.
I don't have your problems with source control. The Linux project probably has somewhere in the neighborhood of that, and since git was built for Linux, I would not bet on it being architecturally impossible for git to scale that far. The more serious problem I see coming down the pipe is getting your entire team to adopt DVCS workflows. For example, you'll probably end up moving away from having one person whose sole job is making sure merges don't explode into firey balls of death. Distribution of responsibility for making merges happen well could, conceivably, cause problems for a segment of your developers.
Once you've refactored your codebase you'll be in a position to make better choices about a source control system.
[1] http://www.objectmentor.com/resources/articles/granularity.p...
SVN is wonderful software. It is a quantum leap above "no version control" and tortoiseSVN is probably the best GUI available for getting value out of version control prior to understanding it. That said, magical goodness awaits you if you use DVCS instead.