Need ammo against those who say "lock everything"

We have a new team lead on my project, and yesterday she was complaining
that our configuration management tool (subversion, of course) has no way to
lock stuff. I said, "That's going to be in a future release."

Then I nearly wet myself when she replied, "That will be great. Then we can
lock all the code to whoever is assigned to work on it." She's not talking
about binary files, here. She's talking mergable code.

Is it just me, or is this idea absurd? I civilly disagreed with her, and I
would absolutely *love* to get my hands on some ammunition explaining why
locking everything is a Bad Idea. Anyone know of a good document, URL,
something like this?

On the other hand, we can just cross that bridge when we come to it... Maybe
after a week of complete stalemate in our dev team, she will see the light.
;) But I'd rather not waste that week.

****
**** --- Eric Wadsworth, 520-533-2749
****

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 23:10:15 2004