I would avoid VSS at all costs, its merge capabilities are less than stellar,
which makes it hard for two developers to change the same file.
Perforce works well. I like the changelist concept and it integrates
well with bug tools like TeamTrack, etc. Its biggest con is cost.
CVS while very popular and works well, has some issues but those issues
are well known and most projects know how to deal with them.
Currently, we're using SVN on my project. I love it. It has great
merge capabilities, the ability to atomically commit a set of files,
it will be pretty familiar to CVS users. The biggest annoyance
is how svn merge requires you to use URLs to the repository, but that's
pretty small.
If I were going to setup a new project I'd choose SVN. The price
is right and does a good job as an SCM tool.
Jesus Rodriguez
Senior Software Engineer
Red Hat Network
[EMAIL PROTECTED] wrote:
I'm preparing to make a case for switching to a differenct SCM tool
(source code management). The options are CVS, Perforce, and VSS.
Anybody have any cogent/credible stories or arguments for choosing one
over the other?
Thanks,
Dennis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
