Re: CVS - setup reserved checkout

[yap_noel]

>> Conflicts are extremely easy to produce and may not be easily resolved.
>
>The issue it seems you are having is that on a regular basis, two or more
>developers making large abouts of unrelated changes to same sections of
code.
>This problem cannot be solved by locking checkouts, or by any change
control
>tool.

Yes, in fact, in environments I've been in that avoided unreserved
checkouts at all costs, one developer started modifying a copy of the file
that was locked.  After the file was checked in, the developer checked the
file out, copied his version over it, and checked it in thereby wiping out
the other developer's changes.

The moral: Developers will seek concurrent development even though they
don't know how to do it properly.  It's much better if the tool and
procedures allow concurrent development.

Noel



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.