blob: 310f58eff40132b649b8a4cedb515f03ce5b4104 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan plan-format="1.0" xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml"
name="CDO Model Repository">
<release projectid="modeling.emf.cdo" version="4.0"/>
<introduction>
<html:div>
This document lays out the feature and API set for the
third release of the CDO Model Repository
Project (CDO), version 4.0. This project plan inherits from the Modeling
Project Plan, which should be referenced when consulting this
individual project plan.
</html:div>
</introduction>
<release_deliverables>
<html:div>
The release deliverables have the same form as is found in most Eclipse projects, namely:
<html:ul>
<html:li><html:b>CDO Dawn Codegen</html:b> (Contains the code generation aspects for graphical collaboration support over CDO.)</html:li>
<html:li><html:b>CDO Dawn Examples</html:b> (Contains example plugins to demonstrate a range of functions of Dawn.)</html:li>
<html:li><html:b>CDO Dawn Runtime</html:b> (Contains the runtime aspects for graphical collaboration support over CDO.)</html:li>
<html:li><html:b>CDO Dawn SDK</html:b> (Includes Runtime, Codegen, Tools, Examples, Documentation and Source.)</html:li>
<html:li><html:b>CDO Gastro Example</html:b> (Contains the CDO Gastro RCP plugins, models and sources.)</html:li>
<html:li><html:b>CDO Model Repository Client</html:b> (Contains the CDO client core and user interface plugins.)</html:li>
<html:li><html:b>CDO Model Repository Definitions</html:b> (Contains the EMF-based definition and wiring plugins for CDO.)</html:li>
<html:li><html:b>CDO Model Repository Documentation</html:b> (Contains the documentation of the CDO SDK.)</html:li>
<html:li><html:b>CDO Model Repository EPP</html:b> (Contains a minimum CDO client and server environment for the Eclipse Modeling package.)</html:li>
<html:li><html:b>CDO Model Repository Examples</html:b> (Contains the CDO example plugin, models and sources.)</html:li>
<html:li><html:b>CDO Model Repository SDK</html:b> (Includes Client, Server, Tools, Examples, Documentation and Source.)</html:li>
<html:li><html:b>CDO Model Repository Server</html:b> (Contains the CDO server plugins.)</html:li>
<html:li><html:b>CDO Model Repository Server DB</html:b> (Contains the DBStore plugins.)</html:li>
<html:li><html:b>CDO Model Repository Server DB4O</html:b> (Contains the DB4O Store bundle. Ensure that DB4O Driver is already installed! Visit http://net4j.sourceforge.net/update for a p2 repository that contains DB4O Driver.)</html:li>
<html:li><html:b>CDO Model Repository Server Hibernate</html:b> (Contains the HibernateStore and Teneo integration plugins. Ensure that Hibernate is already installed! Visit http://net4j.sourceforge.net/update for a p2 repository that contains Hibernate.)</html:li>
<html:li><html:b>CDO Model Repository Server Objectivity</html:b> (Contains the Objectivity Store and stubbed jar file bundle. For runtime, ensure that you have Objectivity /DB installed!)</html:li>
<html:li><html:b>CDO Model Repository Server Product</html:b> (Contains the product definition of an installable CDO server.)</html:li>
<html:li><html:b>CDO Model Repository Tests</html:b> (Contains the CDO test plugins, models and sources.)</html:li>
<html:li><html:b>CDO Release Engineering Version Tool</html:b> (Contains the release engineering plugins and extensions.)</html:li>
<html:li><html:b>Net4j DB Framework</html:b> (Contains the database core framework and database adapter plugins for Derby, Mysql, HSQLDB and PostgreSQL. Additional database drivers are available via http://net4j.sourceforge.net/update. Read the license informations.)</html:li>
<html:li><html:b>Net4j DB Framework Derby Adapter</html:b> (Contains the Derby Adapter matching the Net4j DB Framework and the database driver bundle for Derby.)</html:li>
<html:li><html:b>Net4j DB Framework H2 Adapter</html:b> (Contains the H2 Adapter matching the Net4j DB Framework and the database driver bundle for H2.)</html:li>
<html:li><html:b>Net4j DB Framework HSQLDB Adapter</html:b> (Contains the HSQLDB Adapter matching the Net4j DB Framework BUT NOT the database driver bundle for HSQLDB. This needs to be installed separately, for example from http://net4j.sourceforge.net/update)</html:li>
<html:li><html:b>Net4j DB Framework MYSQL Adapter</html:b> (Contains the MYSQL Adapter matching the Net4j DB Framework BUT NOT the database driver bundle for MYSQL. This needs to be installed separately, for example from http://net4j.sourceforge.net/update)</html:li>
<html:li><html:b>Net4j DB Framework PostgreSQL Adapter</html:b> (Contains the PostgreSQL Adapter matching the Net4j DB Framework BUT NOT the database driver bundle for PostgreSQL. This needs to be installed separately, for example from http://net4j.sourceforge.net/update)</html:li>
<html:li><html:b>Net4j Signalling Platform Definitions</html:b> (Contains the EMF-based definition and wiring plugins for Net4j.)</html:li>
<html:li><html:b>Net4j Signalling Platform Examples</html:b> (Contains the general Net4j examples, the buddies collaboration + chat examples and the experimental JMS provider implementation plugins, as well as all sources.)</html:li>
<html:li><html:b>Net4j Signalling Platform Runtime</html:b> (Contains the Net4j core and transport provider plugins, e.g. tcp, jvm and http.)</html:li>
<html:li><html:b>Net4j Signalling Platform SDK</html:b> (Includes Runtime, UI, DB, Examples, Documentation and Source.)</html:li>
<html:li><html:b>Net4j Signalling Platform Tests</html:b> (Contains the Net4j test plugins and sources.)</html:li>
<html:li><html:b>Net4j Signalling Platform UI</html:b> (Contains the Net4j user interface and utilities user interface plugins. </html:li>
</html:ul>
</html:div>
</release_deliverables>
<release_milestones>
<preamble>
<html:div>
Release milestone occurring at roughly 6 week intervals and follow the
Platform milestone releases by approximately 1 week; that is, until the
final 3.7 release of the Platform, upon which CDO and other projects
will release simultaneously. CDO will deliver its milestones within one week of
the Eclipse Platform. It is anticipated that CDO will synchronize its
milestones with the Helios milestone schedule.
</html:div>
</preamble>
<milestone date="08/17/2010" milestone="M1"></milestone>
<milestone date="09/28/2010" milestone="M2"></milestone>
<milestone date="11/09/2010" milestone="M3"></milestone>
<milestone date="12/14/2010" milestone="M4"></milestone>
<milestone date="02/01/2011" milestone="M5"></milestone>
<milestone date="03/15/2011" milestone="M6"><html:div>API freeze</html:div></milestone>
<milestone date="05/03/2011" milestone="M7"><html:div>Feature Freeze</html:div></milestone>
<milestone date="05/17/2011" milestone="RC1"></milestone>
<milestone date="05/24/2011" milestone="RC2"></milestone>
<milestone date="05/31/2011" milestone="RC3"></milestone>
<milestone date="06/07/2011" milestone="RC4"></milestone>
<milestone date="06/22/2011" milestone="Final"></milestone>
<postamble><html:div>
CDO will produce maintenance releases to align with the Helios SR
releases, that includes the Eclipse Platform 3.6.x release.
CDO may produce interim maintenance releases in addition to these in
order to satisfy client requests. Maintenance releases will only be published
if they have any new fixes to offer.
<html:ul>
<html:li>09/24/2010 - CDO 3.0.1 maintenance release (Helios Service Release 1)</html:li>
<html:li>02/25/2011 - CDO 3.0.2 maintenance release (Helios Service Release 2)</html:li>
<html:li>A list of issues indicated for the 3.0.x maintenance stream can be found in
bugzilla, or by using links on maintenance stream build pages.</html:li>
</html:ul>
</html:div></postamble>
</release_milestones>
<target_environments>
<html:div>
In order to remain current, each Eclipse release targets reasonably
current versions of the underlying operating environments. The CDO Model Repository
Project (CDO) depends upon on the
Platform and other projects, which are mostly "pure" Java<html:sup>TM</html:sup>. CDO
will target the same Java version as EMF Core, which currently requires
Java 5. Eclipse Platform SDK 3.7 will be tested and validated on a
number of reference platforms. CDO will be tested and validated
against a subset of those listed for the platform.
</html:div>
<internationalization>
<html:div>
The CDO Model Repository is a runtime technology with most of the
components having no user interface. The remaining user interface
parts of CDO are considered exemplary and thus no attention has been
paid to externalize them for internationalization.
</html:div>
</internationalization>
</target_environments>
<compatibility_with_previous_releases>
<html:div>
The 4.0 release of the CDO Model Repository will contain a large set of new
functionality and an enhanced API as driven by the community. Therefore CDO
will not be binary compatible with previous releases. Careful attention
has been paid to minimize the API related changes and the resulting impact
to existing applications based upon CDO.
</html:div>
</compatibility_with_previous_releases>
<themes_and_priorities>
<preamble>
<html:div>
A list of project requirements and agreed upon
implementation time frames is found in this document. For the
milestones listed in this document, a set of overall themes is used
to indicate what major set of functionalities is to be concentrated
on for each. These themes are presented below, while the requirements
document and associated Bugzilla entries are left to those wanting
more detailed information on each.
</html:div>
</preamble>
<theme name="Power to the People">
<description>
<html:div>
Major improvements in the API and configuration will give clients considerably more
control over the behaviour and performance of their repositories and sessions.
</html:div>
</description>
<committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard_type=allwordssubstr&amp;query_format=advanced&amp;status_whiteboard=Power%20to%20the%20People&amp;bug_status=RESOLVED&amp;version=4.0&amp;component=cdo.core&amp;component=cdo.dawn&amp;component=cdo.db&amp;component=cdo.docs&amp;component=cdo.hibernate&amp;component=cdo.net4j&amp;component=cdo.net4j.db&amp;component=cdo.net4j.ui&amp;component=cdo.objy&amp;component=cdo.releng&amp;component=cdo.ui&amp;resolution=FIXED&amp;product=EMF&amp;classification=Modeling">
</committed>
<!--
<proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;classification=Modeling&amp;product=EMF&amp;component=CDO&amp;target_milestone=Helios&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=substring&amp;status_whiteboard=Power+to+the+People&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=flagtypes.name&amp;type0-0-0=equals&amp;value0-0-0=indigo%2B">
</proposed>
<deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;classification=Modeling&amp;product=EMF&amp;component=CDO&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=Power+to+the+People&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=flagtypes.name&amp;type0-0-0=equals&amp;value0-0-0=indigo-">
</deferred>
-->
</theme>
<theme name="Appealing to a Broader Community">
<description>
<html:div>
The CDO project has a proven record of robustness and flexibility. However,
in the past best results could only be achieved with EMF models specifically
generated for the usage with CDO. The upcoming 3.0 release will be less invasive
to the client models and applications by being better aligned with EMF and other standards.
</html:div>
</description>
<committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard_type=allwordssubstr&amp;query_format=advanced&amp;status_whiteboard=Appealing%20to%20a%20Broader%20Community&amp;bug_status=RESOLVED&amp;version=4.0&amp;component=cdo.core&amp;component=cdo.dawn&amp;component=cdo.db&amp;component=cdo.docs&amp;component=cdo.hibernate&amp;component=cdo.net4j&amp;component=cdo.net4j.db&amp;component=cdo.net4j.ui&amp;component=cdo.objy&amp;component=cdo.releng&amp;component=cdo.ui&amp;resolution=FIXED&amp;product=EMF&amp;classification=Modeling">
</committed>
<!--
<proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;classification=Modeling&amp;product=EMF&amp;component=CDO&amp;target_milestone=Helios&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=substring&amp;status_whiteboard=Appealing+to+a+Broader+Community&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=flagtypes.name&amp;type0-0-0=equals&amp;value0-0-0=indigo%2B">
</proposed>
<deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;classification=Modeling&amp;product=EMF&amp;component=CDO&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=Appealing+to+a+Broader+Community&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=flagtypes.name&amp;type0-0-0=equals&amp;value0-0-0=indigo-">
</deferred>
-->
</theme>
<theme name="Lighter, Faster and Better">
<description>
<html:div>
The CDO project has a proven track record of quality, reliability, and extensibility
but all these aspects can be continuously improved.
Existing and new clients often desire more functionality from the framework
while long established clients generally desire mostly improvements in performance.
Often these two are at odds since additional extensibility often has a performance cost
and any changes, even performance boosting ones, potentially impact reliability.
Every effort will be made to introduce new capabilities
so that they have negligible impact on established clients
based on the guiding principle:
if you don't use it,
you don't pay for it.
Because service and support has and always will take priority over new development work,
development commitments and schedules are subject to arbitrary change, slippage, or even deferral.
Be sure to establish direct communication to ensure that any hard commitments
are seen as that by the development team itself!
</html:div>
</description>
<committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard_type=allwordssubstr&amp;query_format=advanced&amp;status_whiteboard=Lighter,%20Faster%20and%20Better&amp;bug_status=RESOLVED&amp;version=4.0&amp;component=cdo.core&amp;component=cdo.dawn&amp;component=cdo.db&amp;component=cdo.docs&amp;component=cdo.hibernate&amp;component=cdo.net4j&amp;component=cdo.net4j.db&amp;component=cdo.net4j.ui&amp;component=cdo.objy&amp;component=cdo.releng&amp;component=cdo.ui&amp;resolution=FIXED&amp;product=EMF&amp;classification=Modeling">
</committed>
<!--
<proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;classification=Modeling&amp;product=EMF&amp;component=CDO&amp;target_milestone=Helios&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=substring&amp;status_whiteboard=Lighter,+Faster+and+Better&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=flagtypes.name&amp;type0-0-0=equals&amp;value0-0-0=indigo%2B">
</proposed>
<deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;classification=Modeling&amp;product=EMF&amp;component=CDO&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=Lighter,+Faster+and+Better&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=flagtypes.name&amp;type0-0-0=equals&amp;value0-0-0=indigo-">
</deferred>
-->
</theme>
<theme name="Eclipse 4.1">
<description>
<html:div>
No support, no testing on 4.1
</html:div>
</description>
</theme>
</themes_and_priorities>
<appendix name="A: Legal Notices">
<html:div>
<html:ul>
<html:li>Java is a trademark or a registered trademark of Sun Microsystems, Inc.</html:li>
<html:li>All other products or company names are mentioned for identification purposes only, and
may be trademarks or service marks of their respective owners.</html:li>
</html:ul>
</html:div>
</appendix>
</plan>