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.
COSMOS/COSMOS iteration i12 plan
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 releasing V0.9 (Ruth Lee)
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? 220261
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. 236501
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
Bug | Severity | Description | Owner | Sizing | Design doc ready | Associated with a use case |
---|---|---|---|---|---|---|
216332 | Enhancement | Complete design for COSMOS Security - phase 2 | Paul | Medium | design doc: N/A this enh is for a design doc | use cases are listed in the document |
233690 | Enhancement | Each data manager have configuration values that can be used to identify | Hubert | Unknown until design doc finished | design doc: work in progress | use cases: no. Hubert to find the right place. |
235898 | Enhancement | Bill | ||||
212293 | Enhancement | Hubert? | no design doc yet | use cases: yes | ||
231343 | Enhancement | Handled by adding something to the broker | Hubert | Unknown | Design doc: not yet | Use cases: yes |
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
- some don't have design docs because they're such small amount of work.
- design doc to tell someone else how to implement it
- design doc so that the community knows and agrees with the change
- may be useful to put at least in paragraph form and a link to the use case. QA and documentation people will need it too so they know what to test and what to write about.
- need full design docs: all medium and high. have a design doc for 230405. 237655 working on a design doc. 237655 working on a design doc.
- 234517 might be pushed out along with 235709. Depends on additional work from enhancements from data collection.
- in addition to the sizing we need a priority column
- 236670, 236629 are bugs and don't need a design doc or use case.
- 236907 needs a design doc but it's low-medium sizing. Bill to write the design doc because he's more familiar with the requirements.
Bug | Description | Sizing | Theme | Notes |
236670 | Ability to delete queries | Low | improve function | |
236907 | Launching the COSMOS UI with a MDR query | Low | improve function | |
236629 | Create or Use Appropriate Icons for each Dilaog | Low | usability | |
230405 | Create a Report based on CMDBf information | Medium | improve function | |
237655 | Provide a reporting service group for data managers | High | improve function | |
234517 | Provide the ability to contribute custom property dialogs | Medium | usability | May remove out |
235709 | Report based on Aperi Data | Low | improve function | May remove out |
??? | Security | High | improve function |
Resource Modeling work items (David Whiteman)
Bugs/ERs to consider
Sizing legend:
- Low - takes 1-3 days
- Medium - takes a week
- High - takes more than a week
JUnit test failures (if time permits)
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
200423 | normal | Ali Mehregani | JUnit test TestSMLModelUnits.testRuleInvalidBinding failure | Low |
236866 | major | Mark McCraw? | JUnit failures when running on Sun JRE 1.5 | Low |
Spec completeness:
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
237872 | enhancement | David Whiteman | Validator needs to support optional schema binding feature | High |
237921 | enhancement | Ali Mehregani | Support PSVI in SML validation | High |
237924 | enhancement | Ali Mehregani/David Whiteman | Create additional test cases for the SML validator | Medium |
237132 | major | David Whiteman | URI Reference Processing not working | Medium |
Release readiness:
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
218814 | normal | Ali Mehregani | Reduce dependencies for SML MDR (including things that we're not legally allowed to) | Low |
213635 | normal | David Whiteman | SML-IF editor help not available from F1 (Eclipse UI guidelines conformance, will contain if possible) | Low |
Management Enablement work items (Jason Losh)
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 (release readiness, if time permits) | 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 |
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)
Large work items
Enhancements to consider
- Documenting QA activities to the wiki page
- Document what QA is doing currently for performance testing
- Adding new test cases and updating the test bucket
- Srinivas to open bugzillas for these
- Srinivas is responsible for all of these
Bug# | Severity | Description | Owner | Sizing |
---|
Web/Documentation work items (Rich Vasconi)
Themes
- Consumability
- Documentation
Enhancements To Consider
- all overview sections created for i12
Bug # | Severity | Owner | Description | Sizing |
---|---|---|---|---|
225817 | normal | Mark Weitzel | New overview of COSMOS needed on web site | Med |
218828 | enhancement | weitzelm@us.ibm.com | COSMOS User's Guide Overview development | Med |
219138 | enhancement | weitzelm@us.ibm.com | Write Overview section for COSMOS Development Guide | Med |
219156 | enhancement | Paul Stratton | Write COSMOS Installation Guide | Med |
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)