Hi all!
We have just deployed svn 0.27 and we are very happy, however a lot of
programmers and designers are complaining about not beeing able to lock
files. Normally, this is not a problem (we like the edit/merge concept) but
some files, like uml diagrams and documents in binary format, should never
be used by more than one person (except read-access, of course.)
I understand that this feature is planned beyond 1.0, but I hope you would
consider pushing up the priority on this issue. For two of the projects we
plan to migrate, not beeing able to exclusively lock files requires us to
continue with our old revision system.
What I would REALLY like is a lease based system where person A gets
exclusive access to a resource for a spesific amount of time, such as 2
hours or a day. For instance, to obtain exclusive access for 30 minutes, I'd
like to do a "svn lock <url> -t 30m". Without the "-t" option, the
exclusiveness would not expire until I commited. I would also like the
ability to do a "svn unlock <url>" to force the lease to expire.
After the lease period, person B can get to the resource. If person A still
has the resource (he forgot to commit before the lease time expired), he
gets an error. He didn't commit within the time he requested so now it's his
problem - now he has to merge/resolve when person B has commited, but that's
how I would like it to work.
I guess leasing should only work on files beeing tagged "leasable", using
PROPSET, perhaps.
Thanks.
Ron
_________________________________________________________________
Use MSN Messenger to send music and pics to your friends
http://www.msn.co.uk/messenger
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 3 10:10:30 2003