...
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 (Important) | This covers the major accomplishments that the project wants to cover during the release, such as feature, bugfixes, test coverage, documentation, etc. |
| Relationship Clarification (Important) | For this part, when making plans and accomplishment, please clarify the relationship with other projects/open-source software/previous releases, and how to collaborate with them. |
| Release Milestones (Important) | 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 Accomplishment (Important) | This covers the major accoplishment of the release, such as delivered feature, budfixes, pased test, delivered documentation, etc. |
| Summary of Outstanding Accomplishment | Highlight outstanding accomplishment and explain its benefit. |
| Delta between planend and actual accomplishement accomplishement (Important) | List the difference between the planned accomplishement in Release Plan and the actual accomplement. |
| Plans for Next Release (if any) | Brief description of plans for next release. |
...