User Guide - MKS

Chapter 12: Advanced Change Package Operations
How Resolution
CPs Work
400
You can select an existing change package—or create a new one—and
then ask Source Integrity to use it as a resolution change package. The
only requirement is that the change package must be in the Open state.
For the greatest level of control in isolating a feature or issue, it is
preferable to start with an empty resolution change package. When
the resolution change package contains no previous entries, the only
additions will be those that specifically relate to the issue in question.
If the resolution change package contains other change package
entries, Source Integrity will also process those entries.
To avoid the problem of overlaps and conflicts during the Apply CP
operation, you can only apply one resolution change package per
operation.
The abcBusiness company has two development teams:
a Product Team that develops new features and software for the main
release cycle
a Maintenance Development Team that maintains the released
software and addresses bugs that are identified by customers
The Product Team (PT) implements new features and designs on the main
development path.
The Maintenance Development Team (MDT) works on a variant
development path for Release 2.0 and fixes any problems in the newly-
released product. The main goal of this team is to produce bug fixes for
Release 2.0a. The work process for the MDT is:
A bug is reported by a customer.
A change package for the bug is created, in this case it has the
container ID 1204. If the Integrity Manager integration is enabled, an
issue is created and then associated with a created change package.
An MDT developer is assigned to fix the problem.
The MDT developer creates a change package.
The MDT developer makes the necessary changes and tests the code.
The MDT developer checks the modified files back into the variant
project, making sure to associate the files with change package 1204:1.
In this case, all the work of the MDT developer is now checked into the
variant development path and will be part of release 2.0a. However, what
is the best method for transferring the MDT bug fix work back to the main
u s e r g u i d e