Project Plan For
, version 3.3.0

This document lays out the feature and API set for the 3.3.0 release of the M2T Acceleo project.
The Acceleo component is an open source component under the Eclipse Modeling / Model-To-Text (M2T) project.
Its primary goal is to provide an implementation of the MOF Model-To-Text OMG standard.
The Juno release of Acceleo introduces some new APIs and is labeled 3.3.0.

The implementation will be compliant with the advanced feature compliance level of the MOF Model-To-Text OMG language (No Macro and alternative syntax).
The milestones for this release of Acceleo will be synchronized with the Indigo release schedule.

The acceleo project depends upon the Platform and other projects, which are mostly "pure" Java.
Acceleo 3.3.0 will be compatible with Eclipse Ganymede, Galileo, Helios, Indigo and Juno.
EMF is used throughout Acceleo both for its inner mechanics and accessing the target models.
The MDT-OCL component is reused to edit, parse, and interpret OCL as a sub-language of Acceleo.
Acceleo will target the same Java version as EMF, which currently requires Java 5. It will also be tested
on the latest release of Java 6 and Java 7. Acceleo will be tested and validated against Eclipse SDK 3.4.2,
3.5.2, 3.6.2, 3.7.2, 3.8.0 and 4.2.0.

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. Likewise, the
Acceleo 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.

API compatibility. Acceleo 3.3 will be compatible with the extension points defined
in Acceleo 3.0, 3.1 and 3.2 but some Java APIs may be deprecated and replaced with new APIs.

Workspace compatibility. A workspace being used with Acceleo 3.0, 3.1 or 3.2
will still open and work with Acceleo 3.3. In general, though, once a workspace is opened with Acceleo 3.3
there is no guarantee it will continue to work with older versions (that is, there may be some one-time
migration of some workspace meta data that prevents it being usable in older versions.

Project compatibility. A project being used with Acceleo 3.0, 3.1 or 3.2
will stay compatible with Acceleo 3.3.