02.05.2013 Views

User Guide - Mks.com

User Guide - Mks.com

User Guide - Mks.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 7: Using Change Packages and Reviews<br />

What Are Change Packages?<br />

214<br />

A change package is a group of changes made by a single user that can be<br />

considered a logical unit of work. Only the creator of a change package<br />

may add entries to that change package. Change package entries take the<br />

form of operations, both deferred and <strong>com</strong>mitted. When reviews are<br />

mandatory, change package entries take the form of pending entries before<br />

they are <strong>com</strong>mitted.<br />

For more information on change package entries, see “Change Package<br />

Entry Types” on page 220 and “CP Entry Categories” on page 244<br />

A change package administrator is a user with the permission to discard,<br />

close, and submit change packages that were not created by that user.<br />

The following rules apply when using issues and change packages:<br />

Each change package has a unique change package ID (CP ID). The CP<br />

ID is a colon separated identifier of the following form:<br />

:<br />

NOTE<br />

If Integrity Manager integration is enabled, then the issue ID is used as the<br />

container ID. For more information, see “The Integrity Manager Integration”<br />

on page 371.<br />

A change package acts as a log of both the changes to members that<br />

have already been <strong>com</strong>mitted to the repository (server), and as a<br />

record of work in progress, which is only visible to the user on the<br />

desktop and not <strong>com</strong>mitted to the repository. It tracks the work in<br />

progress using deferred operations that can be associated with a<br />

change package. When reviews are mandatory, a change package acts<br />

as a control placed on changes to the repository, by making them<br />

pending before they are <strong>com</strong>mitted (see “Change Package Review<br />

Process” on page 240).<br />

A traditional change package has the following states: Open, Closed,<br />

Discarded, and CommitFailed. A change package is open, or “in<br />

progress” until you close it, which signifies that work on the change is<br />

<strong>com</strong>pleted. If the changes fail to <strong>com</strong>mit to the repository, then the<br />

change package can be submitted again, or opened to continue work.<br />

When reviews are mandatory, a change package has additional states<br />

before it is closed (see “CP States” on page 241).<br />

u s e r g u i d e

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!