COSMOS 1.2 Iteration1 Features

From Eclipsepedia

Jump to: navigation, search

Contents

COSMOS v1.2 iteration 1 plan

Schedule for Iteration 1

Cosmos_Release_Plan

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:

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

Note: there are no known features in plan for iteration 1 for the Resource Modeling, Data Collection, or Data Visualization components. Resource Modeling will have several small defect fixes in the iteration.


Priority Status Project or subteam Enhancement Severity Description Blocked by (if applicable) Owner Sizing Design Doc Use Case
Medium Defer ME 294764 Enhancement Convert BTG and tooling to use JAXB classes Josh Hester Medium 294764
Medium Defer ME 294766 Enhancement Refactor tooling package names Josh Hester Low