MKS Implementer 2006 Administration Guide

Remote System Scenarios
Allow distribute changes controls whether the release can be the default release
to distribute to a customer system as the most current release available. This is
also used for release deployment.
The release category and the release status together determine the development path
that a release must follow, and the dependency automatically associated between a
current release and a previous release.
Release Control Development Cycle
The development cycle associated with release control effectively handles when objects are
promoted back to production, without hindering the start of new development. Release
control supports both single version and multiple version development models, as illustrated
in the following chart.
Remote System Scenarios
The next six scenarios pertain to promotions that target remote iSeries systems using the
Implementer Receiver.
39