| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-fBwPDexzVTCxcEM5H1ljeQ" name="02_01_package_the_release,_DQowcWzvEeCPgecPbK9bdg" guid="-fBwPDexzVTCxcEM5H1ljeQ" changeDate="2012-05-30T14:12:33.929-0700" version="7.5.1"> |
| <mainDescription><p>
 |
| The key activities normally used to package a release:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Assemble the components and integrate them through a normal (i.e., continuous integration) or release build script
 |
| </li>
 |
| <li>
 |
| Install the release package in one or more test environments and verify its integrity
 |
| </li>
 |
| <li>
 |
| Tag the elements of the release package in the code base to create a baseline
 |
| </li>
 |
| <li>
 |
| Package appropriate documentation to accompany the release: 
 |
| <ul>
 |
| <li>
 |
| Deployment plan
 |
| </li>
 |
| <li>
 |
| Build plan, procedures, and scripts
 |
| </li>
 |
| <li>
 |
| Backout plan
 |
| </li>
 |
| <li>
 |
| Relevant licensing information
 |
| </li>
 |
| <li>
 |
| Relevant infrastructure information
 |
| </li>
 |
| <li>
 |
| Release communiques
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| </ul></mainDescription> |
| <sections xmi:id="_IAEdheB-EeC1y_NExchKwQ" name="Assemble components" guid="_IAEdheB-EeC1y_NExchKwQ"> |
| <sectionDescription>Question all the developers on the development team to determine which components are ready for packaging. Only package
 |
| those components that were completed and accepted during the previous feature development sprint/iterations. Components
 |
| that were not finished or not accepted should not be bundled, unless the customer has granted an exception or they are
 |
| infrastructure-related components.</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAEdguB-EeC1y_NExchKwQ" name="Test the release" guid="_IAEdguB-EeC1y_NExchKwQ"> |
| <sectionDescription>After the components have been packaged and built, that executable should be installed and run in a test environment that
 |
| mimics the production environment. A "staging" environment usually is maintained for this purpose. Testing typically
 |
| includes a "smoke test" in which key features are exercised to highlight any unplanned behavior.</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAEdhOB-EeC1y_NExchKwQ" name="Tag source code repository" guid="_IAEdhOB-EeC1y_NExchKwQ"> |
| <sectionDescription>In the team's configuration management (CM) tool, tag all the components that went into the release package so that the
 |
| package can be reconstructed at a later date, if needed. This tag is known as the release "baseline."</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAEdg-B-EeC1y_NExchKwQ" name="Package release documentation" guid="_IAEdg-B-EeC1y_NExchKwQ"> |
| <sectionDescription>Gather all the product, user, and support documentation developed earlier in the production release sprint/iteration and
 |
| add it to the release package.</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAEdgeB-EeC1y_NExchKwQ" name="Deliver release package" guid="_IAEdgeB-EeC1y_NExchKwQ"> |
| <sectionDescription>When the entire release package, including documentation, is ready, deliver it to the deployment manager and the release
 |
| team in a timely manner. Be prepared to answer questions from the deployment engineer, especially questions about
 |
| conformity to release controls.</sectionDescription> |
| </sections> |
| <purpose>The purpose of this task is to render a complete, deployable package capable of being released into the production
 |
| environment by the deployment engineer.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
