Skip to main content
Location: /localsite//mmt/atl/project-info/plan.xml
Meta-data Tag: projectplanurl

	<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href=""?>
<plan plan-format="1.0" xmlns="" xmlns:html=""
	<release projectid="modeling.mmt.atl" version="3.3.0" />
		<html:div>This document lays out the feature and API set for the
			3.3 release of the ATL project, of the Eclipse MMT Project.
			The release deliverables are the following:
				<html:li>ATL source code release, available as versions tagged
					"R3_3" in the project's CVS repository.</html:li>
				<html:li> ATL SDK (includes runtime and tooling components,
					with sources and documentation) (downloadable and update site).
				<html:li> ATL runtime binary distribution (downloadable and
					update site).</html:li>
				<html:li> ATL examples (downloadable and update site).
				<html:li> ATL EMFTVM, an ATL VM dedicated to composed transformations (downloadable and update site).
Release milestones occur at roughly 6 week intervals 
and follow the Platform release milestone by the Juno-established +2 delta interval.
The final ATL 3.3 release will available simultaneously 
with the 3.8 release of the Platform and all the other Helios projects.
<milestone date="09/27/2011" milestone="M2"></milestone>
<milestone date="11/08/2011" milestone="M3"></milestone>
<milestone date="12/13/2011" milestone="M4"></milestone>
<milestone date="01/31/2012" milestone="M5"></milestone>
<milestone date="03/20/2012" milestone="M6"><html:div>API freeze</html:div></milestone>
<milestone date="05/08/2012" milestone="M7"><html:div>Feature Freeze</html:div></milestone>
<milestone date="05/22/2012" milestone="RC1"></milestone>
<milestone date="05/29/2012" milestone="RC2"></milestone>
<milestone date="06/05/2012" milestone="RC3"></milestone>
<milestone date="06/12/2012" milestone="RC4"></milestone>
<milestone date="06/27/2012" milestone="Final"></milestone>
ATL will produce maintenance releases to align with the Helios Service Releases
which includes the Eclipse Platform's 3.7.1 and 3.7.2 releases.
ATL may produce additional interim maintenance releases.  
Maintenance releases will only be published if they contain new fixes.
Friday, September 23, 2011 - ATL 3.2.1 maintenance release for Indigo Service Release 1.
Friday, February 24, 2012 - ATL 3.2.2 maintenance release for Indigo Service Release 2.
Version numbers are subject to change should there be be any additional maintenance releases.
			In order to remain current, each Eclipse release targets
			current versions of the underlying operating environments.
			The ATL
			project depends upon on the Platform and other projects, which
			mostly "pure" Java. The 3.5 release of the Eclipse Platform
			is written and compiled against version 1.4 of the Java
			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.
				The Eclipse Platform is designed as the basis for
				products. The user interface elements provided by
				the Eclipse SDK
				components, including dialogs and error messages, are
				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
				offered by the Platform. This plan will be updated to
				indicate which
				locales will be provided and the time frame for
		<html:div>Most of the 3.2 APIs will be compatible with ATL 3.3.</html:div>
     	<theme name="Support for Eclipse 3.8 workbench">
     		We will support 3.8 and 4.2 equally, and all the functionality will be the same.
		<theme name="ATL EMFTVM">
			A new VM for ATL (EMFTVM), but also other rule-based transformations languages, that incorporates composition (rule inheritance, module superimposition) as an integral part.

Back to the top