Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Cosmos Release Plan"

m (Features)
(Iteration test status)
 
(92 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
[[COSMOS|COSMOS Wiki]] >  [[COSMOS_Work_Items|COSMOS Work Items]]  
 
[[COSMOS|COSMOS Wiki]] >  [[COSMOS_Work_Items|COSMOS Work Items]]  
  
== COSMOS Release Plan Version 1.0.0==
+
= COSMOS 1.2 Release Plan =
  
 +
== Overview  ==
  
=== Community Systems Management Open Source (COSMOS) 1.0 Project Plan (Draft) ===
+
Please send comments about this plan to the [mailto:cosmos-mgmt@eclipse.org cosmos-mgmt@eclipse.org] project management mailing list.  
  
Please send comments about this plan to the [mailto:cosmos-mgmt@eclipse.org cosmos-mgmt@eclipse.org] project management mailing list.
+
<br>This document lays out the feature and API set for the COSMOS releases.  
  
 +
*[[#Release_Deliverables|Release Deliverables]]
 +
*[[#Release_Milestones|Release Milestones]]
 +
*[[#Project_Designs|Project Designs]]
 +
*[[#Features|Features]]
  
This document lays out the feature and API set for the COSMOS 1.0 release.                                     
+
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.  
* [[#Release Deliverables]]
+
<div style="border-right: blue 1px solid; padding-right: 20px; border-top: blue 1px solid; padding-left: 20px; padding-bottom: 20px; margin: 10px; border-left: blue 1px solid; padding-top: 20px; border-bottom: blue 1px solid; background-color: #e0e0ff">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.</div>
* [[#Release Milestones]]
+
== Release Deliverables ==
* [[#Project Designs]]
+
* [[#Features]]
+
* [[#Defects]]
+
 
+
This plan describes the release deliverables, release milestones, and the plan items for the four projects under COSMOS. 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:  
 
The following release deliverables are provided:  
* Runtime
 
* Source
 
* Examples
 
* Component Tests
 
* Data Collection Implementation
 
* Data Visualization Implementation
 
* Resource Modeling Implementation
 
  
==== Release Milestones ====
+
*Runtime
 +
*Tooling
 +
*Source
 +
*Examples
 +
*Component Tests
 +
*Data Collection Implementation
 +
*Data Visualization Implementation
 +
*Resource Modeling Implementation
 +
*Management Enablement Implementation
 +
*CMDBf Implementation
  
The COSMOS 1.0 release is targeted for general availability on 20-July-2007. All release 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-3 will contain the bulk of the enhancement work, while Iteration 4 will mainly be used to stabilize and shut down the release.
+
== Release Milestones ==
  
Each project leader will send a notification to the project leadership team upon completion of iteration testingOnce all projects have indicated that they have finished iteration testing, a candidate build will be flagged and the teams can begin checking in code for the next iteration.
+
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 testThere will be a total of eight iterations broken out in the release schedule below.
  
 +
<br>
  
'''Release Milestones'''
+
{| cellspacing="0" cellpadding="0" border="1"
+
|- bgcolor="#c0c0c0"
{|border = "1" cellpadding="1"
+
| colspan="2" | '''Milestone'''
|-
+
| '''Duration'''
!Milestone
+
| '''Planned Start Date'''
!Start Date
+
| '''Planned End Date'''
!End Date
+
| '''Actual Start Date'''
!Description
+
| '''Actual End Date'''
|-
+
| '''Description'''
|'''Iteration 1'''
+
| '''Comments'''
|'''Tues 01/02/2007'''
+
|- bgcolor="#ccccdd"
|'''Fri 02/23/2007'''
+
| colspan="2" | '''Iteration 1'''  
|Demo development
+
| '''1 Month'''&nbsp;
|-
+
| '''Nov-2-2009'''
|'''Iteration 2'''
+
| '''Nov-30-2009'''
|'''Mon 02/26/2007'''
+
| &nbsp;
|'''Fri 04/06/2007'''
+
| &nbsp;
|
+
| '''Enhancements'''
|-
+
| &nbsp;
|   i2 Development
+
|- bgcolor="#e6e6fa"
|Mon 02/26/2007
+
| width="25" rowspan="2" | &nbsp;&nbsp;
|Fri 03/30/2007
+
| Development
|Development & Bug Fixes
+
| &nbsp;
|-  
+
| Nov-2-2009
|   i2 Testing
+
| Nov-23-2009
|Mon 04/02/2007
+
| &nbsp;
|Fri 04/06/2007
+
| &nbsp;
|Validation Testing
+
| Development &amp; bug fixes
|-
+
| &nbsp;
|'''Iteration 3'''
+
|- bgcolor="#e6e6fa"
|'''Mon 04/09/2007'''
+
| Testing
|'''Fri 05/18/2007'''
+
| &nbsp;
|
+
| Nov-24-2008
|-
+
| Nov-30-2009
|   i3 Development
+
| &nbsp;
|Mon 04/09/2007
+
| &nbsp;
|Fri 05/11/2007
+
| Validation Testing
|Development & Bug Fixes
+
| &nbsp;
|-  
+
|- bgcolor="#ccccdd"
|   i3 Testing
+
| colspan="2" | '''Iteration 2'''  
|Mon 05/14/2007
+
| '''1 Month'''&nbsp;
|Fri 05/18/2007
+
| '''Dec-1-2009'''
|Validation Testing
+
| '''Dec-24-2009'''
|-
+
| &nbsp;
|'''Iteration 4'''
+
| &nbsp;
|'''Mon 05/21/2007'''
+
| '''Enhancements'''
|'''Fri 06/15/2007'''
+
| &nbsp;
|Shut down and Europa General Availability June 29 2007
+
|- bgcolor="#e6e6fa"
|-
+
| rowspan="2" | &nbsp;&nbsp;
|   i4 Development
+
| Development
|Mon 05/21/2007
+
|
|Fri 06/08/2007
+
| Dec-1-2009
|Bug Fixes
+
| Dec-18-2009
|-  
+
| &nbsp;
|   i4 Testing
+
| &nbsp;
|Mon 06/11/2007
+
| Development &amp; bug fixes
|Fri 06/15/2007
+
| &nbsp;
|Validation Testing
+
|- bgcolor="#e6e6fa"
|-
+
| Testing
|'''Availability'''
+
| &nbsp;
|'''Fri 06/15/2007'''
+
| Dec-21-2009
|'''Fri 07/20/2007'''
+
| Dec-24-2009
|Available for POCs
+
| &nbsp;
 +
| &nbsp;
 +
| Validation Testing
 +
| &nbsp;
 +
|- bgcolor="#ccccdd"
 +
| colspan="2" | '''Iteration 3'''
 +
| '''1&nbsp;Month'''
 +
| '''Jan-4-2010'''
 +
| '''Jan-29-2010'''
 +
| &nbsp;
 +
| &nbsp;
 +
| '''Enhancements'''&nbsp;
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;&nbsp;
 +
| Development
 +
|
 +
| Jan-4-2010
 +
| Jan-22-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Development &amp; bug fixes
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;
 +
| Testing
 +
|
 +
| Jan-25-2010&nbsp;
 +
| Jan-29-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Validation Testing
 +
| &nbsp;
 +
|- bgcolor="#ccccdd"
 +
| colspan="2" | '''Iteration&nbsp;4'''  
 +
| '''1&nbsp;Month'''
 +
| '''Feb-1-2010'''
 +
| '''Feb-26-2010'''  
 +
| &nbsp;
 +
| &nbsp;
 +
| '''Enhancements'''&nbsp;
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;&nbsp;
 +
| Development  
 +
|  
 +
| Feb-1-2010
 +
| Feb-19-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Development &amp; bug fixes
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;
 +
| Testing
 +
|
 +
| Feb-22-2010&nbsp;
 +
| Feb-26-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Validation Testing
 +
| &nbsp;
 +
|- bgcolor="#c0c0c0"
 +
| colspan="2" | '''Iteration&nbsp;5'''
 +
| '''1&nbsp;Month'''
 +
| '''Mar-1-2010'''
 +
| '''Mar-31-2010'''
 +
| &nbsp;
 +
| &nbsp;
 +
| '''Milestone Driver'''&nbsp;
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;&nbsp;
 +
| Development
 +
|
 +
| Mar-1-2010
 +
| Mar-19-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Development &amp; bug fixes
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;
 +
| Testing
 +
|
 +
| Mar-22-2010&nbsp;
 +
| Mar-31-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Validation Testing
 +
| &nbsp;
 +
|- bgcolor="#ccccdd"
 +
| colspan="2" | '''Iteration&nbsp;6'''
 +
| '''1&nbsp;Month'''
 +
| '''Apr-1-2010'''
 +
| '''Apr-30-2010'''
 +
| &nbsp;
 +
| &nbsp;
 +
| '''Enhancements'''&nbsp;
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;&nbsp;
 +
| Development  
 +
|
 +
| Apr-1-2010
 +
| Apr-23-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Development &amp; bug fixes
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;
 +
| Testing  
 +
|  
 +
| Apr-26-2010&nbsp;
 +
| Apr-30-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Validation Testing  
 +
| &nbsp;
 +
|- bgcolor="#ccccdd"
 +
| colspan="2" | '''Iteration&nbsp;7'''
 +
| '''1&nbsp;Month'''
 +
| '''May-3-2010'''  
 +
| '''May-31-2010'''  
 +
| &nbsp;
 +
| &nbsp;
 +
| '''Enhancements'''&nbsp;
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;&nbsp;
 +
| Development  
 +
|  
 +
| May-3-2010
 +
| May-24-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Development &amp; bug fixes
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;
 +
| Testing  
 +
|  
 +
| May-25-2010&nbsp;
 +
| May-31-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Validation Testing  
 +
| &nbsp;
 +
|- bgcolor="#c0c0c0"
 +
| colspan="2" | '''Iteration&nbsp;8'''  
 +
| '''1&nbsp;Month'''  
 +
| '''Jun-1-2010'''  
 +
| '''Jun-25-2010'''
 +
| &nbsp;
 +
| &nbsp;
 +
| '''Release Driver'''
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;&nbsp;
 +
| Development  
 +
|  
 +
| Jun-1-2010
 +
| Jun-11-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Development &amp; bug fixes
 +
| &nbsp;
 +
|- bgcolor="#e6e6fa"
 +
| &nbsp;
 +
| Testing  
 +
|  
 +
| Jun-14-2010&nbsp;
 +
| Jun-25-2010
 +
| &nbsp;
 +
| &nbsp;
 +
| Validation Testing  
 +
| &nbsp;
 +
|- bgcolor="#c0c0c0"
 +
| colspan="2" | '''COSMOS 1.2 availability'''  
 +
| '''1 day'''  
 +
| '''June-30-2010'''  
 +
| '''June-30-2010'''
 +
| &nbsp;
 +
| &nbsp;
 +
| '''GA Release'''
 +
| &nbsp;
 
|}
 
|}
  
==== Themes ====
+
<br>See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=259011|bugzilla 259011] for details on how those release review dates were calculated. They are tentative and may change.
  
The COSMOS project adopted the following theme which represents the key focus area for COSMOS enhancements in the year ahead.
+
== Major deliverables  ==
* Provide an open platform that is standards-based for extensibility and openness
+
* Provide exemplary tools for monitoring and management of popular open distributed platforms
+
* Establish base framework:
+
** Data collection normalization and persistence framework
+
** Validation/Editing/Viewing framework based on SML
+
  
==== Project Designs ====
+
* 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
  
The COSMOS project is comprised of four projects, managed in a coordinated fashion, across which the plan items are allocated. COSMOS projects include:
+
== Features ==
  
* '''Data Collection Project''' - The COSMOS Data Collection framework aims to provide value by building a standard based integration framework that can incrementally replace the existing ad hoc integrations between agent infrastructures and the management applications that utilize them. The initial focus of the data collection component is the delivery of a framework that provides a well-defined set of service interface types that facilitate the discovery and control of monitoring agents as well as related data services such as collection, transformation, filtering, persistence, and query. These services may be discovered, explored, and controlled through Web Services Distributed Management (WSDM) standard interfaces. They will describe themselves by exposing Service Modeling Language Interchange Format (SML-IF) models using WS-metadata exchange.
+
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.  
* '''Data Visulization Project''' ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180073 Design Document])- The COSMOS Data Visualization framework aims to provide value by building a standards based integration infrastructure that provides access to two dimensions of the COSMOS management architecture, COSMOS Data Collection and COSMOS Resource Modeling. COSMOS Data Visualization provides a well-defined set of service interface types that facilitate the exploration of the COSMOS Resource Modeling's repository of models and the retrieval of the COSMOS Data Collection's repository of state, event, and performance information. The model repository is semantically linked to the information in the monitor data repository. This relationship, which is managed in Service Modeling Language (SML) through the Resource Modeling component, is used to connect the exploration of the model with data that has been collected.
+
* '''Resource Modeling Project''' -  The COSMOS Resource Modeling sub-project aims to provide support for building a common model to represent the information being shared in a system management scenario. The project is proposing to use Service Modeling Language (SML) as the XML schema language to define this common model. The SML-IF interchange format will be used to share model components between the tools involved in a system management activity. 
+
* '''Management Enablement''' - To be implemented in a future release
+
+
Designs for these projects will be checked in to the COSMOS bugzilla database so that developers can reference them as they create designs for specific plan items.
+
  
==== Features ====
+
== Iteration test status ==
 
+
*[[COSMOS_1.2_I1_Test|Iteration 1]]
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.
+
*[[COSMOS_1.2_I2_Test|Iteration 2]]
 
+
*[[COSMOS_1.2_I3_Test|Iteration 3]]
'''COSMOS Data Collection Project Plan Items'''
+
*[[COSMOS_1.2_I4_Test|Iteration 4]]
{|border = "1" cellpadding="1"
+
*[[COSMOS_1.2_I5_Test|Iteration 5]]
|-
+
*[[COSMOS_1.2_I6_Test|Iteration 6]]
!Status
+
*[[COSMOS_1.2_I7_Test|Iteration 7]]
!Description
+
*[[COSMOS_1.2_I8_Test|Iteration 8]]
|-
+
|In Plan
+
|Define and build the COSMOS data collection framework. This includes: definition and implementation of the component assembly framework SPI, implementation of binding and component context loading services for an Equinox OSGi host, definition of component APIs supporting all currently defined component types (data source, data sink, filter, transformer), base classes for all currently defined component types, component assembly schema, automated build process for the data collection component, user documentation for adopters of the framework, and automated unit test cases.  The following enhancements are being used to track this work: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=174347 (174347)] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=177821 (177821)] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=180318 (180318)] .
+
|-
+
|In Plan
+
|
+
|-
+
|Not In Plan
+
|Exemplary components for the data collection framework.  [https://bugs.eclipse.org/bugs/show_bug.cgi?id=180322 (180322)]
+
|}
+
 
+
+
'''COSMOS Data Visualization Project Plan Items'''
+
{|border = "1" cellpadding="1"
+
|-
+
!Status
+
!Description
+
|-
+
|In Plan
+
|Visualize a read-only model (the ui is not expected to modify the resource model or data collection information), provide a simple navigation system based on a resource graph, show properties of a resource, and provide visualization of collected resource information.  [https://bugs.eclipse.org/bugs/show_bug.cgi?id=180069 (180069)] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=180073 (180073)]
+
|-
+
|In Plan
+
|Create Data Retrieval Service framework and components. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=184242 (184242)]
+
|-
+
|In Plan
+
|Create Graphical Visualization Service framework and components. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=184243 (184243)]
+
|-
+
|In Plan
+
|Create Presentation Service framework and components. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=184245 (184245)]
+
|-
+
|Not in Plan
+
|}
+
+
'''COSMOS Resource Modeling Project Plan Items'''
+
{|border = "1" cellpadding="1"
+
|-
+
!Status
+
!Description
+
|-
+
|In Plan
+
|Provide validator for SML and SML-IF documents, based on the SML 1.0 specification
+
|-
+
|In Plan
+
|Provide import from SML-IF and export to SML-IF action for a file based SML repository
+
|-
+
|In Plan
+
|Provide simple SML-IF editor for creating SML-IF documents from a file based repository
+
|-
+
|In Plan
+
|Create agent descriptors in SML to represent logging agents. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178590 (178590)]
+
|-
+
|In Plan
+
|Provide a data layer for Data Visualization access to resource, which includes the following services: data filtering, data grouping, data sorting and data counts.  [https://bugs.eclipse.org/bugs/show_bug.cgi?id=180068 (180068)]
+
|-
+
|In Plan
+
|Provide the concept of a repository under the resource modeling subproject. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179828 (179828)]
+
|-
+
|In Plan
+
|SML validator should accept input other than File resources. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=181594 (181594)]
+
|-
+
|In Plan
+
|Create more test cases for the validation plug-in. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=172682 (172682)]
+
|-
+
|Not in Plan
+
|}
+

Latest revision as of 17:01, 9 November 2009

COSMOS Wiki > COSMOS Work Items

COSMOS 1.2 Release Plan

Overview

Please send comments about this plan to the cosmos-mgmt@eclipse.org 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

Features

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