From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Tuesday, September 18, 2012 11:58 AM
To: 'Midrange Systems Technical Discussion'
Subject: development/test/prod environment mini-survey
My company is considering separating dev from test.
For this survey: DEV is where programmers play; TEST is where business analysts and users try out new stuff, PROD is where the money is made.
Please respond only if NOT a software vendor - Im sure rules are much different when there are thousands of installs involved at a software vendor.
I would like to inquire how other iseries shops are handling this.
1) Is dev/test/prod on same LPAR?
Can be. Doesn't need to be. You do need to secure test to mimic production.
2) Is dev/test/prod on same box?
3) How frequently are promotions from dev to test allowed?
Depends upon your development methodology, extent of change being tested, etc.
4) Does separating DEV from TEST require more time & effort for a given development project?
Not if you view TEST as a quasi-production environment.
You set it up once to mimic production then promote your changes to and from it.
5) What would be some reasons why this is a good idea (besides the auditors told us to)?
You don't accidentally munge up production.
You don't introduce unexpected changes due to a developer making just one last change.
Your software will operate as advertised.
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l