Percolating QC changes -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Percolating QC changes
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Thu, 2 Mar 2017 14:00:11 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Given a theoretical app with development, QC and production libraries. The devs send a new build to the QC library and continue work in the development library. 1-2 weeks later, the QC department returns their report, and code and data changes are required in the QC build.

Is there a best practice for percolating those changes to the development library?

TIA

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Percolating QC changes , David Gibbs
Re: Percolating QC changes , Mark Murphy/STAR BASE Consulting Inc.

This mailing list archive is Copyright 1997-2024 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.