[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Communication of LOCKS and CHANGES

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-11-26 17:36:25 CET


> -----Original Message-----
> From: Wayne [mailto:wayne@zk.com]
> Sent: Wednesday, November 21, 2007 3:45 PM
> To: users@subversion.tigris.org
> Cc: users@subversion.tigris.org
> Subject: Re: Communication of LOCKS and CHANGES
> Moore, Tom wrote:
> >> If you cache the information people will see it and
> believe it. And
> >> because it's right most of the time this will re-enforce the idea
> >> that
> >>
> >
> >
> >> the information is correct. Users will come to rely on the
> >> information
> >>
> >
> >
> >> to make important decisions. Sometimes the results will be
> >>
> > catastrophic.
> >
> >> It has been my experience that the likelihood of such a
> problem will
> >> occur is inversely related to the amount of time available to do a
> >> project and directly proportional to the importance of finishing on
> >>
> > time.
> >
> > You know there is a basic assumptions here that a number of
> people are
> > making that is driving a lot of the negativity, and driving
> some of us
> > nuts.
> >
> > "The cached information is a binary solution set. Locked
> or Unlocked.
> > People will view the cache and assume or believe..."
> >

======== snip =========
> I am not sure why your are focusing on files with the locked
> status in the cache (false positives.) They are not the
> problem at all. The developer will see that they were locked
> at one time and figure out whether they are still locked and
> do the right thing.
> It is the false negatives that will cause the problems. The
> developer will look at his working copy see no lock and start
> modifying the file.
> Only later he'll find out it's locked. That's when you have a problem.

And, this is how things are right now. This problem exists and is
unaffected by presenting more information to the user. However, the
other problems are deminished. Also, this problem becomes less likely
if the developer has a habit of updating before beginning new work, say
when she comes into the office in the morning, or after lunch.

This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 26 17:37:03 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.