User Guide - MKS

Change Package Feature Overview
The abcBusiness software company has released their Aurora software,
version 3.0. When the release was completed, the project was
checkpointed. The development team is now working on a new set of
features for the next release, 4.0. A new feature for this release is a
timestamp function. All the changes associated with the timestamp
function have been recorded in a change package, or set of issues, that
isolates the feature from other features.
Now abcBusiness receives a request from a customer who has Release 3.0
but also needs the new timestamp feature for its global operations. The
code in development for Aurora 4.0 is not stable enough for release and too
many resources would be required to accelerate the release schedule. How
can abcBusiness provide the timestamp feature without affecting the
current release? Because the code for this feature is isolated within a
change package, the Apply CP command can be used to transfer the
feature to the earlier, stable release.
The buildmaster at abcBusiness would:
Create a variant project off of the checkpoint for version 3.0. This
variant project is isolated from the rest of the development team so
that unwanted changes are not added to the main trunk of the
development path.
Use Apply CP to apply the change package to the variant project. The
change package contains all the files that were changed or added to
produce the timestamp feature. Apply CP is essentially adding the
feature to the variant of Aurora 3.0.
Create an executable of the software.
That executable can then be tested by Quality Assurance and shipped to
the customer.
Resync CP and Resync By CP Commands
This section provides an example to show how Resync CP can be used in
your environment. The example also illustrates how Resync By CP can be
used in a developer’s sandbox.
The development team at abcBusiness is working on the next release,
which contains hundreds of files that span many Source Integrity projects.
Whenever a fix is made, or a feature added, it may require the
manipulation of a single file, or many different files across multiple
projects. A fix or new feature may also include new dependencies within
the source code.
353