Difference between revisions of "ATL/ReleaseReview/Juno"
(→Juno Release Highlights)
|Line 175:||Line 175:|
Revision as of 06:35, 5 June 2012
- 1 Juno Release Review - ATL 3.3
- 1.1 Juno Release Highlights
- 1.2 IP Issues
- 1.3 Non-Code Aspects
- 1.4 APIs
- 1.5 Documentation
- 1.6 Bugzilla
- 1.7 End of Life
- 1.8 Communities
- 1.9 Schedule
- 1.10 Project Plan
- 1.11 Legal Notices
Juno Release Review - ATL 3.3
Juno Simultaneous Release
Release Review and Graduation Review
William Piers (firstname.lastname@example.org)
Release Review : June, 2012
Process Documentation : http://www.eclipse.org/projects/dev_process/development_process.php
Juno Release Highlights
New and noteworthy
ATL 3.3 is compatible with Eclipse 3.4 (Ganymede), Eclipse 3.5 (Galileo), Eclipse 3.6 (Helios), Eclipse 3.7 (Indigo) and Eclipse 3.8/4.2 (Juno).
A new VM for ATL (EMFTVM), but also other rule-based transformations languages, that incorporates composition (rule inheritance, module superimposition) as an integral part.
Quality of APIs
The component lead certifies that the requirements for Eclipse Quality APIs have been met for this release. All non-API code is in "internal" packages.
End of Life Issues
3 Committers from Obeo, 1 from INRIA and 2 individual committers. William Piers is now co-lead on the project with Frédéric Jouault.
The about files and use licenses are in place as per the Guidelines to Legal Documentation.
All other contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy. The other contributions of the IP log are not significant or are written 100% by employees of the same employer (Obeo) as the Submitting Committer (http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf).
All contribution Questionnaires have been completed.
The "provider" field of each plugin is set to "Eclipse Modeling Project".
The "copyright" field of each plugin is set to the copyright owner.
Any third-party logos or trademarks included in the distribution (icons, logos, etc) have been licensed under the EPL.
The ATL IP log is located at http://www.eclipse.org/projects/ip_log.php?projectid=modeling.mmt.atl
ATL releng system recently moved to the common Hudson build server and uses Tycho to build.
Non-regression tests covers most of the Core part of ATL. ATL transformation engines, compilers, parser, formatter are covered by those tests. ATL uses EMFCompare to check model results.
Checkstyle activated on each distinct plug-in.
Yourkit used on a regular basis to improve performances.
Metamodel definitions and interfaces are considered APIs.
APIs provide access to programmatic launch of ATL components (transformation engine, parser, compiler).
The documentation that comes with ATL 3.3 is available in the Help menu : ATL Model To Text Transformation Language.
The documentation is also fully available on the wiki http://wiki.eclipse.org/ATL. The main sections are:
- ATL User Guide: a complete description of the tooling and the ATL language
- ATL Developer Guide: a more specific description of API
The wiki documentation is converted to the ATL eclipse help plugin using Mylyn Wikitext.
ATL also provide an example and a cheatsheet.
Note : these figures are subject to changes as the whole team is in the process of fixing bugs until the final release (this snapshot has been taken on June 1, 2012)
End of Life
There are no specific end of life concerns for this release.
The ATL newsgroup (eclipse.atl) is still very active.
ATL 3.3 Release Plan
- Final 06/27/2012
- RC4 06/12/2012
- RC3 06/05/2012
- RC2 05/29/2012
- RC1 05/22/2012
The schedule used is matching the schedule of the release train for "+2" projects.
The Juno project plan is available at http://www.eclipse.org/projects/project-plan.php?projectid=modeling.mmt.atl
Java and all Java-based trademarks are trademarks of Oracle, Inc. in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.