RE: RCS permission question

[Cannon, Alastair, VF UK, Partner]

In strict configuration management terms you do *not* check out in prod
ever.
Prod fixes should be made in a Prod 'mirror' and after testing and
verification (**and**  sending back into dev/test) migrated into the
'live' env.

Alastair


Alastair Cannon 
Configuration Management 
CoUk WebServices 
EDS (UK) Limited 
Mobile +44 (0)7825118181 
E-Mail address@hidden 
E-Mail address@hidden 
Electronic Data Systems Ltd
Registered Office:, Lansdowne House, Berkeley Square, London W1J 6ER
Registered in England no: 53419
VAT number: 432 99 5915 


-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Aaron S. Hawley
Sent: 05 December 2008 17:18
To: Tran, Hai
Cc: address@hidden
Subject: Re: RCS permission question

Sounds like you'd have two groups.  One called "development", and
another called "production".

Have the RCS folder (you're using RCS folders, right?) in the
development location.  The RCS folder should be writable by the
development group, and readable by the production group.

Then make a production location where only the "production" group can
make writes to.  In the production location make a symbolic link to the
RCS folder.  Then use the checkout commands to retrieve what you need
from RCS in the production location.

On Tue, Nov 18, 2008 at 10:51 AM, Tran, Hai <address@hidden> wrote:
> Hi,
>
> Generally, do you create a user call RCS and group call RCS?  We want 
> only certain developers to checkout in RCS on development and testing 
> environment, but not in PRODUCTION.  Only a certain user can checkout 
> in Production.  So do you create a RCS user and a RCS group for this?
>
> Thank you,
>
> Brian Tran