Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
COSMOS1.0Release Review Prep
COSMOS 1.0 Release Review Preparation
Tasks & Milestones:
- Get PMC approval for release review
- Target:
- Create Project IP Log and complete IP Clearance review
- Initial draft:
- Reviews:
- Final Draft:
- IP Clearance Review:
- Create Release Review docuware
- Initial Draft:
- Reviews:
- First draft to EMO:
- Final draft to EMO:
- EMO release review:
Release Review Content
1. Summarize major features of the release or features that have generated significant discussion during dev cycle 2. Summarize state of non-code aspects of release (user doc, localization/externalization, examples, tutorials, articles, etc.) 3. Certify that the APIs in the release are Eclipse Quality 4. Summarize the architectural quality of the release (discuss "intrinsic nature of being extensible" embodied by the project, unresolved overlap with other projects, unpaid "merge debt" from incorporating various components, etc.) 5. Summarize usability of the tools (this is about using the tools to solve development problems, not the academic sense of UI evaluation/testing) 6. Summarize the features from previous releases that are being end-of-lifed'd in this release (N/A since this is our first release) 7. Summarize bugzilla state (defect and enhancement statistics) 8. Summarize the standards compliance of this release 9. Summarize the UI usability and conformance to the Eclipse UI Guidelines 10. Discuss the initial schedule and any changes to the schedule over the course of the release 11. Summarize the project's development of its 3 communities 12. IP Issues (see below) 13. IP Issues Speak-Up-Now - EMO asks if any member would like to assert that this release infringes on their IP rights 14. Unveiling of project plan (full or draft) for next release
Detail: IP Issues
As per the Eclipse IP Policy, these steps must be done:
1. The project leadership verifies that:
... that the about files and use licenses are in place as per the Guidelines to Legal Documentation.
... all contributions (code, documentation, images, etc) has been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
... that all significant contributions have been reviewed by the Foundation's legal staff. Include references to the IPZilla numbers of all clearances.
... that all non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff. Include references to the IPZilla numbers of all clearances.
... that all Contribution Questionnaires have been completed
... the "provider" field of each feature is set to "Eclipse.org"
... the "copyright" field of each feature is set to the copyright owner (the Eclipse Foundation is rarely the copyright owner).
... that any third-party logos or trademarks included in the distribution (icons, help file logos, etc) have been licensed under the EPL.
... that any fonts or similar third-party images included in the distribution (e.g. in PDF or EPS files) have been licensed under the EPL.
2. The PMC provides a Project Log that enumerates:
a. every piece of third party software including information on the license
b. every major contribution
c. the name of every contributor including non-committer contributions via bug fixes with bug #'s
d. the About files which contain any non-standard terms (e.g., a reference to a license other than the EPL, etc)
3. The EMO will validate for (a) and (b) that Contribution Questionnaires have been properly submitted and EMO approvals have been completed.
4. A frozen copy of the reviewed-and-approved-by-Eclipse-legal Project Log is part of the Release Review documentation. It can be included in the docuware or as a separate document.