Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS/COSMOS iteration i12 plan"
(→Large work items) |
(→Web/Documentation work items (Rich Vasconi)) |
||
Line 332: | Line 332: | ||
===Enhancements to consider=== | ===Enhancements to consider=== | ||
− | + | ===User's Guide and Development Guide Documentation Status for i11=== | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
<table border="1" cellpadding="1"> | <table border="1" cellpadding="1"> | ||
<tr> | <tr> | ||
− | + | <th>Enhancement</th> | |
<th>Severity</th> | <th>Severity</th> | ||
<th>Owner</th> | <th>Owner</th> | ||
Line 366: | Line 341: | ||
<th>Sizing</th> | <th>Sizing</th> | ||
</tr> | </tr> | ||
− | <tr> | + | <tr> |
− | <td>[http://bugs.eclipse.org/216655 216655]</td> | + | <td><font color="orange">At risk</font></td> |
+ | <td>[http://bugs.eclipse.org/216655 216655]</td> | ||
<td>enhancement</td> | <td>enhancement</td> | ||
<td>vasconi@us.ibm.com</td> | <td>vasconi@us.ibm.com</td> | ||
− | <td>Include Javadoc in online Eclipse help</td> | + | <td>Include Javadoc in online Eclipse help. Should this be moved to future?</td> |
− | <td> | + | <td>High |
</td> | </td> | ||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>[http://bugs.eclipse.org/218828 218828]</td> | |
<td>enhancement</td> | <td>enhancement</td> | ||
<td>weitzelm@us.ibm.com</td> | <td>weitzelm@us.ibm.com</td> | ||
− | <td>COSMOS User's Guide | + | <td>COSMOS User's Guide Overview development</td> |
− | <td> | + | <td>High |
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>[http://bugs.eclipse.org/218830 218830]</td> | |
<td>enhancement</td> | <td>enhancement</td> | ||
<td>weitzelm@us.ibm.com</td> | <td>weitzelm@us.ibm.com</td> | ||
<td>Write COSMOS User's Guide Prerequisites</td> | <td>Write COSMOS User's Guide Prerequisites</td> | ||
− | <td> | + | <td>High |
</td> | </td> | ||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | ||
+ | <td>[http://bugs.eclipse.org/219117 219117]</td> | ||
<td>enhancement</td> | <td>enhancement</td> | ||
<td>jason.losh@sas.com</td> | <td>jason.losh@sas.com</td> | ||
<td>Write Solution Deployment Descriptor (SDD) section for COSOMS User's Guide</td> | <td>Write Solution Deployment Descriptor (SDD) section for COSOMS User's Guide</td> | ||
− | <td> | + | <td>High |
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>[http://bugs.eclipse.org/219120 219120]</td> | |
<td>enhancement</td> | <td>enhancement</td> | ||
<td>hkyleung@ca.ibm.com</td> | <td>hkyleung@ca.ibm.com</td> | ||
<td>Write Running the Example section for the COSMOS User's Guide</td> | <td>Write Running the Example section for the COSMOS User's Guide</td> | ||
− | <td> | + | <td>High |
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>[http://bugs.eclipse.org/219138 219138]</td> | |
<td>enhancement</td> | <td>enhancement</td> | ||
<td>weitzelm@us.ibm.com</td> | <td>weitzelm@us.ibm.com</td> | ||
<td>Write Overview section for COSMOS Development Guide</td> | <td>Write Overview section for COSMOS Development Guide</td> | ||
− | <td> | + | <td>High |
</td> | </td> | ||
</tr> | </tr> | ||
+ | </tr> | ||
+ | |||
+ | </tr> | ||
+ | |||
<tr> | <tr> | ||
− | <td>[http://bugs.eclipse.org/ | + | <td>[http://bugs.eclipse.org/223084 223084]</td> |
<td>enhancement</td> | <td>enhancement</td> | ||
− | <td> | + | <td>Mark Weitzel</td> |
− | <td>Write | + | <td>Write COSMOS Restrictions section for User's Guide</td> |
− | <td> | + | <td>High |
</td> | </td> | ||
</tr> | </tr> | ||
+ | |||
+ | </table> | ||
+ | |||
+ | ===Future Document Enhancements=== | ||
+ | <TABLE BORDER="1"> | ||
+ | <tr> | ||
+ | <th>Bug #</th> | ||
+ | <th>Severity</th> | ||
+ | <th>Owner</th> | ||
+ | <th>Description</th> | ||
+ | <th>Sizing</th> | ||
+ | </tr> | ||
<tr> | <tr> | ||
− | <td>[http://bugs.eclipse.org/ | + | <td>[http://bugs.eclipse.org/219130 219130]</td> |
<td>enhancement</td> | <td>enhancement</td> | ||
− | <td> | + | <td>Mark Weitzel</td> |
− | <td> | + | <td>Approve COSMOS Development Guide for GA</td> |
− | <td> | + | <td>Future |
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>[http://bugs.eclipse.org/ | + | <td>[http://bugs.eclipse.org/219144 219144]</td> |
<td>enhancement</td> | <td>enhancement</td> | ||
− | <td> | + | <td>Joel Hawkins</td> |
− | <td>Write | + | <td>Write Management Enablement section in COSMOS Development Guide</td> |
− | <td> | + | <td>Future |
</td> | </td> | ||
</tr> | </tr> | ||
Line 471: | Line 448: | ||
<td>Write the WSDM Tooling section in COSMOS Development Guide</td> | <td>Write the WSDM Tooling section in COSMOS Development Guide</td> | ||
− | <td> | + | <td>Future |
+ | <tr> | ||
+ | <td>[http://bugs.eclipse.org/219154 219154]</td> | ||
+ | <td>enhancement</td> | ||
+ | <td>Jimmy Mohsin</td> | ||
+ | <td>Write Internationalization section in COSMOS Development Guide</td> | ||
+ | |||
+ | <td>Future | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 480: | Line 464: | ||
<td>Write COSMOS Installation Guide</td> | <td>Write COSMOS Installation Guide</td> | ||
− | <td> | + | <td>Future |
</td> | </td> | ||
</tr> | </tr> | ||
+ | <tr> | ||
+ | <td>[http://bugs.eclipse.org/225817 225817]</td> | ||
+ | <td>normal</td> | ||
+ | <td>Mark Weitzel</td> | ||
+ | <td>New overview of COSMOS needed on web site</td> | ||
+ | <td>Future</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>[http://bugs.eclipse.org/235398 235398]</td> | ||
+ | <td>normal</td> | ||
+ | <td>Rich Vasconi</td> | ||
+ | <td>Update COSMOS Team Committers page</td> | ||
+ | <td>Future</td> | ||
+ | </tr> | ||
</table> | </table> | ||
Revision as of 12:25, 4 June 2008
Contents
- 1 COSMOS iteration i12 plan
- 1.1 Cross component work items (Mark Weitzel)
- 1.2 externalization/internationalization
- 1.3 security
- 1.4 logging
- 1.5 clean API
- 1.6 release items
- 1.7 Data Collection work items (Jimmy Mohsin)
- 1.8 Data Visualization work items (Sheldon Lee-Loy)
- 1.9 Resource Modeling work items (David Whiteman)
- 1.10 Management Enablement work items (Jason Losh)
- 1.11 RE/Build team work items (Saurabh Dravid)
- 1.12 QA work items (Srinivas Reddy Doma)
- 1.13 Web/Documentation work items (Rich Vasconi)
- 1.14 Mandatory for graduation (Ruth Lee/Tania Makins)
COSMOS iteration i12 plan
Cross component work items (Mark Weitzel)
externalization/internationalization
security
logging
clean API
release items
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
Bug | Severity | Description | Owner | Sizing |
---|---|---|---|---|
216332 | Enhancement | Complete design for COSMOS Security - phase 2 | Jimmy | Medium |
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
Improve Usability - bugs that will improve existing tooling usabillity
Bug | Severity | Description | Owner | Sizing |
---|---|---|---|---|
222709 (new) | normal | QueryBuilder should populate the MdrID | sleeloy@ca.ibm.com | Low |
224169 (Need to upgrade to Dojo 1.1) | enhancement | Ability to resize dialog box. | martin.simmonds@ca.com | Medium |
223241 (Need to upgrade to Dojo 1.1) | enhancement | Full screen mode toolbar button | sleeloy@ca.ibm.com | Medium |
229083 (future?) | enhancement | Predefined queries with parameters | sleeloy@ca.ibm.com | Low |
Improve Tooling - enhancements that will provide additional tooling to manage visualize and query MDRs
Bug | Severity | Description | Owner | Sizing |
---|---|---|---|---|
230405 (future?) | Create a Report based on CMDBf information | sleeloy@ca.ibm.com | Medium | |
222504 (future?) | enhancement | UI cannot show the query request | sleeloy@ca.ibm.com | Medium |
211093 (future?) | enhancement | Custom visualization for example MDR | sleeloy@ca.ibm.com | Medium |
Framework Improvements - bugs that will improve the core ui framework
Bug | Severity | Description | Owner | Sizing |
---|---|---|---|---|
229411 (legal?) | enhancement | Upgrade to Dojo 1.1 | sleeloy@ca.ibm.com | Medium-High |
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:
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
228223 | major | Ali Mehregani | Data center sample validation errors - TestPluginMainValidator failures | Low-Medium |
200423 | normal | Dlwhiteman.us.ibm.com | JUnit test TestSMLModelUnits.testRuleInvalidBinding failure | Low |
Spec completeness:
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
229890 | major | Ali Mehregani | Locating SML documents remotely | Low |
Stability:
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
221409 | major | Dlwhiteman.us.ibm.com | Identifying definition content type fails when WTP is installed | Low |
185391 | major | Dlwhiteman.us.ibm.com | Export SMLIF wizard > ruleBindings page shows no documents | Low |
Code cleanup:
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
218814 | normal | Ali Mehregani | Reduce dependencies for SML MDR | Low |
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:
Bug # | Severity | Description | Owner | Sizing |
---|---|---|---|---|
216332 | enhancement | Complete design for COSMOS Security - phase 2 | Jimmy Mohsin | High |
220594 | enhancement | Provide contextual help for toolkit UI | Dlwhiteman.us.ibm.com | Low |
SDD Work:
Bug | Severity | Description | Owner | Sizing |
---|---|---|---|---|
229088 | enhancement | Create initial SDD runtime framework for COSMOS installation | Jason Losh | High |
Testing:
Bug # | Severity | Description | Owner | Sizing |
---|---|---|---|---|
230282 | enhancement | Create JUnit test for running & querying projects built from toolkit | Dlwhiteman.us.ibm.com | Medium |
RE/Build team work items (Saurabh Dravid)
Themes
For example:
- Stability
- Globalization
- Accessibility
Large work items
For example:
- Security
- Logging
Enhancements to consider
Enhancement | Severity | Description | Blocked by (if applicable) | Owner | Sizing |
---|---|---|---|---|---|
215609 | Normal | Maintain documentation of third party dependencies | Ruth Lee | Low | |
215135 | Enhancement | Establish a process for running JUnits against a COSMOS build | Bobby Joseph | High | |
229078 | Blocker | Add about.html and other legal files to the build | Ruth Lee | Medium |
QA work items (Srinivas Reddy Doma)
Themes
For example:
- Stability
- Globalization
- Accessibility
Large work items
Enhancements to consider
Bug# | Severity | Description | Owner | Sizing |
---|
Web/Documentation work items (Rich Vasconi)
Themes
- Consumability
- Documentation
Enhancements to consider
User's Guide and Development Guide Documentation Status for i11
Enhancement | Severity | Owner | Description | Sizing | |
---|---|---|---|---|---|
At risk | 216655 | enhancement | vasconi@us.ibm.com | Include Javadoc in online Eclipse help. Should this be moved to future? | High |
218828 | enhancement | weitzelm@us.ibm.com | COSMOS User's Guide Overview development | High | |
218830 | enhancement | weitzelm@us.ibm.com | Write COSMOS User's Guide Prerequisites | High | |
219117 | enhancement | jason.losh@sas.com | Write Solution Deployment Descriptor (SDD) section for COSOMS User's Guide | High | |
219120 | enhancement | hkyleung@ca.ibm.com | Write Running the Example section for the COSMOS User's Guide | High | |
219138 | enhancement | weitzelm@us.ibm.com | Write Overview section for COSMOS Development Guide | High | |
223084 | enhancement | Mark Weitzel | Write COSMOS Restrictions section for User's Guide | High |
Future Document Enhancements
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
219130 | enhancement | Mark Weitzel | Approve COSMOS Development Guide for GA | Future |
219144 | enhancement | Joel Hawkins | Write Management Enablement section in COSMOS Development Guide | Future |
219148 | enhancement | bsubram@us.ibm.com | Write the WSDM Tooling section in COSMOS Development Guide | Future |
219154 | enhancement | Jimmy Mohsin | Write Internationalization section in COSMOS Development Guide | Future |
219156 | enhancement | jim@gyng.com | Write COSMOS Installation Guide | Future |
225817 | normal | Mark Weitzel | New overview of COSMOS needed on web site | Future |
235398 | normal | Rich Vasconi | Update COSMOS Team Committers page | Future |
Mandatory for graduation (Ruth Lee/Tania Makins)
We had a meeting with Bjorn and another meeting with Harm to cover the known questions. Before I get into those answers, generally speaking there are few inviolates. As long as you have a story you can, for example, release an English-only COSMOS even though there is an Eclipse pervasive theme of globalization.
It boils down to what the COSMOS adopters need. Whatever the adopters need we should provide and any discussions about those requirements need to be done in the open in order to be open and transparent to Eclipse.
Bjorn recommended the following:
- That we release a version 0.5 before we release a 1.0 to give us practice going through a release review before the Big Release Review.
- The we clean up our inactive committer list.
Mandatory for graduation:
- Legal (about.html, IP log, all IP Zillas approved, etc.)
- I am concerned that we don't have permission from Eclipse Legal to use DOJO yet. For details read https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2026. (For those of you who can't read it because you aren't committers, the quote is,
"Because we identified license and pedigree concerns in the previous version, further investigation is required before we can determine whether the code can be checked into CVS/SVN. We will not be able to grant parallel IP at this time, however we will keep you informed of our progress.
Auto-Generated Text: This submission is now awaiting analysis." I (Ruth) believe that Parallel IP also includes prereqs, but have not yet checked with Eclipse Legal to confirm. - We need to open an IPZilla for our prereq of BIRT. (This is as per an email sent to Sheldon and myself responding to my question asking same.)
- Any changes, such as changing a prereq to a redistribute, changing a version number, using something from Orbit, etc. cannot be done silently or directly to the build team. Please check with Mark Weitzel for an architectural review first, and then he'll tell you the next steps to take. (Note that Bjorn did not tell us this item: this came out of a variety of sources, including a meeting with our mentor who suggested that before a legal review is done that an architectural review is necessary, and that every adopter of COSMOS should be consulted to ensure that the 3rd party open source will not inhibit their adoption of COSMOS due to either legal or technical reasons.)
- I am concerned that we don't have permission from Eclipse Legal to use DOJO yet. For details read https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2026. (For those of you who can't read it because you aren't committers, the quote is,
The questions that we asked Bjorn:
- How much public API do we need to release?
- What support will we be required to provide?
- How many adopters do we need? How do we need to demonstrate adoption?
- How should we handle the changes to the project roadmap? For example, at Project creation time, SDD was not explicitly in plan.
- When COSMOS graduates into a Mature project, what project should it graduate into?
Bjorn's answers:
- (Mark, please correct me if I misstate this.) It depends on what your adopters need. As long as you can demonstrate adoption, then you can release using provisional API if your adopters are happy with that.
- Whatever you, as a project, decide to do. The only requirement is that you make that guarantee/claim in public as part of the release. (Harm commented that we should consult the adopters to see what they need.)
- Three would be wonderful, two would be good, one would be ok/iffy (because then it looks like a single company project), zero would be bad. It is okay to demonstrate adoption without the mailing list or newsgroup; that is, public questions/comments on those venues are not required.
- During your 0.5 Release Review explain the new roadmap & project structure.
- It's a myth that it has to leave Technology. You can do so if you wish, and if you do then typically projects move to Tools. (Note that Harm recommended the Technology project instead of the Tools project.)
Harm commented:
- 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.5), we want to state this and to address this question.
- When releasing a 1.0, that implies that you need to maintain the API until a 2.0 release. He recommended that we use package provisional on any code where the specification has not finalized because if the specification changes significantly then we will be forced to break API out of cycle, and that's bad.