Revision as of 09:48, 20 June 2008

COSMOS iteration i12 plan

Cross component work items (Mark Weitzel)

externalization/internationalization

• how do we make sure that we keep our strings externalized? automate as part of the build? There's an ER for the build to call a utility that checks for embedded strings. Does it work for both Eclipse UI and Web UI? [1]

security

• few use cases that Paul updated recently. But for i12 we've done as much as we can do. For future iterations we need to do some planning.

logging

• there may be new log records created during i12. There were some log entries that don't conform to the naming convention and as a result the message ids were not assigned to those messages.
• SDD was looking at how to resolve their logging with the rest of COSMOS.
• message IDs to be generated
• We need a checklist for things that need to be done at the end of every iteration. For logging at least there's at least one item that needs to be done at the end of every iteration.
• Ruth to create a wiki page for the checklist; subproject leads to go over this checklist in their next meeting; community to review the final checklist at the next Community call
• Hubert created a wiki page that has a list of all of the log messages that we have. [http://wiki.eclipse.org/COSMOS_Log_Messages}

clean API

• everything done
• there's a build script to confirm that all of our packages confirm to the naming packages? Yes, Leonard did that.
• Javadoc? Public or provisional that we expect people to build on top of needs javadoc. Add "write javadoc" to the checklist.
• Plus generate it with the build. [2]

release items

• Ruth to find the old wiki page that lists the release items that we need to have done for i12

Data Collection work items (Jimmy Mohsin)

Themes

• Consumability - remove impediments to adoption
• Stability - reduce the bug backlog
• Quality - refactor as necessary to meet Eclipse API and coding conventions

Large work items

• API standards compliance and other code refactoring
• Security design

Enhancements to consider

Consumability - remove impediments to adoption

Data Visualization work items (Sheldon Lee-Loy)

Themes

• Stability - bugs that will improve the stability of the driver
• Cleanup -bugs that will help meet 1.0 release guidelines and help cleanup code
• Improve Usability - bugs that will improve existing tooling usabillity
• Improve Tooling - enhancements that will provide additional tooling to manage visualize and query MDRs
• Framework Improvements - bugs that will improve the core ui framework

Large work items

• Bugs and ERs are given a rough sizing
  • Low - takes 1-3 days
  • Medium - takes a week
  • High - takes more than a week

Resource Modeling work items (David Whiteman)

Themes

• Stability - reduce defect backlog in validator/import/export/editor
• Completeness - expanding tests to cover more nuances from spec, and fixing defects uncovered by this activity
• Documentation - integrate tooling with online documentation using contextual help

Large work items

Bugs/ERs to consider

Sizing legend:

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

JUnit test failures:

Spec completeness:

Stability:

Code cleanup:

Release readiness:

Management Enablement work items (Jason Losh)

Themes

• Consumability - producing a toolkit that significantly improves the speed & reduces the learning curve with building MDRs
• Design - finalize SDD runtime design
• Initial contributions - commit IBM/SAS code as foundation for tooling/runtime implementation
• Stability - driving out bugs and fixing them
• Testing - improving JUnits to build automated test to connect to and query MDRs built from the toolkit
• Globalization - externalizing all error messages & UI labels
• Documentation - integrate tooling with online documentation using contextual help

Large work items

• Logging
• API Cleanup (bug 229962)
• SDD runtime design finalization
• SDD runtime orchestrator
• SDD build time generator (BTG) framework

Bugs/ERs to consider

Sizing legend:

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

Consumability:

SDD Work:

Testing:

RE/Build team work items (Saurabh Dravid)

Themes

For example:

• Stability
• Globalization
• Accessibility

Large work items

For example:

• Security
• Logging

Enhancements to consider

QA work items (Srinivas Reddy Doma)

Themes

For example:

• Stability
• Globalization
• Accessibility

Large work items

• • http://wiki.eclipse.org/COSMOS_QA_i12_Activities
  • http://wiki.eclipse.org/COSMOS_QA_End2End_Tests

Enhancements to consider

Web/Documentation work items (Rich Vasconi)

Themes

• Consumability
• Documentation

Enhancements To Consider

Mandatory for releasing V0.9 (Ruth Lee)

Review itself

• arrange for COSMOS to be added to the Eclipse Board docket 5 weeks in advance of the intended release of V0.9
• Review slides: Zip of first draft of PPT During the release review we have to explain the divergences from the original plan, such as the addition of SDD.
• answer Harm's question in the review slides: How do the parts of COSMOS relate to each other? If they're disjoint then maybe that's fine and COSMOS can deliver them in disjoint packages. If they're all comingled technically then they should be packaged together. During the mini-project review (version 0.9), we want to state this and to address this question.

Legal

• about.html for third party OSS in COSMOS: Ruth to arrange for these specialized about.html to be written and then delivered to the build team for inclusion in COSMOS
• documentation of COSMOS IP
• get DOJO approved by Eclipse Legal

COSMOS process

• clean up the inactive committer list (in progress)