Every time I'm starting a new project, I take a look on the web, talk to friends and check on magazines what are the latest hot technologies I can apply to the project. Of course, I can't apply everything, it's a risk, so I pick up what I can depending on several factors, being determinant the deadlines.
And that's how I started to move on with version control. My first experience was with a Borland tool, I can't remember the name, but I remember that it came bundled with a Delphi 4 package, if I'm not missing the correct version. Anyway, there was no flexibility at all, and the tool was full of bugs. But we get used to them, and I used it for a while.
With java projects, initially I started to use CVS, or Concurrent Version System. In 2001 I participated in one specific project that required a trustful version control, since we had three distinct teams, located in two different cities, working together in the same project. And CVS responded as expected. We had some minor issues on renaming files, and when we worked on the same file, but the benefits on using CVS on that project were unquestionable.
I don't remember well when I tried the Apache SVN, but when I tested the branching, I left CVS behind. Never used again. The tools are much better, wide supported - the Eclipse plugin, in example, make it easy to use.
I stayed working with SVN since 2011, when I tried out Git. I remember checking out the speed of the commits, the ability to easily and quickly have concurrent local branches, commit some of them, and push it to the central repository. And also the merging impressed me. Much better than SVN for what I was doing! I know, it's not only that, but comparing how fast and easy it was, comparing to SVN... I moved on to Git.
And when we talk to Git, we can't forget to mention GitHub. I just left my first repository there. The idea of having a Git repository hosting server available for everyone is awesome!
When considering a version control solution for a new project, for sure, there are lots of good options. And the decision on which one to pick must be tied to the technology (like Team Foundation for a .Net project), the project requirements and the preferences (architect and developers). Also, if it's new to you and your team, spend some time testing. Make sure you're selecting a solution easy to work with.
