User Guide - MKS

Chapter 7: Using Change Packages
Using Change Packages to Control
Development
202
The following is an example of the recommended way to use change
packages to control development:
1 Open the Manage Change Packages window (see “Managing Change
Packages” on page 206). This is your control centre for managing your
development activities.
2 Create a change package (see “Creating a Change Package” on
page 203) 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 window (see
“Viewing Change Package Details and Entries” on page 211). All
operations you associate with the change package will appear in this
window.
4 As part of your development process, identify the members that are
affected by the issue. Add the members to the change package during
one of the following operations:
Check Out
Rename
Lock
Add Member
Drop Member
NOTE
You can only add change package lock entries to a change package through a
check out and member lock if lock tracking is enabled. For more information on
lock tracking, see your administrator.
The operations are listed in the Change Package window.
u s e r g u i d e