User Guide - Mks.com

Chapter 7: Using Change Packages and Reviews
Change Package Review Process
How the CP
Review Works
240
A change package review is a review of changes by specified reviewers
before the changes are committed to the server repository.
If change package reviews are mandatory globally, then all change
packages must progress through the change package review process.
If change package reviews are mandatory at the project level only, then a
change package only progresses through the review process if it contains
at least one entry associated with a member in a project that requires a
review. Change packages follow the review process before the changes are
successfully committed to the server repository. All other change packages
function as non-review change packages.
IMPORTANT
To use change package reviews, you must use Source Integrity 8.6 or later.
A change package reviewer is a user specified by your administrator to
review change packages containing members associated with specific
projects. The reviewer may be individually specified or a member of a
specified reviewer group. In the case of a reviewer group, any member of
that group casts an accept or reject vote on behalf of the entire group.
A change package watcher is a user specified by your administrator who is
notified when a reviewed change package is closed after being successfully
committed to the repository. Change package watchers may be
individually specified or a member of a specified watcher group.
A Super Reviewer is a user with permission to vote on change packages that
the user is not a listed reviewer for. Voting as a super reviewer overrides
all other votes, for example casting an accept vote as a super reviewer is
sufficient for accepting the change package.
Following is a summary of how the change package review process works:
1 The review starts when a developer (change package creator) submits
a change package containing deferred entries (or any combination of
deferred, pending, or committed entries).
2 Source Integrity creates a pending change package entry for each
deferred entry, and where necessary pending revisions.
3 Change Package Reviewers (possibly a mentor or a senior developer)
accept or reject the change package.
u s e r g u i d e