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
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
Design doc every enhancement?
- 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.
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)
Other bullets necessary for a release
Proposed table of bugzillas for i12
Sizing legend:
- Low - takes 1-3 days
- Medium - takes a week
- High - takes more than a week
Priority | 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 | ||||
Build | 229078 | Blocker | Add about.html and other legal files to the build | Ruth Lee | Medium | N/A for defects | N/A for defects | ||
DC and ME | 216332 | enhancement | Complete design for COSMOS Security - phase 2 | Jimmy Mohsin | High | [1] | |||
ME | 220594 | enhancement | Provide contextual help for toolkit UI (release readiness, if time permits) | David Whiteman | Low | ||||
ME | 229088 | enhancement | Create initial SDD runtime framework for COSMOS installation | Jason Losh | High | ||||
ME | 229962 | enhancement | API cleanup | Jason Losh | |||||
ME | enhancement | SDD runtime design finalization | Jason Losh | ||||||
ME | enhancement | SDD runtime orchestrator | Jason Losh | ||||||
ME | enhancement | SDD build time generator (BTG) framework | Jason Losh | ||||||
RM | 200423 | normal | JUnit test TestSMLModelUnits.testRuleInvalidBinding failure | Ali Mehregani | Low | N/A for defects | N/A for defects | ||
RM | 236866 | major | JUnit failures when running on Sun JRE 1.5 | Mark McCraw? | Low | N/A for defects | N/A for defects | ||
RM | 237872 | enhancement | Validator needs to support optional schema binding feature | David Whiteman | High | ||||
RM | 237921 | enhancement | Support PSVI in SML validation | Ali Mehregani | High | ||||
RM | 237924 | enhancement | Create additional test cases for the SML validator | Ali Mehregani/David Whiteman | Medium | ||||
RM | 237132 | major | URI Reference Processing not working | David Whiteman | Medium | N/A for defects | N/A for defects | ||
RM | 218814 | normal | Reduce dependencies for SML MDR (including things that we're not legally allowed to) | Ali Mehregani | Low | N/A for defects | N/A for defects | ||
RM | 213635 | normal | SML-IF editor help not available from F1 (Eclipse UI guidelines conformance, will contain if possible) | David Whiteman | Low | N/A for defects | N/A for defects | ||
DV | [http://bugs.eclipse.org/236670 236670 | normal | Ability to delete queries | Sheldon | Low | N/A for defects | N/A for defects | ||
DV | [http://bugs.eclipse.org/236907 236907 | enhancement | Launching the COSMOS UI with a MDR query | Bill | Low | [2] | |||
DV | [http://bugs.eclipse.org/236629 236629 | normal | Create or Use Appropriate Icons for each Dilaog | Martin | Low | N/A for defects | N/A for defects | ||
DV | [http://bugs.eclipse.org/230405 230405 | enhancement | Create a Report based on CMDBf information | Sheldon | Medium | [3] | |||
DV | [http://bugs.eclipse.org/237655 237655 | enhancement | Provide a reporting service group for data managers | Sheldon | High | ||||
DV | [http://bugs.eclipse.org/234517 234517 | enhancement | Provide the ability to contribute custom property dialogs | May move out due to unknown amount of Security work | Sheldon | Medium | |||
DV | [http://bugs.eclipse.org/235709 235709 | enhancement | Report based on Aperi Data | May move out due to unknown amount of Security work | Sheldon | Low | |||
DV | ??? | enhancement | Security | Sheldon | High | ||||
DC | 216332 | Enhancement | Complete design for COSMOS Security - phase 2 | Paul | Medium | N/A this enh is for a design doc | use cases are listed in the document | ||
DC | 233690 | Enhancement | Each data manager have configuration values that can be used to identify | Hubert | Unknown until design doc finished | use cases: no. Hubert to find the right place. | |||
DC | 235898 | Enhancement | Bill | ||||||
DC | 212293 | Enhancement | Hubert? | use cases: yes | |||||
DC | 231343 | Enhancement | Handled by adding something to the broker | Hubert | Unknown | Use cases: yes | |||
Doc | 225817 | normal | New overview of COSMOS needed on web site | Mark Weitzel | Med | N/A for defects | N/A for defects | ||
Doc | 218828 | enhancement | COSMOS User's Guide Overview development | weitzelm@us.ibm.com | Med | [4] | N/A for documentation | ||
Doc | 219138 | enhancement | Write Overview section for COSMOS Development Guide | weitzelm@us.ibm.com | Med | [5] | N/A for documentation | ||
Doc | 219156 | enhancement | Write COSMOS Installation Guide | Paul Stratton | Med | http://wiki.eclipse.org/COSMOS_InstallGuide10 | N/A for documentation | ||
QA | ??? | enhancement | Documenting QA activities to the wiki page | Srinivas | N/A for documentation | N/A for documentation | |||
QA | ??? | enhancement | Document what QA is doing currently for performance testing | Srinivas | N/A for documentation | N/A for documentation | |||
QA | ??? | enhancement | Adding new test cases and updating the test bucket | Srinivas | N/A for documentation | N/A for documentation |