Re: Programmer Authorities

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

>If U have only one system and U have programmers working on it (for
>applications, not system programs for save/restore etc.) then use three (3)
>separate environments; one for development purposes, one for the acceptance
>tests and one production environment (=the largest).

>Rina,


I'd recommend 4 environments:

Production:  Programmers can have read-only access

Training:  Production users can try out things; new employees can be trained

QA:  Where the new stuff lives until it's been approved for production.
Moves here from the Development environment once it has passed preliminary
testing.

Development:  Programmers' Playground.  Here's where the stuff is developed
and cleaned up to a point where it can be shown in public.


Of course, this all takes disk space.  Which brings up my pet peeve:  The
Test Environment(s) Do NOT Have To Contain Every Record From The Production
Environment!

--Paul E Musselman
PaulMmn@ix.netcom.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---