I'm not shure want you mean.
Do you want to place a Lock on all members in a project's development path?
> use "menu/project/open" to open a view on the project's devpath you desire; select the top project and "Lock" the members recursive.
Do you want to prevent Members in a project's development path from being changed?
> use "menu/project/open" to open a view on the project's devpath you desire; select the top project and "Freeze" the members recursive.
> use "menu/project/open" to open a view on the project's devpath you desire; create a chekpoint on the project to store the current projects setup (for ever in a read-only way)
Please specify your use case!
Thanks for your reply. I want to prevent users from checking in into the dev branch in question. So which would be the best and quickest option of the three above ? And is there a command line equivalent ?
if you have the use case that you'd like to "lock" the branch because you want to avoid changes in the member revisions becasue you are planning for a "release checkpoint", then you also could freeze the members.
With a member being frozen, users can still check-in but can NOT set the member revision unless they "thaw" the member.
So you could give the permission to "thaw" a member only to a few persons (e.g. admins of this devbranch).
When the "release checkpoint" is done, the devbranch admins can thaw all members and everybody can continue working, updating member revisions etc.
The advantage of this solution is that you need not remove the checkin permission for all users and then set it again when they should continue to work.
One more use case could be that you simply want to deny that people continue to work on the devbranch at all. Then simply delete the devbranch. The last checkpoint is still there but people cannot continue to work there (unless you create a new devbranch).