tags:

views:

889

answers:

3

We are trying to follow the branching strategy from the TFS Branching Guide and have reached the point where we have made a branch representing a release, which should now be made read-only.

In the Properties|Security tab for the branch, it presents six user groups each with 10 permissions other than Read. Do I have to go through and click Deny on 60 check boxes, or is there a better way to make this branch read-only?

+2  A: 

As a quick-n-dirty, you could Lock it for Check Out (although the locker would have to remember to keep the lock in their pending changes forever... which makes me think there's a better way)

AakashM
dang! you beat me by 11s!
Josh E
the locker wouldn't have to remember to keep the lock - it would just prevent check-ins. The best strategy in that case is for Devs with pending changes to shelve them on the server.
Josh E
What I mean is that the Lock sits in the lockers pending changes window as if it were an actual 'pending change' - and clicking Check In with the lock item checked is what releases the lock. It's... somewhat unintuitive.
AakashM
I have a "management" workspace where I perform merges, hold locks, etc. That way I don't see them during day to day development.
Richard Berg
+6  A: 

Right-click the branch in the Source Control Explorer, and select the Lock... option

Josh E
+2  A: 

To answer the 2nd part of the question -- removing or denying the Read permission effectively denies everything else.

Richard Berg