02.05.2013 Views

User Guide - Mks.com

User Guide - Mks.com

User Guide - Mks.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

CP Review<br />

Workflow<br />

242<br />

Change Package State Details<br />

Accepted An intermediate state denoting that the change<br />

package is accepted by all of the reviewers.<br />

Source Integrity automates the state change from<br />

Accepted to Closed if the changes are successfully<br />

<strong>com</strong>mitted to the repository.<br />

CommitFailed The state signifying that the pending changes could<br />

not be <strong>com</strong>mitted to the repository.<br />

Rejected The state denoting that the change package is<br />

rejected by a reviewer. The creator must manually<br />

move the change package to Open to continue<br />

development.<br />

Discarded Empty change packages or change packages with<br />

changes that do not need to be <strong>com</strong>mitted to the<br />

repository are moved by the creator to the<br />

Discarded state. Discarded change packages can<br />

be opened at a later date if needed.<br />

Closed The end state for the change package, when<br />

pending changes are successfully <strong>com</strong>mitted to the<br />

repository.<br />

A change package under review progresses through states in a workflow.<br />

For a graphical representation of the workflow, see the diagram “Change<br />

Package State Workflow” on page 244.<br />

The following is the change package progression through the workflow:<br />

1 A change package is created, and in the Open state. Entries are added<br />

to the change package by the developer.<br />

2 The developer submits the change package to begin the change<br />

package review process (see “Submitting Change Packages” on<br />

page 238), and Source Integrity moves the change package to the<br />

Submitted state.<br />

An e-mail is sent to notify the reviewers of the change package<br />

submission (if the server is configured to send e-mail notifications).<br />

The e-mail contains both change package and review information.<br />

3 The reviewer or reviewers, either accept the change package or reject<br />

it. The following can then happen:<br />

If all individual reviewers and at least one reviewer from a<br />

reviewer group (if any exist) accept the change package, it is<br />

moved to the Accepted state. For each vote cast by a reviewer,<br />

Source Integrity sends the reviewers an e-mail notification of the<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!