Re: subversion and locking

Ben Collins-Sussman said:
>
> On May 11, 2005, at 10:31 AM, Simon Whittaker wrote:
>>
>> If subversion 1.2 can emulate VSS in this capacity then I will use
>> this otherwise I will be using VSS :(
>>
>
> Well, you'll be missing out on half the point of Subversion, but at
> least it will be cheaper. :(

One additional consequence of using a lock model is that productivity can
sink like a rock, for several reasons. If your developers aren't in
regular communication and a file one needs is locked by another, then you
have to wait until the other is around to unlock it. The second reason is
the obvious speedup of having two or more people work on one file. Having
used VSS at various points, I can say that the lock-unlock model *is*
horrible, especially what you intend to use it for.

If you're not in a position to make decisions as to what model you use,
you can at least go with subversion 1.2 and the lock model, and then later
attempt to persuade your developers (and whomever else is in the way) that
the copy-modify-merge solution is the way to go.

-- 
Ryan Ernst
http://shadowlife.warflame.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org