| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-QpMXBM5_A8w0pRyIT5n5yA" |
| name="change_set,_1QU9MAIoEdyLh7vsrHZ4YA" guid="-QpMXBM5_A8w0pRyIT5n5yA" changeDate="2007-05-31T16:18:27.346-0700"> |
| <mainDescription><p>
 |
| A change set is a logical grouping of related changes made to the implementation and supporting artifacts. Change sets
 |
| are defined for a specific purpose and encompass all changes made to achieve that purpose.
 |
| </p>
 |
| <p>
 |
| Change sets allow for multiple related changes to be referred to as single item, simplifying tracking of&nbsp;that
 |
| item’s progress through the development lifecycle.
 |
| </p>
 |
| <p>
 |
| The change set forms the basic unit of configuration control, accountability, and collaboration on the development
 |
| team.&nbsp; Additionally, change sets track the dependencies between artifact changes that facilitate discovery and
 |
| correction of configuration inconsistencies. The relationship between items in a change set can be used to verify that
 |
| all related changes have been included in a build.
 |
| </p>
 |
| <p>
 |
| Change sets have the following characteristics:
 |
| </p>
 |
| <ol>
 |
| <li>
 |
| Change sets consist of changes that belong together and can be built and tested together.
 |
| </li>
 |
| <li>
 |
| Change sets are owned by a single developer.
 |
| </li>
 |
| <li>
 |
| Change sets represent small, testable changes to the system.
 |
| </li>
 |
| </ol>
 |
| <p>
 |
| Multiple change sets&nbsp;may be&nbsp;related to&nbsp;a single work item.
 |
| </p>
 |
| <p>
 |
| Change sets are also known as CM tasks, activity change sets, change lists or change packages.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |