Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS/COSMOS iteration i13 plan"

(→‎Bugzillas for i13 (Jimmy, Sheldon, David, Jason, Saurabh, Srinivas))
(→‎Bugzillas for i13 (Jimmy, Sheldon, David, Jason, Saurabh, Srinivas))
Line 289: Line 289:
 
<tr>
 
<tr>
 
<td></td>
 
<td></td>
−
<td><font color="red">Not containable</font></td>
+
<td></td>
 
<td>RM</td>
 
<td>RM</td>
 
<td>[http://bugs.eclipse.org/175382 175382]</td>
 
<td>[http://bugs.eclipse.org/175382 175382]</td>

Revision as of 16:15, 29 July 2008

COSMOS iteration i13 plan

Cross component work items (Jimmy Mohsin, Sheldon Lee-Loy, David Whiteman, Jason Losh)

externalization/internationalization

  • anything left to do?

security

  • anything left to do?

logging

  • anything left to do?

clean API

  • anything left to do?

Design doc every enhancement

  • if the enhancement is really small, put in at least a paragraph and a link to the use case for QA and documentation.
  • if the enhancement is not small, the design doc needs to explain the change, anyone other than the assignee who is affected, how much work it is, any ramifications, and please avoid any changes to 3rd party open source other than removing a dependency on it. Piggybacked 3rd party open source is grudgingly acceptable because we get approvals for that very quickly. It's grudging because by this stage we should know what we need and for every 3rd party plugin we still need to write its about.html and changing our dependencies means changing those files and plug-ins.

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 and other ipzillas approved by Eclipse Legal: list of IPZillas awaiting approval

COSMOS process

  • clean up the inactive committer list (done)

Other bullets necessary for a release

June 2008 options

Bugzillas for i13 (Jimmy, Sheldon, David, Jason, Saurabh, Srinivas)

Sizing legend:

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

Status to be filled in by:

  • Data Collection bugzilla status (Jimmy Mohsin)
  • Data Visualization bugzilla status (Sheldon Lee-Loy)
  • Resource Modeling bugzilla status (David Whiteman)
  • Management Enablement bugzilla status (Jason Losh)
  • RE/Build bugzilla status (Saurabh Dravid)
  • QA bugzilla status (Srinivas Reddy Doma)

The Status column can have one of these values:

  • COMPLETE
  • On track
  • At risk
  • Not containable
  • Defer (no longer a priority for i13)
  • Not started


Priority Status 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
ME 238679 normal Change code generated by MDR toolkit as a result of bug 238450 238450 ? (Decided to move to i13 on 15-Jul) Low N/A for defects N/A for defects
ME 237978 normal NPE problem when submitting a query via UI to an MDR developed with the toolkit ? (David will need to advise) Med N/A for defects N/A for defects
ME 237997 enhancement Edit manual DM toolkit test to add steps for running the MDR on server and using UI (stopgap for not doing automated - perhaps can be done by QA) ? Low N/A - all needed info in bugzilla [1]
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 ? (maybe Mark McCraw) Low N/A for defects N/A for defects
RM 179349 major Validator doesn't support baseURI in rule bindings ? Medium N/A for defects N/A for defects
RM 179350 major Validator does not support prefix matching ? Medium N/A for defects N/A for defects
RM 238492 enhancement Support xml:base in validator ? Medium New spec item, no design yet [2]
On track RM 241138 enhancement Support validating base64 encoded format Hubert Leung Medium No design yet [3]
On track RM 237872
237921		 enhancement Validator needs to support optional schema binding feature
Support PSVI in SML validation		 237921 David Whiteman and Ali Mehregani 9 PW http://wiki.eclipse.org/COSMOS_Design_237921 [4]
On track RM 238000 enhancement Implement sml:locid attribute in validator Hubert Leung High http://wiki.eclipse.org/COSMOS_Design_238000 [5]
RM 237924 enhancement Create additional test cases for the SML validator Hubert Leung High http://wiki.eclipse.org/COSMOS_Design_237924 [6]
RM 237132 major URI Reference Processing not working ? Medium N/A for defects N/A for defects
RM 175382 normal Create manual tests for the UI components of the SML-IF plugin ? Low N/A for defects N/A for defects
Retrieved from "https://wiki.eclipse.org/index.php?title=COSMOS/COSMOS_iteration_i13_plan&oldid=111785"

Back to the top