Andrew Close wrote:
> 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
> 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. ;)
> To unsubscribe, e-mail: email@example.com
> For additional commands, e-mail: firstname.lastname@example.org
We're implementing SVN/TSVN at our (largish) shop of approximately 45
developers. We've decided to go with Subversion for the following
1) We have risks associated with the current SCM process and toolset and
SVN is something that we can implement easily compared to other tools.
2) SVN has a proven track record and is widely accepted.
3) We have many different development environments from Oracle/PLSQL to
Java, to .Net and mostly the Progress 4GL. SVN can work very easily in
all those environments.
4) SVN is developer friendly. It allows for a lot of freedom while
providing enough control to make management happy. There's many ways to
use the tool to accomplish your desired workflow.
5) Our company is extremely customer-driven. One of our distinctives is
the ability to respond *very* quickly to customer requests. While
ClearCase is an excellent tool, we feel that the overhead of using it
might make our environment less responsive to change requests. We opted
for more developer freedom at the expense of rigid control in order to
stay fast and responsive as a team. YMMV.
ClearCase is IMNSHO the SAP of version control systems. It's huge,
powerful, has high network and machine resource requirements, and
requires possibly more than one adminstrator. SVN is at the other end
of the spectrum. Lightweight in the svnserve flavor, it's easy to
administer, easy to learn and barely sips at network resources. SVN is
more agile and light on it's feet. :)
Perforce is about in the middle of the spectrum between SVN and CC.
It's interesting to note that SVN/TSVN are closing in on the feature set
of Perforce. We won't have the pending changelists feature of Perforce,
but with the addition of merge tracking to SVN, there will be no reason
for us to ever consider Perforce or CC.
Just my 2 cents
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed May 9 16:46:05 2007