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

Introduction

This document lays out the feature and API set for the next release of the Eclipse UML2 API (MDT UML2) Project, version 4.0.0. 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:
  • MDT UML2 source code release, available as versions tagged "R4_0" in the project's git repository.
  • MDT UML2 SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
  • MDT UML2 runtime binary distribution (downloadable and update site).
  • MDT UML2 stand-alone binary distribution (downloadable).
  • MDT UML2 tests (downloadable)

Table of Contents

Release Milestones

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 1 day; that is, until the final 3.8 release of the Platform, upon which MDT UML2 and other projects will release simultaneously. As MDT UML2 is a dependency of numerous other projects, MDT UML2 will deliver its milestones within one day of the Eclipse Platform. It is anticipated that MDT UML2 will synchronize its milestones with the Juno milestone schedule.
M108/15/2011
M209/26/2011
M311/07/2011
M412/12/2011
M501/30/2012
M603/12/2012
API Freeze
M705/07/2012
Feature Freeze
RC105/21/2012
RC205/28/2012
RC306/04/2012
RC406/11/2012
Juno06/27/2012
MDT UML2 will produce maintenance releases to align with the Indigo SR releases, that includes the Eclipse Platform 3.7.1 and 3.7.2 releases. MDT UML2 may produce interim maintenance releases in addition to these in order to satisfy clients requests.
  • Friday, September 23, 2011 - MDT UML2 3.2.1 maintenance release (Indigo Service Release 1)
  • Friday, February 24, 2012 - MDT UML2 3.2.2 maintenance release (Indigo Service Release 2)
  • A list of issues indicated for the 3.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 Unified Modeling Language (MDT UML2) project depends upon on the Platform and other projects, which are mostly "pure" Java. The 3.8 release of the Eclipse Platform Project is written and compiled against versions 1.5 and 1.6 of the Java Platform APIs, and targeted to run on version 1.5 of the Java Runtime Environment, Standard Edition. MDT UML2 will target the same Java version as EMF, which currently also requires Java 5. Eclipse Platform SDK 3.8 will be tested and validated on a number of reference platforms. MDT UML2 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 UML2 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 4.0: The MDT UML2 project will be developed in parallel, and released simultaneously, with the following projects. As stated above, each milestone release of the MDT UML2 project will be compatible with the corresponding milestones for each of these projects, and delivered the appropriate offset.
  • Eclipse Platform SDK version 3.8
  • Eclipse Modeling Framework (EMF) version 2.8
Therefore, the MDT UML2 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.

Community Support

The MDT UML2 project has a proven track record of quality and reliability. Service and support will take priority over new development work; commitments and schedules are subject to arbitrary change, slippage, or even deferral.
  • Committed

    • UML2Ecore Converter should make derived features transient [236184] (target milestone: M4)
    • [Static Profiles] API proposal to get StereotypeApplication from a UML Element [350402] (target milestone: M4)
    • Migrate source repository to git [351775] (target milestone: M4)
    • Migrate build system to Buckminster [351776] (target milestone: M4)
    • Keep up with EMF 2.8 changes [351777] (target milestone: RC)

Compliance

As an implementation of the OMG's UML specification, the MDT UML2 project will maintain currency with the revised 2.4(.1) specification.
  • Committed

    • Update existing getting started articles. [205478] (target milestone: M4)
    • Static version of the Standard UML profile [226723] (target milestone: M4)
    • Support for UML 2.3 [290042] (target milestone: M4)
    • Support for UML 2.3: package merge bug? [292171] (target milestone: M4)
    • Support for UML 2.4 [327039] (target milestone: M4)
    • Support for UML 2.4.1 [351774] (target milestone: M4)
  • Deferred

    • Support converting a toplevel CMOF package into a metamodel. [304719] (target milestone: ---)

Table of Contents

Appendix Legal Notices

  • Java is a trademark or a registered trademark of Sun Microsystems, Inc.
  • UML 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"