Post 1.0 - Does locking have priority?

I assume post 1.0 stuff will begin in march/april?

My question is: will locking get priority of post-1.0
stuff?

I "sold in" Subversion to our shop several months ago,
but now a group of users are starting to complaint
big-time.

Except for the following two issues, Subversion has
been a _huge_ success (we are using SVN on a large
scale):

1) Binary: While removing SourceSafe was a good thing
in general, we get a lot of problems with Word, PPT,
UML files and some other binary stuff. I'm worried
since some people have actually started to mail these
files to eachother as a way of sharing without
conflicts (!!?)

So we need locking ;-)

2) For text: No problems, except quite a few false
conflicts on XML files. Any solution here? I guess
diff'ing on XML should be done in an xml-canonical-way
to remove false conflicts. This is a weekly problem
because our IDE's uses xml-based project files. Each
time a file is added/removed, the xml project file is
updated, creating a potential conflict (although it
isn't...)

I really liked the proposal of locks that times out
(leased locks?), but it's not in the "locking plan"
document.

Could someone with expertice add that proposal to the
document?

Time-out as default seems to be a must for a shop like
ours where quite a few people are not that technical
(no probs for the developers, though)

Thanks!

Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jan 11 07:04:53 2004