Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| ### Patterns & Practices Deploying to the .Net Environment Microsoft Operations Framework |
| Release a Product Release Manager
|  | Participating Roles Responsible: Release Manager
### Overview At some point in the project, the amount of functionality will warrant a release. There are many types of releases, such as alphas, betas, and the final version or point release. This release will have impacts greater than the immediate development team that built it. There will be users to consider. For externally released software products, marketing and sales collateral need to be created. Internal systems require training and operations support. To prepare these folks for the upcoming release, a release plan is created. The release process and corresponding release plan differ depending on the type of product and whether it is for internal or external consumption. # Entry Criteria The build designated as the release candidate meets the date or functionality objectives called for in the test approach. The build designated as the release candidate meets the quality objectives called for in the test approach. # Activities
1 | Execute a Release Plan | Review material for accuracy. Coordinate product delivery.
2 | Validate a Release | Run complete regression test. Open bug reports.
3 | Create Release Notes | Document known limitations. Review the release notes.
4 | Deploy the Product | Package the product for release. Create the media master or execute the deployment of the product.
# Exit Criteria
| The system is released.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |