Artifact: Release Notes
| Release Notes identify the contents-including the changes and known bugs-of a versioned build or deployment unit that has been made available for use. | |
| Other Relationships: | Part Of End-User Support Material |
| Role: | Deployment Manager |
| Optionality/Occurrence: | Recommended. |
| Templates and Reports: | - Template: Release Notes |
| Examples: | - CREG Release Notes - Transition Phase - CSPS Release Notes - Transition Phase |
| UML Representation: | Not applicable. |
| More Information: |
| Input to Activities: - Create Deployment Unit | Output from Activities: - Write Release Notes |
Purpose
The purpose of the release notes is to describe the characteristics of each product release.
Timing
The release notes are created or updated for each executable release, however they are generally not treated as a formal artifact until the Transition phase, when the product is released to the end-user community.
Responsibility
The Deployment Manager role is responsible for writing the Release Notes.
Tailoring
Release notes are generally considered useful to produce, even for purely internal releases, although their format might be simplified, casual or informal. In particular, testing and technical writing staff will find release notes useful in conducting their activities.
This artifact is commonly enclosed in End-User Support Material.