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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
