[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Visual Source Safe vs Subversion

From: Durden, Paul <Paul.Durden_at_avocent.com>
Date: 2006-11-07 15:37:17 CET

Eric,
We've used VSS back from the days when One-Tree software owned it before
Microsoft bought them out. When there were only a handful of developers
working on nearly independent projects, VSS was not a problem. However,
as we grew, and the size of our projects and teams grew, VSS was not
providing the solution we needed.

At the beginning of this year, we switched to Subversion.

I can only echo what others have stated about VSS database corruption,
merge on commit, etc.

One of the biggest advantages that Subversion has over VSS is the atomic
commit. When I commit (check in in VSS terms) a revision to the
repository, I know that ALL the files (not just the one I worked on) I
have in my local working copy are the same as what is in the repository.
You don't have to worry if another developer has checked in a different
file before you labeled the project.

I recently took over another project whose release build process
included the steps "Make sure all other developers are not making
changes to VSS" and "Let other developers know it is safe to make
changes in VSS." This is when I was truly glad we had switched to
Subversion.

Regards,
Paul

-----Original Message-----
From: Eric [mailto:spamsink@scoot.netis.com]
Sent: Monday, November 06, 2006 8:32 PM
To: users@subversion.tigris.org
Subject: Visual Source Safe vs Subversion

As a followup to "Problems with Limitations or Differences of
Subversion"
posted a short time ago...

One of my partners is pushing really, REALLY hard to convert us over to
Visual Source Safe and whatever that add-on is (I forget the name, now)
that supports accessing VSS repositories over the Internet.

I really don't want to do this even if I wanted to spend the $1500 or
thereabouts that it would cost us to do it, but I don't personally have
any experience with VSS and so I have no way to present an effective
argument.

This is the same partner who objects to the fact that you can't check
out an individual file or maintain individual version numbers for each
file (well, in truth, we all object to those, but I can live with them
better than he can, apparently).

Can some of you, especially those of you with experience with VSS, help
me to formulate some arguments against VSS and in favor of Subversion?

(Unfortunately, "VSS is evil" will have seriously limiited effectiveness
as
an argument.) :-)

Is there a "VSS vs Subversion vs ???" chart somewhere on the web that
compares and contrasts?

Thanks...

Eric

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 7 15:38:52 2006

This is an archived mail posted to the Subversion Users mailing list.