Difference between revisions of "COSMOS CountdownTo1.0"

Revision as of 14:10, 3 September 2008

Legal tasks remaining

• IPZilla review for DOJO 2026 (under review)
• IPZilla review for Log4J 2309 (awaiting analysis)
• about.html and other legal notices to be added to the build bugzilla 229078
• Axis2 zip file bugzilla 242766
• DOJO zip file (bugzilla to be opened)
• 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?
• schedule a meeting with Harm to see if he has any 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

Must do for 1.0

• about.html and other legal notices to be added to the build bugzilla 229078
• Axis2 zip file bugzilla 242766
• DOJO zip file (bugzilla to be opened). Will also need a bugzilla to update MDR toolkit in response to that change
• 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 215135 Run BVT
• 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

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