...
A Release Plan is recommended to contain the following information
Contents | Description |
---|---|
Project name | / |
Introduction | Provide the overview of the project and current status, which covers existing architecture, feature, stability, maturity, etc. |
Planned Major Accomplishments for the Release | This covers the |
major accomplishments that the project wants to cover during the release, such as feature, bugfixes, test coverage, documentation, etc. For this part, when making plans, please also mention the relationship with other projects/communities, and previous release. | |
Release Milestones | Milestones and timelines for the release. |
Release leader and active committer | A list of release leader's and active committers' information, which includes name, email, contact, company, release contents involvement. |
Challenges (if any) | Challenges the project is facing and needs help with from other projects, the TSC or the LFN umbrella |
A Release Review is recommended to contain the following information
Contents | Description |
---|---|
Project name | / |
Release Accomplishment | This covers the major accoplishment of the release, such as delivered feature, budfixes, pased test, delivered documentation, etc. |
Delta between planend and actual release accomplishement | List the difference between the planned accomplishement in Release Plan and actual accomplement. |