User Guide - Mks.com

Chapter 7: Using Change Packages and Reviews
216
Because a change package is stored with each new revision, there is a
relationship between every change in the repository and all of the
other changes made by the author.
Using change packages with the track locks feature, managers can
monitor work in progress.
Groups of changes can be reviewed as a unit. If reviews are
mandatory, changes are reviewed before they are committed to the
server repository.
TIP
You can expand the capabilities of change packages with Integrity Manager to
take advantage of workflow and process management through the use of
issues. The change packages can then be associated with issues. Enabling the
Integrity Manager integration also permits multiple change packages for each
issue. For more information, see “The Integrity Manager Integration” on
page 371.
Using Change Packages to Control
Development
The following is an example of a way to use change packages to control
development. You can combine this example with the review process to
control what changes become a permanent part of the repository (see
“Change Package Review Process” on page 240).
1 Open the Manage Change Packages window (see “Managing Change
Packages” on page 220). This is your control center for managing your
development activities.
2 Create a change package (see “Creating a Change Package” on
page 217) for the changes you need to make to address an issue. The
change package acts as a container, grouping together the specific
members (files) that need to be changed to address the issue.
Source Integrity assigns the change package an ID and leaves the
change package in an open state.
You can see the change package listed in the Manage Change
Packages window.
3 View the change package in the Change Package view (see “Viewing
Change Package Details and Entries” on page 226). All operations you
associate with the change package appear in this window.
u s e r g u i d e