> If they do not update before working on the file they will
> also have lost work. If the workers are so untrustyworthy to
> follow rules then it would seem that an extraordinary effort
> will be needed to enforce this.
It's easy to do an update on the top level tree, before going into the
tree and I have instructed all the users to do this.
This step is sufficient, I believe, but it does not give the user any
information about file locks. So, in the current model, the users are
also required to check for modifications after doing the update. It
seems like this is extra work that shouldn't be necessary. Automation
is the strong point for computers, and the weak point for humans.
Also, when you check for modifications, it will merely present a list of
files that have locks, and if you have dozens of people working on
files, there will probably be dozens of files that have locks, and from
the perspective of the engineer, they have to ask themselves, "Will I
need to work on any of the files in this list." And simply remember
which files have locks by other people.
I think it would be a lot easier if only a person could see that a file
was locked, before they try to edit it.
> There is supposed to be a mechanism in subversion
> (svn:needs-lock) which will help enforce this... Have you used that?
Yes, I've looked at needs-lock. The concept is good, but in practice,
it's no fun to use. If everything worked smoothly (which it doesn't)
then it would require users to always get locks, even if they know
nobody else will work on a file. And everytime they create a new file,
they have to apply the needs-lock on it, and simply this creates
additional work for the users. Instead of being able to simply notice
that someone else has already got a file locked.
> I noticed that Tortoise adds a SVN Lock owner attribute to
> the explorer window. But in my lock tests I do not see this
> value getting populated even after an update, even after
> doing a manual check for modifications/check repository which
> shows the lock. How can I get this column to show the current
> lock owner?
I've noticed this too. If anyone knows anything about this one, I'd
like to know too.
An additional point -- If you simply go to "Properties" of a file, and
look under the "Subversion" tab, the lock owner never gets populated.
Maybe a bug.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Apr 25 21:13:17 2006