Project Plan For Model-to-Model Transformation (M2M), version 3.0
Introduction
This document lays out the feature and API set for the
3.0 release of the ATL project, of the Eclipse M2M Project.
Release Deliverables
The release deliverables have the same form as is found in most Eclipse projects, namely:
- ATL source code release, available as versions tagged "R3_0" in the project's CVS repository.
- M2M ATL SDK (includes runtime and tooling components, with sources and documentation) (downloadable and update site).
- M2M ATL runtime binary distribution (downloadable and update site).
- M2M ATL examples (downloadable and update site).
- M2T ATL tests (downloadable and update site).
Release Milestones
Release milestones occur at roughly 6 week intervals and follow the Platform release milestone by the Galileo-established +2 delta interval. ATL will synchronize its release milestones with the Galileo release schedule until the M4 date.
| M4 | 12/29/2008 | |
| M5 | 02/06/2009 | |
| M6 | 03/18/2009 | API freeze |
| M7 | 05/05/2009 | |
| RC1 | 05/19/2009 | |
| RC2 | 05/26/2009 | |
| RC3 | 06/02/2009 | |
| RC4 | 06/09/2009 | |
| RC5 | 06/16/2009 | |
| 3.0 | 06/28/2009 |
ATL produce maintenance releases to align with the Ganymede
Service
Releases
which includes the Eclipse Platform's 3.4.1
and 3.4.2
releases. Maintenance releases will only be published if they
contain new fixes.
Target Environments
In order to remain current, each Eclipse release targets
reasonably
current versions of the underlying operating environments.
The ATL
project depends upon on the Platform and other projects, which
are
mostly "pure" Java. 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. ATL will target the same Java version
as 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 ATL 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
We plan to change the API in the ATL 3.0 release but the
ATL language compatibility will be preserved.
Themes and Priorities
ATL 3.0 new features
Here is a list of the features we plan to integrate into the ATL
3.0 release.
- Transformation launch API refactoring
- Transformation launch UI improvement
- New In-place model transformation mode
- ATL transformation profiler integration
- Documentation and example refactoring
- Execution errors traceability improvement
- ATL UI improvement
- ATL debugger improvement
- Transformation plugins export feature
- Advanced UML profiles management
Appendix Project Refactoring
The ATL 3.0 release consists on a refactoring of the
current 2.0 version, in order to integrate new features
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.
