Edward Harvey wrote:
>> You forgot: you have to force all users to update their
>> working copies or they won't notice that the svn:needs-lock
>> property is set on this file. And how do you want to do this?
>
> Everybody can accept the fact that their working copy is only as current
> as their most recent update.
And what exactly is the benefit from setting svn:needs-lock in your procedure?
Beside from the fact that svn:needs-lock makes it rather confusing to the user.
Normally it tells them to obtain a lock before starting work, but they can't do
this because it is locked. So you want to abuse this property for showing the
status "is-locked".
> If they don't update, they don't see someone else's lock. That's
> acceptable.
Okay, so they could simply do "Check for modifications" to see existing locks
before starting work. That's acceptable.
> Every user should do an update before they begin working, and my users
> have accepted this procedure.
Tell them to use "Check for modifications" to see the locks or install a
post-lock hook to publish the information in any other way, e.g. via email.
And maybe you should tell them about merging changes... I can't think of a case
where two developers make massive changes on a file at the same time. Do you use
some sort of issue tracker or task management? It should be easily to assign
developers to different tasks and they should talk to other developers, who are
assigned to the same task, about what they are doing.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Apr 29 00:45:18 2006