RE: Change Control

Dave,

We are/where a small shop; just went through a conversion to the corp
system/umbrella,
so I will be looking for work - when things calm down here.

We had a staff of 4 people doing coding here, instead of purchasing
something
like Turnover or any other packages that are out there (that's the only one
I have
used prior to working here)...  We opted to do the following to keep our
ducks in a row.

Do not make changes to "live" source code,
copy it to your personal "test" library,
on the live source member, place a underscore and your initials at the
end of the source type (ie: rpgle_mm).
Do your thing, test it, test it, test it.
Move it back over, thus over-writing the source type back to "normal".

In six years it only bit us once, someone forgot to "check out the source".

The only "complications" with a procedure like this, is "training" everyone
to
actually do this and when you "bump heads" on multiple projects, it can be
a real bear, but we did our best to plan out projects to avoid bumping
heads.

HTH

Mark A. Manske
Sr. Project Lead



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Dave Snyder
Sent: Thursday, May 06, 2004 3:08 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Change Control


What are small shops (less than 5 on staff) doing for change control
procedures? if anything. Interested to hear especially from any financial
institutions.
Dave


_______________________________________________
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.