[Top][All Lists]

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

Re: Use of CVS on large scales

From: Greg A. Woods
Subject: Re: Use of CVS on large scales
Date: Tue, 12 Jun 2001 15:09:31 -0400 (EDT)

[ On Monday, June 11, 2001 at 20:19:48 (-0500), Bob Bowen wrote: ]
> Subject: Re: Use of CVS on large scales
> 2) Building a unified development process on top of CVS; e.g. enforcing
> conventions and policies which are inevitable as the size of the project
> grows. The hooks again are too primitive and each script shouldn't have
> to be called for every directory involved. The interfaces to the hooks
> are all different and not enough information is available, e.g. what
> branch is this on? I'm continually frustrated by the holes in the
> support for the checkin templates in the client/server methods as well
> as the lack of interactivity with the callout scripts.

Yes, CVS is not well suited for projects/teams which require automation
to assist with enforcement of policies and conventions that are not
directly related to versioning issues.

However I'd just like to point out that not all large projects require
such stuff.  Many relatively large projects seem to work quite well
without such "interference".  No doubt it depends somewhat on the
experience levels of the team members.

                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

reply via email to

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