...
XGVela follows the LFN Project Lifecycle process which includes the Project Review Process, and can be found here: LFN Project Lifecycle
2.5. Release Process
Initially the TSC will make all decisions about Releases of the project. This may be amended by vote to include Project Committers as the project grows. However, to be able to measurable, the project must demonstrate a history of following the Release Process. The purpose of the Release Process is to assure openness and maximum opportunity for participation. The idea is to have a simple, clear, public declaration of what a project intends to do and when, and what was actually done in a release cycle. Towards that end, a project following the ‘Release Process’ should have a Release Plan published at the beginning of its release cycle by its Committers, after review by the TSC, and a Release Review just prior to the project release.
Both Release Plan and Release Review documents are intended to be relatively short, simple, and posted publicly on the wiki to assist project in coordinating amount themselves and the general world in gaining visibility.
Release Plan and Release Review should contain roughly the following sections:
- Introduction
- Release Deliverables
- Release Milestones
- Expected Dependencies on Other Projects
- Compatibility with Previous Release
- Themes and Priorities
- Features delivered
- Non-Code Aspects (user docs, examples, tutorials, articles)
- Architectural Issues (if any)
- Security Issues (if any)
- Any other Open Issues (if any)
- Quality Assurance (test coverage, etc)
- End-of-life (API/Features EOLed in Release)
- Summary of Outstanding Bugs
- Summary of Standards Compliance
- Delta between planed schedule and actual schedule
- Other