MKS Implementer 2006 Administration Guide

Host System Scenarios
This user has authority to check out from the modified and base production
environments and promote to the modified and vendor PTF quality assurance
environments.
Tester performs the tests either in the modified quality assurance or vendor PTF
environments using their own copy of the changes.
Administrator promotes changes into the test environments to allow the tester to
start testing a change.
Administrator creates projects and moves the promotion requests to modified
production or to the vendor base production environments. This user also has
conflict resolution capabilities.
Release Control: Scenario 10
Overview
A typical release control development scenario starts with setting up your products and
versions, and attaching the environments associated with each product at the version level.
You then create an open release (the release must be at a status that allows software changes
to occur, for example, ENV-OPEN). Any issues or design requests that have at least one
entity promoted to production while the release is open are attached to that release.
Follow your normal change management procedures for checking out and promoting
member/objects. When you are ready to close a release (for example, for system test or to
target production) set the release to a status that does not allow software changes (for
example, ENV-CLOSED). This prevents promotions from targeting the environments
defined for the version that allow creating standard releases from it (defined when you attach
an environment to a version). Changing the status from one that allows software changes to
one that does not allows you to capture an image of the Implementer repository so you know
exactly which objects were in the release when it closed.
37