Location: http://www.eclipse.org/modeling/amalgam/project-info/plan-juno.xml
Meta-data Tag: projectplanurl
Raw:

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml">
   <release projectid="modeling.amalgam" version="1.1.0"/>
   <introduction>
     <html:p>This document lays out the feature and API set for the first release of the Modeling Amalgamation Project, version 1.1.0.  This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.</html:p>
   </introduction>
   <release_deliverables>
     <html:p>Amalgam is different than most Eclipse projects in that its deliverables are EPP and product-based builds of several Modeling projects.  While some UI and integration code is provided, it is not made available in the traditional runtime, SDK, doc, etc. individual downloads.</html:p>
    </release_deliverables>
   <release_milestones>
      <preamble>
      	<html:p>Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 3 weeks; that is, until the final 3.5 release of the Platform, upon which Amalgam and other projects will release simultaneously. As Amalgam is dependent upon the EMF, GMF, and other Modeling projects, which are scheduled to release milestones within 3 weeks of Platform milestones, Amalgam will deliver its milestones within the following week. Amalgam is part of Juno and is synchronized with it.</html:p>
      </preamble>
      <milestone date="09/30/2011" milestone="M2"><html:div></html:div></milestone>
      <milestone date="11/11/2011" milestone="M3"><html:div></html:div></milestone>
      <milestone date="12/16/2011" milestone="M4"><html:div></html:div></milestone>
      <milestone date="02/03/2012" milestone="M5"><html:div></html:div></milestone>
      <milestone date="03/23/2012" milestone="M6"><html:div>API Freeze</html:div></milestone>
      <milestone date="05/11/2012" milestone="M7"><html:div>Feature Freeze</html:div></milestone>
      <milestone date="05/25/2012" milestone="RC1"><html:div></html:div></milestone>
      <milestone date="06/01/2012" milestone="RC2"><html:div></html:div></milestone>
      <milestone date="06/08/2012" milestone="RC3"><html:div></html:div></milestone>
      <milestone date="06/15/2012" milestone="RC4"><html:div></html:div></milestone>
      <milestone date="06/27/2012" milestone="Final"><html:div></html:div></milestone>
      <postamble></postamble>
   </release_milestones>
   <target_environments>
     <html:p>In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments.
The Amalgam project depends upon on the Platform and other projects, which are mostly "pure" Java. The 4.2 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. Amalgam will target the same Java version as EMF and other Modeling projects, which currently require Java 5.
Eclipse Platform SDK 4.2 will be tested and validated on a number of reference platforms. Amalgam will be tested and validated against a subset of those listed for the platform. Those available will be presented on the project download site.</html:p>
     <internationalization>
       <html:p>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 Amalgam project will provide English strings in its default bundles and be localized to a subset of those locales offered by the Platform and provided by the Babel project. This plan will be updated to indicate which locales will be provided and the time frame for availability.</html:p>
     </internationalization>
   </target_environments>
   <compatibility_with_previous_releases>
     <html:p>As this is the first release of Amalgam, no compatibility issues exist.</html:p>
   </compatibility_with_previous_releases>
   <themes_and_priorities>
     <preamble>
       <html:p>A list of project requirements and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to indicate what major set of functionalities is to be concentrated on for each. These themes are presented below, while the requirements document and associated Bugzilla entries are left to those wanting more detailed information on each.</html:p>
     </preamble>
     <theme name="Usability">
        <description><html:p>As one of the main purposes of Amalgam is to improve usability of Modeling technologies from Eclipse, it is a major theme for this and subsequent releases. This release is focused on providing a consummable modeling package and federating Eclipse Modeling Projects through a discovery UI integrated in the package.</html:p></description>      
     </theme>     
   </themes_and_priorities>
 </plan>