This question is related to evilrix'es "What's your favorite Version Control System (VCS), and why?" http:Q_27321575.html
Assuming you have chosen the CVS, CVSNT, SVN, VSS, Mercurial, Git or whatever, you probably had or none or a different VCS before. And you probably have colleagues who want or are forced to use the version control system. Can you summarize your experience with the transition?
I am going to summarize my own experience. I lead one of the software project in our company.
Once upon a time, I have started to use the VCS (namely CVSNT) and it solved my pain in the time. Being grown on punched cards and later on command line, I have always prefered to know what I am doing -- I am using the command line plus some trivial batch files (the most repeated cvs commands), plus some Python script later (to zip differences from some tag...).
It happened that colleague of mine complained about having problems with maintaining all the sources updated by more people. I had suggested to use the CVSNT, and he agreed. However, he and his co-workers were not grown on a command line and they decided to use the Tortoise client tool (http://www.tortoisecvs.org/
). Then, it was a bit difficult for me to explain what should be done in some situations. The problem is that some users do not understand what is behind the system. They tend to think in terms "some magick thing is done", and they complain if the magick is not the one they expect.
Can you summarize what you see as a problem with your first or another version control system from that point of view? What was your expectation, what was the reality, how did you cope with that? How to introduce the vcs to the others? How to convince them, and/or how to force them to us it?
Thanks for your time and experience,