[Top][All Lists]

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

Re: CVS - setup reserved checkout

From: yap_noel
Subject: Re: CVS - setup reserved checkout
Date: Tue, 30 Oct 2001 19:35:47 -0500

A huge portion of Streamed Lines deals with branches.  Now, consider that
unreserved checkouts are sort of like (if not exactly) virtual branches...

IOW, if the manager is _really_ against concurrent development, then he/she
should be against any version control tool that allows branches as well.
OTOH, he/she may just want more control over the checkouts, in which case
you may be able to sell him on the "reserved checkouts" patches (really
more like advisory locks) available for CVS.


>>>>> 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:

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

This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.

reply via email to

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