<?xml version="1.0" encoding="UTF-8"?>
<!--Arbortext, Inc., 1988-2015, v.4002-->
<!DOCTYPE pubsConcept PUBLIC "-//PTC//DTD PUBS DITA Concept//EN"
 "pubsConcept.dtd">
<?Pub UDT template _font?>
<?Pub UDT _bookmark _target?>
<?Pub Inc?>
<pubsConcept id="_change_package_reviews_overview_52150" xml:lang="en"
xmlns:import="http://www.oberontech.com/import"
import:style="0_TopicSub"
import:map-object="2Heading_to_concept_in_conceptH1">
<title>Change  Package Review Benefits</title>
<prolog>
<metadata><keywords>
<indexterm>change package<indexterm>review<indexterm>benefits of</indexterm
></indexterm></indexterm>
<indexterm>review<indexterm>change package<indexterm>benefits of</indexterm
></indexterm></indexterm>
</keywords></metadata>
</prolog>
<pubsConbody>
<p>The benefits of using reviews are:</p>
<ul>
<li><p>Reviews provide a formal and enforceable review process.</p
></li>
<li><p>Reviews force changes to be reviewed before they are committed
to the repository thereby providing control over what changes are
accepted into a project by making operations pending. Unlike deferred
operations, which are stored only client side, pending operations
are stored server side and so are visible to all users. This can be
useful near the end of a release cycle as a pre-commit review of changes
before they are included in a release build.</p></li>
<li><p>Pending revisions are not a part of the current state of the
project until they have been reviewed (not at member revision); however,
they remain in the member history and can be checked out (without
a lock) by users (other than the creator) for review.</p></li>
<li><p>If the project is one that users will be building from, reviews
can remove the need for using a variant project to review changes
manually.</p></li>
<li><p>Reviews provide an alternative to manual post-commit review
while recording all of the review information.</p></li>
</ul>
</pubsConbody>
</pubsConcept>
