[Top][All Lists]

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

RE: Locking support

From: Noel L Yap
Subject: RE: Locking support
Date: Wed, 22 Aug 2001 10:11:47 -0400

>[ On Monday, August 20, 2001 at 20:39:22 (-0400), Noel L Yap wrote: ]
>> Subject: RE: Locking support
>> I originally created these patches for users who were also used to locks
>> and RCS), but by the time I finished the patches, they were so used to the
>> concurrency in CVS that they never used them.
>Ah, now that tells a tale I wasn't fully aware of before!  And it's a
>tale that fills volumes too!  ;-)

Here's more of the tale:  The users were forced (due to various reasons none of
which were concurrency related) to stop using PVCS.  The choices were ClearCase
or something less expensive.  Since the group already had an extremely good
process and they were small, I suggested using CVS and explained concurrent
development.  They were still wary (and hence the request for the patches).

If it weren't for the fact that they had to abandon PVCS, they would not have
adopted concurrent development.

>>  I still think a good process
>> would include use of the patches to support more confidence in concurrent
>> development.
>I suspect a bit of up-front education is far far more beneficial in all
>cases.  Such sleight of hand can very (too) easily backfire.

There's no better education than experience.  These patches give developers a
chance to be eased into concurrent development.  The only backfire I can think
of is if a user didn't adhere to team practices and procedures.  If the team
never stops using the patches, so what?  Concurrent development can still
happen, but it's just a little more controlled.


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]