Re: Subversion 101: To lock or not to lock..

Michael March wrote:
> "When editing an html or jsp file, it is often necessary to modify
> many parts of the file.

That's not jsp/html specific at all but IMHO holds for almost every kinda sourcecode.

What you tell sounds to me like you struggle to change the culture of a stubborn crowd. I'd say
chances aren't good to do so by education (tell'em about XP, agile processes, the "pragmatic" stuff
etc.) nor by brute force ("I'm in charge and just decide").

Best is to make small changes that return a visible benefit for ALL and feels comfortable. That's
what I experienced back when I introduced continuous integration. First no one bothered or was
negatively biased. But after a few weeks everybody enjoyed the immediate feedback after a commit -
everthing works!

So maybe don't set up a policy concerning locking at all, but ensure that who needs to edit in case
can break the lock - to avoid productivity blocks. And get'em to accept that everybody can edit
everything at any time. No private code ownership. Maybe things sort out by itself.

Greetings,
        M

P.S.: Please tell us your experiences after several weeks.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 9 10:46:31 2006