[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Use of CVS on large scales

From: Donald Sharp
Subject: Re: Use of CVS on large scales
Date: Fri, 8 Jun 2001 09:30:01 -0400
User-agent: Mutt/1.2.4i

What's large scale for your team?

Go with Clearcase if you have 100+ developers.

CVS starts to break down( ie become unuseable ) with
over a 100 developers actively developing at a single time.
This is related to how cvs does file locking inside of 
the repository when people commit/update/checkout in the

Another good advantage of Clearcase is the multisite capabilities.
If you have developers working at a large number of remote 
sites, you might want to think seriously about this.  Especially
if they are connected at a relatively slow ethernet speeds
or their connection can be unreliable

One big disadvantage of clearcase over cvs is that their tends
to be a lot more administration needed( ie a dedicated support 
staff ) and their is a large yearly maintenance costs associated
with buying and getting support from rational.


On Fri, Jun 08, 2001 at 11:40:35AM +1000, Lucas Chan wrote:
> Guys,
> We are currently looking at implementing some kind of version control
> system.  We have been trialling CVS for the past few weeks, storing sources
> on a FreeBSD machine and using WinCVS on our development machines.  It seems
> that this is exactly what we're looking for.
> I have struck a problem that I'm hoping some of you can help me with.
> Our company hired a "testing expert" a week or so ago, and he is currently
> opposing our move to roll out WinCVS.
> This is because:
> a) He's never heard of it.
> b) He doubts that it is scalable enough for us.
> c) He believes that anything that's free _must_ have disadvantages (as
> opposed to Clearcase for example).
> This didn't go down too well with me (or my team) because:
> a) For someone who's supposed to be an expert on testing systems, it
> surprises me that he's never heard of CVS.
> b) When talking about scalability, I gave the example that FreeBSD itself is
> maintained using CVS.  i.e. implying that we're only building web sites, not
> whole operating systems.  This didn't seem to be good enough evidence for
> him.
> c) And of course, I'm a FreeBSD and Open Source fan.
> So, to cut to the chase... it would be great if some of you could show me
> where to find further information about CVS.
> I'm particularly interested in it's uses for (really)large scale projects,
> perhaps even some stats on the quantity of sources it can maintain, any
> advantages it has over commercial source control products, etc.  I've
> checked out the CVS web site but none of the information there was useful in
> this context.
> Something like... a case study of a large software company using CVS would
> be pefect (I imagine).
> Thanks for your time everyone.
> Regards,
> [ lucas ]
> [ the ego has landed ]
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]