Project Plan For Graphical Modeling Framework (GMF) Tooling, version 3.1.0

Introduction

This document lays out the feature and API set for the Kepler release of the Eclipse Graphical Modeling Framework Tooling (GMF-T) Project, version 3.1.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:

  • GMF Tooling source code release, available as versions tagged "R3_1" in the project's GIT repository.
  • GMF Tooling SDK (includes sources, examples, and documentation) (downloadable zip and update site).
  • GMF Tooling Runtime binary distribution (downloadable zip and update site).
  • GMF Tooling Tests (downloadable zip)

Table of Contents

Release Milestones

Release milestones occur at roughly 6 week intervals and follow the Platform milestone releases by approximately 2 weeks; that is, until the final 4.3 release of the Platform, upon which GMF Tooling and other projects will release simultaneously. It is anticipated that GMF Tooling will synchronize its release milestones with the Kepler release schedule for +3 components.

M210/03/2012
M311/15/2012
M412/19/2012
M502/05/2013
M603/19/2013
M705/08/2013
RC105/22/2013
RC205/29/2013
RC306/05/2013
RC406/12/2013
3.1.006/26/2013

GMF Tooling will produce maintenance releases to align with the Kepler SR releases, that includes the Eclipse Platform 4.3.1 and 4.3.2 releases. GMF Tooling may produce interim maintenance releases in addition to these in order to satisfy clients requests.

  • 9/28/2013 (last Friday of September) - GMF Tooling 3.1.1 maintenance release (Kepler Service Release 1)
  • 2/22/2014 (last Friday of February) - GMF Tooling 3.1.2 maintenance release (Kepler Service Release 2)
  • A list of issues indicated for the 3.1.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.

To Be Added Here

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 GMF Tooling 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 3.1

To Be Added Here

Therefore, the GMF tooling 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

The project has identified major areas of work, that will be the priorities for this development cycle. These areas will address the major themes identified by the Eclipse Requirements Council ( Eclipse Themes and Priorities).

Currency

  • Proposed

    • GMF-Tooling should switch back to standard templates language [386838] (target milestone: 3.1)
    • GMF-T should generate code aligned with API deprecation status of Juno/Kelper [386835] (target milestone: 3.1)
    • Migrate GMF Tooling site to http://www.eclipse.org/gmf-tooling/ [380998] (target milestone: 3.1)
  • Deferred

    • Graphiti-specific GenModel and templates for GMF-Tooling [386824] (target milestone: 3.1)
    • Consider back-porting custom developed features from Eclipse GMFT implementations [388851] (target milestone: 3.1M6)
    • Consider using XCore for GMF Tooling models [390313] (target milestone: 3.1)

Design for Extensibility

  • Proposed

    • GMF-Tooling to support runtime platforms alternative to GMF-Runtime [386821] (target milestone: 3.1)
  • Deferred

    • Allow DI-based customization of the generated code [390319] (target milestone: 3.1M4)
    • Split GMFGen model into the core- and platform-specific parts [386822] (target milestone: 3.1)

Ease Of Use

  • Proposed

    • GMFT to allow define dynamic behavior via GMFTool model [386834] (target milestone: 3.2)
    • Support GMFT toolsmith with ability to use debugger for codegen / M2M stages [390323] (target milestone: 3.2M4)
    • Support for diagrams with semantic properties directly mapped to graphical properties [386832] (target milestone: 3.2)
    • More icons-oriented features for GMF-T generated editors [388850] (target milestone: 3.2)
  • Deferred

    • Improve validation for GMFT input / codegen models [390317] (target milestone: 3.2)

Lower Entry Barrier

  • Proposed

    • Restructure GMF-Tooling examples [388803] (target milestone: 3.1)
    • GMFGraph preview editor [386830] (target milestone: 3.1)
    • GMF-Tooling bootstrapping -- visual editor for diagram definitions [386829] (target milestone: 3.1)

Table of Contents

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