project-info/plan.xml

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
  <!--  Use this to test local rendering in firefox -->
  <!--  <?xml-stylesheet type="text/xsl" href="project-plan-render.xsl"?>  -->
<?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"
  name="EPP"
  plan-format="1.0">
  <release
    projectid="technology.packaging"
    version="1.1"></release>
  <introduction>
    <html:p>The Eclipse Packaging Project (EPP) is responsible for creating technology that makes
      it easier for new users to consume the output of other Eclipse projects and for coordinating
      the package releases together with the yearly release train. In order to achieve this goal,
      EPP is active on different levels since the Europa Release 2007:</html:p>
    <html:ul>
      <html:li>
        <html:b>Create entry level downloads based on defined user profiles.</html:b>
        The project defined and created the EPP downloads of Java Developer, Java EE Developer,
        C/C++ Developer and RCP Developer. These downloads are available from the main Eclipse
        download page. In addition to that, EPP coordinates with other package maintainers the
        creation of new package definitions and ensures that the packages are tested.
      </html:li>
      <html:li>
        <html:b>Provide and integrate the EPP Usage Data Collector.</html:b>
        The Usage Data Collector collects information about how individuals are using the Eclipse
        platform. The intent is to use this data to help committers and organizations better
        understand how developers are using Eclipse.
      </html:li>
      <html:li>
        <html:b>Provide a platform that allows the creation of packages (zip/tar downloads)
          from an update site.</html:b>
        The core technology of the project will enable the creation of download packages that are
        created by bundling Eclipse features from one or multiple Eclipse update sites.
      </html:li>
      <html:li>
        <html:b>Create and manage a new dynamic installer.</html:b>
        EPP creates a new RAP-based wizard that enables a user to choose and pick software
        components from other Eclipse projects. The output is a customized p2-installer that guides
        the user through the initial install process and downloads the necessary software
        components.
      </html:li>
    </html:ul>
  </introduction>
  <release_deliverables/>
  <release_milestones>
    <preamble>
      <html:p>All EPP releases appear simultaneously with the release train releases (here:
        Galileo).</html:p>
    </preamble>
    <milestone
      milestone="Galileo M1 - no EPP builds"
      date="n/a"/>
    <milestone
      milestone="Galileo M2 - no EPP builds"
      date="n/a"/>
    <milestone
      milestone="Galileo M3 - to be discussed: EPP builds necessary?"
      date="n/a"/>
    <milestone
      milestone="Galileo M4"
      date="2009-01-08"/>
    <milestone
      milestone="Galileo M5"
      date="2009-02-12"/>
    <milestone
      milestone="Galileo M6"
      date="2009-03-20"/>
    <milestone
      milestone="Galileo M7"
      date="2009-05-08">
      <html:p>All packages must be defined and their content must be specified.</html:p>
    </milestone>
    <milestone
      milestone="Galileo RC1"
      date="2009-05-21"/>
    <milestone
      milestone="Galileo RC2"
      date="2009-05-28"/>
    <milestone
      milestone="Galileo RC3"
      date="2009-06-04"/>
    <milestone
      milestone="Galileo RC4"
      date="2009-06-11"/>
    <milestone
      milestone="Galileo RC5"
      date="2009-06-18"/>
    <postamble/>
  </release_milestones>
  <target_environments>
    <html:p>EPP creates its packages for Windows 32-bit, Linux 32-bit, Linux 64-bit and Mac OSX.
      All of the packages require at least a JVM 1.5 because of the software components that are
      included in the packages.</html:p>
    <html:p>Source code used and developed within the project needs a JVM 1.5 or higher.
    </html:p>
    <internationalization/>
  </target_environments>
  <compatibility_with_previous_releases/>
  <themes_and_priorities>
    <preamble/>
    <theme
      name="Galileo Packages">
      <description>
        <html:p>EPP will create and deliver the packages for the next release train. The exact
          content and the number of packages are subject to change and depend on the community
          feedback and help.</html:p>
      </description>
      <committed>
        <html:p>Galileo Packages</html:p>
        <html:ul>
          <html:li>Eclipse IDE for Java EE Developers</html:li>
          <html:li>Eclipse IDE for Java Developers</html:li>
          <html:li>Eclipse IDE for C/C++ Developers</html:li>
          <html:li>Eclipse Modeling Tools</html:li>
          <html:li>Eclipse for RCP/Plug-in Developers</html:li>
          <html:li>Eclipse IDE for Java and Report Developers</html:li>
        </html:ul>
      </committed>
    </theme>
    <theme
      name="Dynamic Package Delivery Component">
      <description>
        <html:p> The dynamic package delivery component provides an extensible framework for, and an
          exemplary implementation of, a service for dynamically selecting and
          downloading/installing installable units.</html:p>
      </description>
      <committed>
        <html:p>Preview available for Friends-of-Eclipse.</html:p>
      </committed>
    </theme>
  </themes_and_priorities>
  <appendix/>
</plan>