Jozef Kosoru wrote:
I would like to know
whether it is worth to invest my free time for such a tool.
CVS is rather an old system and I have no idea how widely is
used in development teams. So my question is easy: Do you use
CVS in your development?
These are the following systems I've used:
CVS : the most common open source SC system used by nearly all open
source projects.
- It has issues but some very nice features - the most interesting is
the robustness - i.e. simple respository - meaning that if (inevitably)
the repository has a failure (disk corruption or even a CVS failure
mode) it is recoverable with some manual effort.
Perforce : powerful but learning curve.
Bitkeeper : used by linux kernel maintainers. It's well thought out.
Subversion : Touted as a CVS replacement - however robustness is my
biggest concern. So far so good. Already alot of tools that work for
CVS (like WinCVS and Tortoise are available for Subversion.
ClearCase : When I used this on Irix systems it was very cool but
unstable and slow. It was a "file system" and the filesystem "view"
could be changed. For the longest time I thought that was an advantage
but I soon realized that the ability to run remotely/disconnected was
the much more important.
SourceSafe : Next to useless for teamwork
http://www.highprogrammer.com/alan/w...ourcesafe.html
I have also used in house SCM's which I can say without fear are
inferior to CVS.
Here is a huge list of SCM systems:
http://www.linuxmafia.com/~rick/linux-info/scm.html
So to answer your question. I think you want to abstract away the SC
tool and make it pluggable - start with a CVS plug-in.