RE: Re: Lock/unlock memory leak ?

>>> Clicking "Get lock..." on the main directory allows us to lock every file
>>> in it.
>
> Well... the phylosophy we have here is that the tools shall support the
> production process, and not force the production process to be changed.

The problem is that your production process is broken when viewed in conjunction with SVN. You can't really lock a whole branch that way and really achieve anything with it. The problem is that the developer will not know that it has been locked until he/she tries to commit. This will waste (your) precious resources (developer time). This won't be fixed with a pre-commit hook either.
 
To solve this problem you will have to rely on: Other Means of Communication! (*gasp*)
This can for example be a mailing list, or project meetings.
 
And what happens if a developer accidentally commits to the branch? Nothing! As long as you either have made a tag or simply noted the revision number of the branch (and you do that already I hope?) you are completely safe! (This is version control after all. :-) ) The only thing you risk is having to revert the changes later on. (And if you feel that the risk of "polluting" the repository through careless developers a pre-commit hook will protect you. (And you are of course free to create a tool/script for your non-technical project admins to enable/disable it for different directories.))
 
Think about the whole situation again. Locking is not the answer.
 
Hans-Emil
Received on Mon Apr 3 12:32:47 2006