[p4] Managing groups of users

[Hoff, Todd]

> -----Original Message-----
> From: John Griffin [mailto:JohnG at sedonanetworks.com]
> Sent: Tuesday, October 10, 2000 8:50 AM
> To: 'perforce-user at perforce.com'
> Subject: [p4] Managing groups of users
> 
> 
> Hi all,
> in the development process we are using we need to, at the end of the
> development cycle, lock down a branch and only let people 
> update it when
> they have been given leave to do so. I have accomplished this 
> by removing
> all write privileges from the branch and then grant write access to an
> individual only when they need it. The system works quite 
> well but I can see
> a problem with scalability; when there are more and more 
> development streams
> to be locked down I will spend more and more of my time 
> denying and granting
> people access to update branches. It also places me, the 
> super user, in the
> critical path of an update.

We use a submit trigger to filter submits by user and bugid.
A web allows which users and bugs to be configured on a per 
branch basis. It works but when a trigger screws up it prevents
everyone from submitting.