Project Plan For Model Development Tools (MDT), version Galileo
Introduction
This document lays out the feature and API set for the third release of the Eclipse Model Development Tools (MDT) Project. This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.
Release Deliverables
The release deliverables have the same form as is found in most Eclipse projects, namely:
- source code release, available as versions tagged "R0_7" in the project's CVS repository.
- SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
- runtime binary distribution (downloadable and update site).
- tests (downloadable)
- source code release, available as versions tagged "R0_7" in the project's CVS repository.
- SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
- runtime binary distribution (downloadable and update site).
- tests (downloadable)
- source code release, available as versions tagged "R1_3" in the project's CVS repository.
- SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
- runtime binary distribution (downloadable and update site).
- tests (downloadable)
- source code release, available as versions tagged "R0_7" in the project's CVS repository.
- SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
- runtime binary distribution (downloadable and update site).
- tests (downloadable)
- source code release, available as versions tagged "R3_0" in the project's CVS repository.
- SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
- runtime binary distribution (downloadable and update site).
- tests (downloadable)
- source code release, available as versions tagged "R0_9" in the project's CVS repository.
- SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
- runtime binary distribution (downloadable and update site).
- Tools tests (downloadable)
- source code release, available as versions tagged "R2_5" in the project's CVS repository.
- SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
- runtime binary distribution (downloadable and update site).
- tests (downloadable)
Release Milestones
Release milestone occurring at roughly 6 week intervals and follow the Platform
milestone releases by approximately 3 weeks; that is, until the final 3.5
release of the Platform, upon which MDT and other projects will release
simultaneously. Components of MDT that are dependencies of numerous other
projects will deliver their milestones within one week of the Eclipse Platform.
It is anticipated that MDT will synchronize its milestones with the Galileo
milestone schedule.
M2 | 10/03/2008 | |
M3 | 11/14/2008 | |
M4 | 01/05/2009 | |
M5 | 02/10/2009 | |
M6 | 03/19/2009 | API Freeze |
M7 | 05/06/2009 | Feature Freeze |
RC1 | 05/20/2009 | |
RC2 | 05/27/2009 | |
RC3 | 06/03/2009 | |
RC4 | 06/10/2009 | |
RC5 | 06/17/2009 | |
Galileo | 06/26/2009 |
MDT will produce maintenance releases to align with the Ganymede SR releases,
that includes the Eclipse Platform 3.4.1 and 3.4.2 releases. MDT may produce
interim maintenance releases in addition to these in order to satisfy client
requests.
Target Environments
In order to remain current, each Eclipse release targets reasonably current
versions of the underlying operating environments. The Eclipse Model
Development Tools (MDT) project depends upon on the Platform and other
projects, which are mostly "pure" JavaTM. The 3.5
release of the Eclipse Platform Project is written and compiled against version
1.4 of the Java Platform APIs, and targeted to run on version 1.4 of the Java
Runtime Environment, Standard Edition. MDT will target the same Java version as
EMF, which currently requires Java 5. Eclipse Platform SDK 3.5 will be tested
and validated on a number of reference platforms. MDT will be tested and
validated against a subset of those listed for the platform.
Internationalization
The Eclipse Platform is designed as the basis for internationalized products.
The user interface elements provided by the Eclipse SDK components, including
dialogs and error messages, are externalized. The English strings are provided
as the default resource bundles. As a result, the MDT project will provide
English strings in its default bundles and be localized to a subset of those
locales offered by the Platform. This plan will be updated to indicate which
locales will be provided and the time frame for availability.
Compatibility with Previous Releases
Compatibility of Galileo Release: The MDT project will be developed in
parallel, and released simultaneously, with the following projects. As stated
above, each milestone release of the MDT project will be compatible with the
corresponding milestones for each of these projects, and delivered the
appropriate offset.
- Eclipse Platform SDK version 3.5
- Eclipse Modeling Framework (EMF) version 2.5
- Graphical Modeling Framework (GMF) version 2.2
Themes and Priorities
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.
Release Currency
- Committed
- No items.
- Proposed
- Maintain Currency with EMF, UML2 Templates [207365] (target milestone: 1.3.0)
- Deferred
- OCL Specification Currency [156363] (target milestone: 2.0.0)
- Committed
- No items.
- Proposed
- Support for conversion of owned ends [157982] (target milestone: 3.0.0)
- Deferred
- No items.
Extensibility
- Committed
- OCL's type checking system needs to be extensible. [233673]
(target milestone: M3) - InvOrDefCS irregularities [243976]
(target milestone: M3) - Bug in AbstractEnvironment when looking up implicit sources [234354]
(target milestone: M2) - Provide a general support for parameterized type resolution bycustom OCL environments [179990]
(target milestone: M4) - Use resolved operation name to determine OperationCallExp.opcode [213886]
(target milestone: M2) - Adopt Eclipse API Tooling [248869]
(target milestone: M3)
- OCL's type checking system needs to be extensible. [233673]
- Proposed
- Adding a parsing option to exclude non-standard operations from OCL Standard Library [228839] (target milestone: 1.3.0)
- There is currently no way to un-define an operation [236604] (target milestone: 1.3.0)
- OperationCallExp arguments_conform constraint looks up operation [236247]
(target milestone: 1.3.0)
- Deferred
- No items.
Appealing to a Broader Community
- Committed
- Proposed
- Deferred
- No items.
Compliance
- Committed
- BPMN 2.0 Metamodel [247456] (target milestone: M6)
- Proposed
- No items.
- Deferred
- No items.
- Committed
- XML Schema Profile [247460] (target milestone: M6)
- E/R Metamodel [230441] (target milestone: M6)
- Core Metamodel [230443] (target milestone: M6)
- E/R Profile [247458] (target milestone: M6)
- Relational Profile [247459] (target milestone: M6)
- XMI for Relational Metamodel [248025] (target milestone: M6)
- XMI for XML Schema Metamodel [248024] (target milestone: M6)
- Proposed
- Deferred
- No items.
- Committed
- Proposed
- Deferred
- No items.
- Committed
- Proposed
- UML2 Implementation Bug - Redefinable Template Signature does not conform to OMG Spec [238537] (target milestone: 3.0.0)
- Deferred
- No items.
Community Support
- Committed
- Genmodel copyright fields setting ignored for operations classes [242726] (target milestone: M4)
- Proposed
- Deferred
- No items.
- Committed
- No items.
- Proposed
- No items.
- Deferred
Usability
- Committed
- Proposed
- No items.
- Deferred
- No items.
Sample Tools
- Committed
- Sample SBVR editor and menus [226017] (target milestone: M4)
- Proposed
- Deferred
- No items.
Appendix Legal Notices
- Java is a trademark or a registered trademark of Sun Microsystems, Inc.
- All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.