COSMOS CountdownTo1.0

Countdown schedule

• Starting in i14, we will track weekly status on the Countdown page
  • by Sept 12, any inactive committers will resign their committer status
  • by Sept 12, Ruth to find new mentors for COSMOS (not sure how realistic this is, but let's start with this date)
  • by Sept 26, Ruth to schedule the release review for COSMOS with the Eclipse EMO. Ask for Oct 10.
  • by Oct 10, everyone to try and resolve any Eclipse Legal outstanding items for DOJO and log4j and axis2
  • by Oct 10, attend the release review to request permission to release COSMOS 1.0 and to graduate COSMOS into a mature project

Legal tasks remaining

• about.html and other legal notices to be added to the build bugzilla 229078
• Axis2 zip file bugzilla 242766
• DOJO zip file bugzilla 246855
• complete the project IP log

Release review tasks remaining

• finish the slides Tania's COSMOS 1.0 Release Review draft slides
• schedule a meeting with Bjorn to inform him of updates (cancel 0.9, staffing) and ask what are his recommendations given that we had to cancel 0.9 due to legal clearance issues. Can we run through a practice run with the Eclipse board (or maybe even just Bjorn and Harm) before going for the Big 1.0 Review?
• find new project mentor (Harm leaving board)
• schedule a meeting with new mentor to see if there are new concerns
• book the review itself with Anne Jacko five weeks in advance of the hoped
• ask Bjorn how the review works; i.e., Anne reviews the slides & tells if there's a big problem, team presents to the board and has the five weeks to correct before GA?

Technical and documentation items remaining

Doc ownership

• Jimmy to own User Guide
• Paul to own Install Guide
• David and Jack to own the Developer Guide
• Javadoc still needs to be written but that's in the code itself and is owned by development

Sizing legend and Status column

Sizing legend:

• Low - takes 1-3 days
• Medium - takes a week
• High - takes more than a week

The Status column can have one of these values:

• COMPLETE
• On track
• At risk
• Not containable
• Defer (no longer a priority for COSMOS 1.0)
• Not started

Must do for 1.0

Priority	Status	Project or subteam	Enhancement	Severity	Description	Blocked by (if applicable)	Owner	Sizing	Design Doc	Use Case
		Build	215609	Normal	Maintain documentation of third party dependencies		Ruth Lee	Low	N/A for defects	N/A for defects
		Build	215135	Enhancement	Establish a process for running JUnits against a COSMOS build		Bobby Joseph	High

• about.html and other legal notices to be added to the build bugzilla 229078
• Axis2 zip file bugzilla 242766
• DOJO zip file bugzilla 246855
• bugzilla 246868 update MDR toolkit in response to that change (246855)
• bugzilla 216210 Define & document COSMOS 1.0 hardware & software operational guidelines, recommendations, and best practices
• bugzilla 240382 Update install guide for new version of Dojo
• bugzilla 218825 COSMOS User's Guide development
• bugzilla 245568 Cannot open staff query folder
• Update User Guide and Developer Guide with changes due to changed code and package names, or any other updates required
• Add missing sections to User Guide and Developer Guide
• release notes need to be created for known critical issues
• bugzilla 247658 MDR Toolkit : Problem with DataManager Name

Recommended for 1.0 but can be dropped if necessary

• bugzilla 220594 Release readiness: contextual help

SML: In Research items

COSMOS 1.0 will contain an SML-IF document editor and utilities to validate SML-IF documents. The SML code will not have cleared the Eclipse Legal process required to validate the IP cleanliness of external dependencies, e.g. XSD files, by the 1.0 release and therefore, will be given the designation "In Research". The implication of this is that this portion of the code will not be forced to comply with the release readiness requirements of COSMOS.

• IPZilla review for SML schema and SML-IF schema files 2240 (awaiting analysis - checkin due to parallel IP)
• IPZilla review for Schematron skeleton 2584 (awaiting analysis - checkin due to parallel IP)
• documentation will not be guaranteed to be complete by 1.0

SDD: In Research items

The COSMOS 1.0 deliverable will be a validation utility for SDD documents and a corresponding programmatic interface. The SDD code will not have cleared the Eclipse Legal process by the 1.0 release and therefore, will be given the designation "In Research". The implication of this is that this portion of the code will not be forced to comply with the release readiness requirements of COSMOS.

• IPZilla review for SDD Change Analyzer 2316 (awaiting committer)
• IPZilla review for Schematron skeleton 2472 (awaiting analysis)
• IPZilla review for Schematron text implementation 2473 (awaiting analysis)

Actions that COSMOS will do to prepare for the release review

• cancel any bugzillas that we will not complete by COSMOS 1.0 or the first release after COSMOS 1.0. (This is to cull the list of any "noise" (abandoned bugzillas). If someone wants to reopen it then fine. We should put the list of bugzillas here.)
  • WSDM, OSGi, CBE, and other deprecated code to be wontfix
  • everything else that cannot be contained in 1.0 to be future
  • use i14 for anything not committed to 1.0 but in consideration for 1.0. Should also be in the bugzilla list on this page.
• clean up the committer list of any inactive committers (need to check with Bjorn to see what he thinks about retaining committer status for the IBMers who may be back in 2009)

Resources

• Some more details involved in what needs to be covered at the Release Review and Graduation Review

Active or inactive? post to read

• Docs

Completed

• bugzilla 215135 Run BVT
• reassign any ownership in bugzilla to the new component owner
• IPZilla review for DOJO 2026
• IPZilla review for Log4J 2309