Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Cosmos Release Plan 1.1

COSMOS 1.1 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.1 is targeted for general availability on 25-September-2009. All deliverables will be available for download as soon as the release has been tested and validated in the target configurations. There is an allocation of resource to defect removal in all iterations. The first Iterations 1-2 will contain the bulk of the enhancement work, with Iteration 3 stabilizing the milestone driver, with Iterations 4, 5 and 6 will be devoted to fleshing out the framework, and Iteration 7 will mainly be used to stabilize and shut down the release. There is a one week buffer after I7 to the GA date in order to plan and prep for the release review.

Milestone Duration Planned Start Date Planned End Date Actual Start Date Actual End Date Description Comments
Iteration 1 8 weeks Nov-17-2008 Jan-09-2009     Enhancements  
   i1 Development 5 weeks Nov-17-2008 Dec-17-2008     Development & bug fixes  
i1 Testing 3 weeks Dec-22-2008 Jan-09-2009     Validation Testing  
Iteration 2 6 weeks Jan-12-2009 Feb-20-2009     Enhancements  
   i2 Development 4 weeks Jan-12-2009 Feb-04-2009     Development & bug fixes  
i2 Testing 2 weeks Feb-09-2009 Feb-20-2009     Validation Testing  
Iteration 3 8 weeks Feb-23-3009 Apr-03-2009     Stabilize  
   i3 Development 4 weeks Feb-23-2009 Mar-18-2009     Development & bug fixes  
   i3 shutdown phase 2 weeks Mar-19-2009 Apr-01-2009     Approved changes only: documentation, examples, defects that stabilize the driver, write new tests. Before checking in anything, a project lead must review and approve that change.  
  i3 Testing 2 weeks Apr-06-2009 Apr-17-2009     Validation Testing  
Milestone driver 1 day Apr-17-2009 Apr-17-2009     Available for POCs  
Iteration 4 4 weeks Apr-20-2009 May-15-2009    


   i4 Development 2 weeks Apr-20-2009 Apr-29-2009     Development & bug fixes  
i4 Testing 2 weeks May-04-2009 May-15-2009     Validation Testing  
Iteration 5 6 weeks May-18-2009 June-26-2009    


   i5 Development 4 weeks May-18-2009 June-10-2009     Development & bug fixes  
i5 Testing 2 weeks June-15-2009 June-26-2009     Validation Testing  
Iteration 6 6 weeks June-29-2009 August-7-2009    


  • July 31st: email inactive committers, give them a week to respond
  • July 31st: start the release review slides
  • July 31st: ask the Technology PMC for permission to release COSMOS v1.1
  • August 3rd: submit the IP log to Eclipse Legal. No change that would affect the IP log or about.html files are allowed after the log is submitted to Eclipse Legal.
  • August 7th: any inactive committers who responded, make the appropriate changes
  • August 7th: complete first draft of the release review slides
   i6 Development 4 weeks June-29-2009 July-24-2009     Development & bug fixes  
i6 Testing 2 weeks July-27-2009 August-7-2009     Validation Testing  
Iteration 7 6 weeks August-10-2009 September-18-2009    


  • August 14th: complete the inactive committers cleanup
  • August 14th: complete the release review slides
  • August 17th: submit the release review slides to the EMO
  • August 31st: hold the release review for COSMOS v1.1
   i7 Development 4 weeks August-10-2009 September-4-2009     Development & bug fixes  
i7 Testing 2 weeks September-7-2009 September-18-2009     Validation Testing  
COSMOS 1.1 availability 1 day September-25-2009 September-25-2009     GA Release  

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

Major deliverables

  • SML bug fixes
  • reconciliation taxonomy
  • finish the SDD tooling for the BTG
  • have our SDD runtime driver for conformance level 1
  • stabilize CMDBf support
  • move SML out of research
  • move SDD out of research


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.

Milestone 1 Objectives (i1 - i3)

GA Objectives (i4 - i7)

Copyright © Eclipse Foundation, Inc. All Rights Reserved.