Hi all,
our company is currently using an old version of VSS that really isn't
cutting it anymore. there's been talk for a couple years now to
replace VSS with something 'better'. several of the devs have pitched
SVN as the repo of choice. another division (newly purchased) is
already using SVN as their repository, but they have a very small
development shop and don't have near the commit rate or concurrent
development that we have. so it would be hard to use them as a model
example. the current project i'm working on has assumed that we would
be moving to SVN and since we needed a separate codebase to work on,
we've set up an SVN repo and have been successfully using it for a
couple months.
however, management is not quite convinced that SVN will fulfill our
needs. surprisingly there is quite a bit of support for ClearCase.
surprising since it has a price tag (a hefty price tag) and we don't
spend money on tools. one concern is that management will bring in
another expensive tool, do a crappy job of implementing/configuring
and then we'll be stuck with another sub-par system for the
foreseeable future since we paid for it (just like we're stuck with
Lotus Notes...). we are by no means an IBM shop, although it's
starting to look that way. :)
i've noticed several posts from users mentioning that they are
migrating from ClearCase to SVN. i'm curious as to why ClearCase
didn't cut it, or why SVN was a better alternative.
any thoughts or comments out there? anyone that moved from ClearCase
to SVN want to provide details as to why?
i know that we're going to have growing pains either way we go, so i'm
trying to be tool agnostic. but i'd prefer SVN. ;)
thanks,
andy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 9 15:01:57 2007