Skip to main content
Jump to: navigation, search

Difference between revisions of "COSMOS 1.1 Iteration4 Features"

(Use cases)
(Bugzillas for this iteration (Jimmy, David, Jason, Saurabh, QA, Doc, Ruth))
Line 8: Line 8:
 
* 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 in general <b>please avoid any changes to 3rd party materials other than removing a dependency on it</b>. We have no guarantee that the change will be approved for COSMOS v1.1.
 
* 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 in general <b>please avoid any changes to 3rd party materials other than removing a dependency on it</b>. We have no guarantee that the change will be approved for COSMOS v1.1.
  
== Bugzillas for this iteration (Jimmy, David, Jason, Saurabh, QA, Doc, Ruth) ==
+
== Bugzillas for this iteration (Jimmy, David, Jason, Saurabh, QA, Doc) ==
  
 
Sizing legend:
 
Sizing legend:
Line 25: Line 25:
 
* QA bugzilla status ('''No owner''')
 
* QA bugzilla status ('''No owner''')
 
* Doc bugzilla status ('''No owner''')
 
* Doc bugzilla status ('''No owner''')
* Legal & release review prep and status ('''Ruth Lee''')
+
* Legal & release review prep and status ('''Jason Losh''')
  
 
The Status column can have one of these values:  
 
The Status column can have one of these values:  
Line 59: Line 59:
 
<td>Update the IP log and about.html in v1.1 iteration 4</td>
 
<td>Update the IP log and about.html in v1.1 iteration 4</td>
 
<td></td>
 
<td></td>
<td>Ruth Lee</td>
+
<td>Jason Losh</td>
 
<td>N/A</td>
 
<td>N/A</td>
 
<td>N/A</td>
 
<td>N/A</td>
Line 73: Line 73:
 
<td>Prep for the V1.1 release (part 1)</td>
 
<td>Prep for the V1.1 release (part 1)</td>
 
<td></td>
 
<td></td>
<td>Ruth Lee</td>
+
<td>Jason Losh</td>
 +
<td>N/A</td>
 +
<td>N/A</td>
 +
<td>N/A</td>
 +
</tr>
 +
 
 +
<tr>
 +
<td>P3</td>
 +
<td>Not started</td>
 +
<td>RM</td>
 +
<td>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=270836 270836]</td>
 +
<td>Normal</td>
 +
<td>Update RTx name to FRC</td>
 +
<td></td>
 +
<td>Mark Johnson</td>
 
<td>N/A</td>
 
<td>N/A</td>
 
<td>N/A</td>
 
<td>N/A</td>

Revision as of 13:10, 1 April 2009

COSMOS v1.1 iteration 4 plan

Schedule for Iteration 4

Schedule for Iteration 4

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 in general please avoid any changes to 3rd party materials other than removing a dependency on it. We have no guarantee that the change will be approved for COSMOS v1.1.

Bugzillas for this iteration (Jimmy, David, Jason, Saurabh, QA, Doc)

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 (Jimmy Mohsin)
  • Resource Modeling bugzilla status (David Whiteman)
  • Management Enablement bugzilla status (Jason Losh)
  • RE/Build bugzilla status (Saurabh Dravid)
  • QA bugzilla status (No owner)
  • Doc bugzilla status (No owner)
  • Legal & release review prep and status (Jason Losh)

The Status column can have one of these values:

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


Priority Status Project or subteam Enhancement Severity Description Blocked by (if applicable) Owner Sizing Design Doc Use Case
Medium On track All 259004 Defect Update the IP log and about.html in v1.1 iteration 4 Jason Losh N/A N/A N/A
P1 All 259105 Normal Prep for the V1.1 release (part 1) Jason Losh N/A N/A N/A
P3 Not started RM 270836 Normal Update RTx name to FRC Mark Johnson N/A N/A N/A

Use cases

Back to the top