Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Cosmos Release Plan

COSMOS Wiki > COSMOS Work Items

COSMOS 1.2 Release Plan


Please send comments about this plan to the project management mailing list.

This document lays out the feature and API set for the COSMOS releases.

This plan describes the deliverables, milestones, and plan items for the COSMOS project. Each plan item covers a feature or API that is to be added to COSMOS, or some aspect of COSMOS that is to be improved. Each plan item has its own entry in the COSMOS bugzilla database, with a title and a concise summary (usually a single paragraph) that explains the work item at a suitably high level so that everyone can readily understand the work item.

Fixing bugs, improving test coverage, documentation, examples, performance tuning, usability, etc. are considered routine ongoing maintenance activities and are not included in this plan unless they would also involve a significant change to the API or feature set, or involve a significant amount of work. The intent of the plan is to account for all interesting feature work.

Release Deliverables

The following release deliverables are provided:

  • Runtime
  • Tooling
  • Source
  • Examples
  • Component Tests
  • Data Collection Implementation
  • Data Visualization Implementation
  • Resource Modeling Implementation
  • Management Enablement Implementation
  • CMDBf Implementation

Release Milestones

This COSMOS 1.2 release is targeted for general availability on June 30th 2010. All deliverables will be available for download as soon as the release has been tested and validated in the target configurations. The project will follow one month iterations consisting of three weeks for development and one week for test. There will be a total of eight iterations broken out in the release schedule below.

Milestone Duration Planned Start Date Planned End Date Actual Start Date Actual End Date Description Comments
Iteration 1 1 Month  Nov-2-2009 Nov-30-2009     Enhancements  
   Development   Nov-2-2009 Nov-23-2009     Development & bug fixes  
Testing   Nov-24-2008 Nov-30-2009     Validation Testing  
Iteration 2 1 Month  Dec-1-2009 Dec-24-2009     Enhancements  
   Development Dec-1-2009 Dec-18-2009     Development & bug fixes  
Testing   Dec-21-2009 Dec-24-2009     Validation Testing  
Iteration 3 1 Month Jan-4-2010 Jan-29-2010     Enhancements   
   Development Jan-4-2010 Jan-22-2010     Development & bug fixes  
  Testing Jan-25-2010  Jan-29-2010     Validation Testing  
Iteration 4 1 Month Feb-1-2010 Feb-26-2010     Enhancements   
   Development Feb-1-2010 Feb-19-2010     Development & bug fixes  
  Testing Feb-22-2010  Feb-26-2010     Validation Testing  
Iteration 5 1 Month Mar-1-2010 Mar-31-2010     Milestone Driver   
   Development Mar-1-2010 Mar-19-2010     Development & bug fixes  
  Testing Mar-22-2010  Mar-31-2010     Validation Testing  
Iteration 6 1 Month Apr-1-2010 Apr-30-2010     Enhancements   
   Development Apr-1-2010 Apr-23-2010     Development & bug fixes  
  Testing Apr-26-2010  Apr-30-2010     Validation Testing  
Iteration 7 1 Month May-3-2010 May-31-2010     Enhancements   
   Development May-3-2010 May-24-2010     Development & bug fixes  
  Testing May-25-2010  May-31-2010     Validation Testing  
Iteration 8 1 Month Jun-1-2010 Jun-25-2010     Release Driver  
   Development Jun-1-2010 Jun-11-2010     Development & bug fixes  
  Testing Jun-14-2010  Jun-25-2010     Validation Testing  
COSMOS 1.2 availability 1 day June-30-2010 June-30-2010     GA Release  

See 259011 for details on how those release review dates were calculated. They are tentative and may change.

Major deliverables

  • Conversion of all SDD tools to JAXB
  • SDD conformance level two implementation
  • Eclipse plug-in for SDD editing
  • Alignment with P2 for deploying non-OSGi specific applications
  • SDD generator addition to create SDDs from MSI packages


Plan items targeted for this release represent the addition of new features or areas where existing features will be significantly reworked or enhanced. Plan items are allocated to the projects indicated above.

Iteration test status

Back to the top