I work at a rather sizable government facility with multiple departments,
some of which do development work. I got an email this week regarding
something new: There is an initiative to standardize on a "CM" tool
(Configuration Management). They are considering Visual Source Safe. I wrote
a few email messages, and made a couple of phone calls, and deduced that the
reason that they are considering VSS is because:
1) Most people here have used it or are using it.
2) It integrates with Visual Studio (which makes the Windows developers
happy).
3) Most departments already have licenses for it.
In other words, they are choosing it kind of by default. They have not
considered features in their choice. The people I spoke with said that they
would be open to consider alternatives to VSS. Now would be the time to
clear my throat and say something, if something will ever be said here.
I, for one, have never seen VSS used, but one guy on my team here says he's
used it, and hated it. Has anyone writtem a document doing a feature
comparison? How about a usability comparison? Is there a URL that compares
Subversion with VSS, showing relative strengths and weaknesses? I'd like to
have a document to pass around to a few key people (some of whom are big
open-source fans) but I'm not qualified to write it myself, having never
used VSS.
Thanks in advance!
--- Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 7 18:27:06 2003