Menu
The types of VCS are: Local Version Control System. Centralized Version Control System. Distributed Version Control System.
One important technical skill of increasing importance is using version control (also referred to as source control) systems. For those un-familiar version control systems give the user the ability to track changes to code, text, html, images and pretty much any other file you want.
Version control, also known as source control, is the practice of tracking and managing changes to software code. Version control systems are software tools that help software teams manage changes to source code over time.
The most important thing about version control is:
JUST START USING IT
Not using version control is a horrible idea. If you are not using version control, stop reading right now and start using it.
It is very easy to convert from
cvs<->svn<->git<->hg
It doesn't matter which one you choose. Just pick the easiest one for you to use and start recording the history of your code. You can always migrate to another (D)VCS later.
If you are looking for a easy to use GUI look at TortoiseSVN (Windows) and Versions (Mac) (Suggested by codingwithoutcomments)
Edit:
pix0r said:
Git has some nice features, but you won't be able to appreciate them unless you've already used something more standard like CVS or Subversion.
This. Using git is pointless if you don't know what version control can do for you.
Edit 2:
Just saw this link on reddit: Subversion Cheat Sheet. Good quick reference for the svn command line.
Use subversion, it's easy to setup, easy to use, and has plenty of tools. Any future revision system will have an import from SVN feature, so it isn't like you can't change down the road if your needs grow.
The Subversion Book is your best bet for learning the tool. There may be other quick-start tutorials out there, but the Book is the best single reference you'll find.
Git has some nice features, but you won't be able to appreciate them unless you've already used something more standard like CVS or Subversion. I'd definitely agree with the previous posters and start with Subversion.
If you are new to versioncontrol read this:
Source Control HOWTO
Go for SVN. If you have never used source control before, it won't matter to you one way or the other.
Also, there is not a large amount of learning involved in using a Source Control system. If you learn one, you can easily switch over to another at a later date.
SVN is a great tool, and it should take care of most of your needs. And since it's been around, it has a fair sharer of GUI tools (TortoiseSVN, for example).
Go for SVN.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With