Re: CVS - setup reserved checkout

[David Masterson]

>>>>> Kaz Kylheku writes:

[...with respect to CVS...]

> Tell the manager to shed his or her superstitions, and work with the
> facts. The facts are:

> - Concurrent development works just fine.
> - Your team already likes it.
> - Strict locking does not prevent concurrency, it only reduces
>   it to a coarse granularity: coarse enough to interfere with
>   productivity, but not coarse enough to eradicate conflicts.
>   To eliminate conflicts, you have to lock the entire repository
>   so that only one developer at a time can do anything on the
>   software base as a whole.

> Since it is already working for you, you can invite the manager to
> witness, or participate in, some of your day to day version control
> activities.

The point is that the development policy should fit the configuration
management tool and the CM tool should fit the development policy.  If
the two don't get along, then the development environment is broken
(well, if not broken, certainly very hampered).  Brad Appleton's
papers on SCM patterns provide a good start at understanding how to
setup your policies and patterns:

        http://www.enteract.com/~bradapp/acme

-- 
David Masterson                dmaster AT synopsys DOT com
Sr. R&D Engineer               Synopsys, Inc.
Software Engineering           Sunnyvale, CA