CVS or SVN or GIT?

Question

Possible Duplicate:
Revision Control System Recommendations

I'm in the middle of developing a web app. Which version control system (CVS/SVN/GIT) is recommended for managing a web app (it's environment is PHP/MySQL, Apache 2, Ubuntu 10.10 64-bit server)?

The web app is being developed on a dev/sandbox server for now, but will eventually be hosted on dedicated servers in the cloud when its private beta and then launch time.

Solution

Once upon a time, cvs almost completely replaced its competition and ruled the world of version control.

Then it was itself replaced by svn.

And now, svn has been replaced by git and github.

Git, Mercurial, and some proprietary systems are clearly the future of the VCS world.

Comments

[crashintoty]

Why do popular VCS's keep getting replaced relatively quickly?

[DigitalRoss]

It wasn't quick, the above process took 20 years. (CVS was first released in 1990.) Prior to CVS, revision control applied mainly to single files, though you could always say *.c. CVS introduced the idea of keeping track of projects and hierarchies. Then svn was basically a from-scratch rewrite of cvs. Git and Mercurial introduced the distributed and branch-aware VCS, both quite important features and worth tossing svn overboard for.

[nialloc]

Its really not that big a learning curve and there are many good examples out there.