Options for the COSMOS June 2008 Release
This is my opinion/assessment. Please take it with a grain of salt. A COSMOS Lead needs to review this with an Eclipse person to confirm that this is accurate.
Option 1: Release 1.0 in June, graduate to a Top-Level Project
- Definition of a Top-Level project: http://www.eclipse.org/projects/dev_process/development_process.php#6_2_5_Top-Level
- If you look at the Project Lifecycle diagram, http://www.eclipse.org/projects/dev_process/development_process.php#6_2_Project_Lifecycle, does that diagram mean that before a project becomes a Top-Level project it must first be a Mature project?
- guidelines and checklists for Top-Level projects: http://www.eclipse.org/projects/dev_process/top-level-phase.php
Option 2: Release 0.x in June, remain an Incubation Project
- Definition of an Incubation project: http://www.eclipse.org/projects/dev_process/development_process.php#6_2_3_Incubation
- guidelines and checklists for Incubation projects: http://www.eclipse.org/projects/dev_process/incubation-phase.php
To achieve this, COSMOS must go through a Release Review. (Why do you say this?) For a Release Review, COSMOS must fulfill all of the details in this document: http://www.eclipse.org/projects/dev_process/release-review.php This is a summary of the questions that COSMOS must answer for just the Requirements, not the Guidelines.
|2.1 Features||Features themselves are in place or will be by the June deliverable.
|2.2 Non-code aspects||COSMOS is planning to ship some of the documentation in the driver and some on the web. Mark needs to check with Bjorn that this is acceptable. What about the other bullets? What do you think?|
|2.3 APIs||COSMOS needs to certify that its APIs are Eclipse Quality http://www.eclipse.org/projects/dev_process/eclipse-quality.php
This is a big one. Ali has started the process to get the Javadoc in place. Someone needs to take the to-do to check that every subproject has its API conforming to that document. Volunteers?
|2.4 Architectural issues||Does COSMOS have any architectural issues?|
|2.5 Tool usability||Explain how we made the tools usable.|
|2.6 End-of-life||No previous release.|
|2.7 Bugzilla||FYI that COSMOS will be asked about the number of defects and enhancements that are pending and how many P1 & P2 etc. are outstanding.|
(Note that they have two 2.7
|Explain the standards that COSMOS is implementing and in what state those standards are.|
|2.8 UI Usability||Summarize COSMOS' conformance to the Eclipse User Interface Guidelines: http://wiki.eclipse.org/index.php/User_Interface_Guidelines
Does COSMOS have anything that does not conform to these guidelines?
|2.9 Schedule||Did any schedule date slip in COSMOS' history?|
|2.10 Communities||Explain how COSMOS builds its three communities: http://www.eclipse.org/projects/dev_process/development_process.php#2_5_Three_Communities
COSMOS clearly has Contributors and Committers, but what Users and what Adopters does COSMOS have? We need to list them. How does COSMOS demonstrate adoption and what is the Foundation looking for?
|2.11 IP Issues||We need to get about.html and other legal documentation in place.
We need to get IPZillas opened for every prerequisite that COSMOS depends on as well as anything that COSMOS redistributes.
Did every committer count the number of lines in every contribution to confirm that they fell under the 250 line limit? Because the COSMOS Project Log doesn't list any non-committer contributions today, and that's valid only if every contribution was 250 lines or less. Plus we have to address every other bullet in this section in the Release Review documentation. Not going to list them all here.
|2.12 IP Issues speak-up-now||Out of our hands. An Eclipse Member may complain that COSMOS infringes on their IP rights.|
|2.13 Project Plan||This one is a guideline, not a requirement. If COSMOS has a draft plan for the next release we need to include it for this review.|
Option 3: Release 1.0 in June, graduate to a Mature Project
- Definition of a Mature project: http://www.eclipse.org/projects/dev_process/development_process.php#6_2_4_Mature
- guidelines and checklists for Mature projects: http://www.eclipse.org/projects/dev_process/mature-phase.php
First, COSMOS needs its two mentors, Harm Sluiman and Valentina Popescu, to vote +1 to pass a Graduation Review (http://www.eclipse.org/projects/dev_process/development_process.php#6_1_Mentors).
To achieve this, COSMOS must go through the Release Review as in Option #2 and also must go through a Graduation Review. (Why do you say this?)
|The criteria for graduating from Incubation to Mature include:
Bullet #1: any issues or questions?
Quote from the Guidelines for Incubation Phase
Section: Initial Code and Development, subsection Interim
Incubation Phrase projects may make 0.N releases (e.g., 0.2, 0.5, 0.7, ...) but may not release an N.0 or greater releases (e.g., not 1.0, 1.2, 2.0, ...). A project ready to make a 1.0 release is a project ready to graduate from Incubation. All major releases (i.e., 0.N and M.N) releases, must go through a Release Review.