MKS Implementer 2006 Administration Guide

Preparing for the Next Release
Implementer and MKS Source Integration
As the development cycle progresses and work on the current release comes to completion,
minimal administration is required to prepare for creating a new release. The basic tasks
consist of closing the current version/release and opening the new version/release.
NOTE The ongoing administration tasks are functions you perform in Implementer.
MKS Source does not require ongoing administration.
To prepare for a new release
1 Close the current release of the product/version.
a) In the Work with Releases for a Product/Version panel, select the current release
with option 12=Change status, and press ENTER. In the Change Release Status
window, select the appropriate closed status with option 1=Select, and press
ENTER.
b) In the Product Version Release Maintenance panel, checkpoint the release by
pressing F6=Checkpoint in MKS Source.
2 Create and open a new release of the product/version.
3 Begin development on the new release.
You can perform patch and PTF release activity with environments in previous versions
of the product now set to development path *VERSION. These changes are tracked on
branch revisions with suffixes after the departure point, for example, 1.4.1.2 for a
change to an item that was at revision 1.4, while the trunk revision, for example, 1.5, is
assigned the next revision of the item promoted into the *HEADREV version.
Preparing for the Next Version
NOTE You must perform these steps for each new release.
As the development cycle progresses and work on the current version comes to completion,
minimal administration is required to prepare for creating a new version. The basic tasks
consist of closing the current version/release and opening the new version/release.
NOTE The ongoing administration tasks are functions you perform in Implementer.
MKS Source does not require ongoing administration.
293