Edward Harvey wrote:
> 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.
They don't know if anybody works on a file but they do know
for certain that nobody works on another?
What about a policy "aquire a lock if you don't know if anybody
is working on that file"?
>> There is supposed to be a mechanism in subversion
>> (svn:needs-lock) which will help enforce this... Have you used that?
> 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.
With the autoprops feature you are able to implement the reserved
checkout model with subversion. Follow the link in chapter 5.25.1
"General Settings"/"Subversion configuration file" in the help.
> 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.
With svn:needs-lock it works the other way round: The icon tells
the user whether *(s)he* has a lock and can savely edit the
file. In this case (s)he can be certain, that noone else is
editing the file - you don't have that security with the features
you propose.
Subversion enables you to use the copy-modify-merge model or the
reserved checkout model. In my opinion you can always find
a good mixture of both for every project, spiced up with some
(if necessary: enfored) policies. You can't completely replace
team communication by a piece of software.
With your experience in version control, I'm positive that you'll
find solutions for your projects. Your co-workers are an important
part of it: Show them, how TortoiseSVN can help them with their
daily work and also show them what can go wrong and how to avoid
and solve problems. As soon as they understand the concept they
will gain confidence.
Kind regards
Sven
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Apr 25 22:42:47 2006