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
VSS- walk away, don't make eye contact :-)
Pros: umm, it does manage versions, close integration with MS VisualStudio
Cons: windows-only administration and probably access too, not
intuitive to use, opaque binary files having no discernable relation
to the actual artifacts themselves, not cheap
[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
CVS seems to be the
On 9/16/05, [EMAIL PROTECTED]
[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?
Perforce:
Seriously consider SVN, too if possible. From what I am hearing, all
Apache projects will be on SVN within the next year.
CVS is getting a bit long in the tooth but works well for everything
i have ever needed.
VSS is IMO a waste of digital storage that could have been better used
for something
[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.
VSS: *hurl* I can' recall a time where I've ever thought Whew, thank
goodness I'm using VSS and horror stories abound.
Perforce:
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
[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?
Don't touch Perforce with a barge pole it
Subject: Re: [OT] SCM stories (war? horror?)
VSS- walk away, don't make eye contact :-)
Pros: umm, it does manage versions, close integration with MS VisualStudio
Cons: windows-only administration and probably access too, not
intuitive to use, opaque binary files having no discernable relation
9 matches
Mail list logo
