Re: Percolating QC changes

With turnover, you check out the source from qa to dev, then when done,
promote back to qa. this ensures that the final qa will match the final
dev version.
it *is* possible for a programmer to make changes directly to the qa
version, but then turnover issues an error when attempting to promote to
prod.

Jeff Young
Sr. Programmer Analyst

On Thu, Mar 2, 2017 at 2:06 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

The change needs to go thru the devs. The development library no longer
matches the QC build, so you have to make the changes to the data & source
for the QC build, and then build again. Almost certainly all of that must
be duplicated in the development library. Source code can be merged, but
data???



-----Original Message-----
From: Sam_L [mailto:lennon_s_j@xxxxxxxxxxx]
Sent: Thursday, March 02, 2017 12:55 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Percolating QC changes

So someone in QC is making changes? In my experience, an object had to go
back to development to make the changes and QA was just a testing & review
group.

However, if QA can make changes, you might want to look at Aldon
Scompare/Harmonizer. Many years ago we used it to do a 3-way merge of
vendor code with our changes when they updated their source. I believe it
is still available (at least it was before Rocket bought Aldon.) Did a
good job but you still had to review the code.

Sam




--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD