...
Independent releases of individual components could address these concerns. Rather than take a global snapshot of trunk, tested and documented component versions could be bundled together for general QA.
Expectations on Releases
Individual component teams - whether one person or many - would take on the responsibility of release management for their component. This includes:
- Documentation of the changes, both technical and user-facing as called for. For a more thorough breakdown of the kinds of questions that need answers, see New Feature Documentation.
- Testing that the component is completely functional and internally consistent to the point of release-readiness (i.e. whether it introduces regressions in other components will be a matter for the full Sakai release QA to follow later, though API changes should again be thoroughly documented)
- Recruiting community resource to see all this accomplished, where needed. Foundation Staff will be able to help communicate this need.
If a particular component release version does not meet this standard, it should be expected that a prior stable version of the component will be reverted to for a full Sakai release.