Project Plan For Model Development Tools (MDT), version Galileo

Introduction

This document lays out the feature and API set for the fourth release of the Eclipse Object Constraint Language (MDT OCL) Project, version 1.3.0. This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.

Note that, depending on the nature of the anticipated OCL® 2.1 revised specification from the OMGTM, MDT OCL may require incompatible API changes and release as version 2.0.0.

Release Deliverables

The release deliverables have the same form as is found in most Eclipse projects, namely:
  • MDT OCL source code release, available as versions tagged "R1_3" in the project's CVS repository.
  • MDT OCL SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
  • MDT OCL runtime binary distribution (downloadable and update site).
  • MDT OCL stand-alone binary distribution (downloadable).
  • MDT OCL tests (downloadable)

Table of Contents

Release Milestones

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 1 week; that is, until the final 3.5 release of the Platform, upon which MDT OCL and other projects will release simultaneously. As MDT OCL is a dependency of numerous other projects, MDT OCL will deliver its milestones within one week of the Eclipse Platform. It is anticipated that MDT OCL will synchronize its milestones with the Galileo milestone schedule.
M108/13/2008
M209/24/2008
M311/05/2008
M412/17/2008
M502/03/2009
M603/16/2009
API freeze
M705/04/2009
Feature Freeze
RC105/18/2009
RC205/25/2009
RC306/01/2009
RC406/08/2009
RC506/15/2009
1.3.006/28/2009
MDT OCL 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 OCL may produce interim maintenance releases in addition to these in order to satisfy clients requests.
  • Friday, August 15, 2008 - MDT OCL 1.2.1 maintenance release
  • Friday, September 26, 2008 - MDT OCL 1.2.2 maintenance release (Ganymede Service Release 1)
  • Friday, February 27, 2009 - MDT OCL 1.2.3 maintenance release (Ganymede Service Release 2)
  • A list of issues indicated for the 1.2.x maintenance stream can be found in bugzilla, or by using links on maintenance stream build pages.

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The Eclipse Object Constraint Language (MDT OCL) 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 OCL will target the same Java version as EMF and UML2, which currently require Java 5. Eclipse Platform SDK 3.5 will be tested and validated on a number of reference platforms. MDT OCL 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 OCL 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.

Table of Contents

Compatibility with Previous Releases

Compatibility of Release 1.3: The MDT OCL project will be developed in parallel, and released simultaneously, with the following projects. As stated above, each milestone release of the MDT OCL 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
  • Model Development Tools (MDT) UML2 version 2.3
Therefore, the MDT OCL initial release will be compatible with these versions and will publish binary and source compatibilities with migration guides on subsequent releases.

Table of Contents

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

The MDT OCL project will maintain currency with its dependencies, in particular advances in the EMF and MDT UML2 projects. Additionally, as an implementation of the OMG's OCL 2.0 specification, the MDT OCL project will maintain currency with the revised 2.1 specification.

Extensibility

The Object Constraint Language is re-used and extended by other language specifications, in particular the OMG MOF® Query/View/Transformation family of languages. This theme addresses the need for extensibility of the MDT OCL language implementation and APIs.

Appealing to a Broader Community

There are a few fairly routine capabilities which, historically, MDT OCL has not supplied because of its narrow focus on parsing and evaluating OCL text. User demand shows the value of providing the EMF.Edit plug-ins, for example, as well as a more flexible feature structure.

Table of Contents

Appendix Legal Notices

  • Java is a trademark or a registered trademark of Sun Microsystems, Inc.
  • OCL and OMG are trademarks or registered trademark of the Object Management GroupTM, Inc.
  • All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"