Skip to main content
Jump to: navigation, search

COSMOS 1.2 Iteration3 Features

COSMOS v1.2 iteration 3 plan

Schedule for Iteration 3


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.2.

Bugzillas for this iteration

Sizing legend:

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

Status to be filled in by:

  • Management Enablement bugzilla status (Jason Losh)
  • RE/Build bugzilla status (Brad Beck)
  • QA bugzilla status (SAS)
  • Doc bugzilla status (No owner)
  • Legal & release review prep and status (Jason Losh)

The Status column can have one of these values:

  • 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 ME Enhancement Design/document SDD runtime interaction/integration with P2 Jeff Hamm High 300044
Medium COMPLETE ME 299382 Enhancement Implement simple registry to store resulting resource/change information Josh Hester High 299382

Back to the top