blob: 413ab4ba511073bba6030ca1f8b20e16f24e0e9a [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan plan-format="1.0" xmlns="http://www.eclipse.org/project/plan"
xmlns:html="http://www.w3.org/1999/xhtml" name="Project Name">
<release projectid="modeling.emf" version="1.6.0" />
<introduction>
<html:div>
<html:p>
This document lays out the feature and API set for the seventh
release of
the EMF Model Query (EMF Query) Project, version 1.6.0.
This project
plan inherits from the Modeling Project Plan, which
should be
referenced when consulting this individual project plan.
</html:p>
<html:p>
The intent for this release is to drive development by
community contributions. No new features are planned by the project
committers, but patches from the community will be processed as
efficiently as possible.
</html:p>
</html:div>
</introduction>
<release_deliverables>
<html:div>
The release deliverables have the same form as is found in most
Eclipse projects, namely:
<html:ul>
<html:li>EMF Query source code release, available as versions tagged
"R1_6" in the project's CVS repository.</html:li>
<html:li>EMF Query SDK (includes runtime, sources, examples, and
documentation) (downloadable and update site).</html:li>
<html:li>EMF Query runtime binary distribution (downloadable and
update site).</html:li>
<html:li>EMF Query tests (downloadable)</html:li>
</html:ul>
</html:div>
</release_deliverables>
<release_milestones>
<preamble>
<html:div>
Release milestone occurring at roughly 6 week intervals and
follow the Platform milestone releases by approximately 1 week; that
is, until the final 4.2 release of the Platform, upon which EMF
Query and other projects will release simultaneously. It is
anticipated that EMF Query will synchronize its milestones with the
Juno milestone schedule
</html:div>
</preamble>
<milestone date="08/20/2011" milestone="M1"></milestone>
<milestone date="10/01/2011" milestone="M2"></milestone>
<milestone date="11/12/2011" milestone="M3"></milestone>
<milestone date="12/17/2011" milestone="M4"></milestone>
<milestone date="02/04/2012" milestone="M5"></milestone>
<milestone date="03/18/2012" milestone="M6">
<html:p>API freeze</html:p>
</milestone>
<milestone date="05/20/2012" milestone="M7">
<html:div>Feature Freeze</html:div>
</milestone>
<milestone date="05/20/2012" milestone="RC1"></milestone>
<milestone date="05/25/2012" milestone="RC2"></milestone>
<milestone date="06/03/2012" milestone="RC3"></milestone>
<milestone date="06/10/2012" milestone="RC4"></milestone>
<milestone date="06/22/2012" milestone="RC5"></milestone>
<milestone date="06/22/2012" milestone="1.6.0"></milestone>
<postamble>
<html:div>
EMF Query will produce maintenance releases to align with the Juno
SR releases, that includes the Eclipse Platform 4.2.1 and 4.2.2
releases. EMF Query may produce interim maintenance releases in
addition to these in order to satisfy client’s requests. Maintenance
releases will only be published if they have any new fixes to offer
<html:ul>
<html:li>Friday, September 30, 2012 (last Friday of September) -
EMF Query 1.6.1 maintenance release (if necessary)</html:li>
<html:li>Friday, February 24, 2013 (last Friday of February) - EMF
Query 1.6.2 maintenance release (if necessary)</html:li>
<html:li>A list of issues indicated for the 1.6.x maintenance
stream can be found in bugzilla, or by using links on maintenance
stream build pages.</html:li>
</html:ul>
</html:div>
</postamble>
</release_milestones>
<target_environments>
<html:div>
In order to remain current, each Eclipse release targets reasonably
current versions of the underlying operating environments. The EMF
Query project depends upon on the Platform and other projects, which
are mostly "pure" Java
<html:sup>TM</html:sup>
. The 4.2
release of the Eclipse Platform Project is written and
compiled
against version 1.5 of the Java Platform APIs, and targeted
to run on version 1.5 of the Java Runtime Environment, Standard
Edition. EMF Query will target the same Java version as EMF Core,
which
currently requires Java 5. Eclipse Platform SDK 4.2 will be
tested and
validated on a number of reference platforms. EMF Query
will be tested
and validated against a subset of those listed for the
platform.
</html:div>
<internationalization>
<html:div>
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 EMF Query 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
</html:div>
</internationalization>
</target_environments>
<compatibility_with_previous_releases>
<html:div>
Compatibility of Release 1.6: The EMF Query project will be developed
in parallel, and released simultaneously, with the following
projects. As stated above, each milestone release of the EMF Query
project will be compatible with the corresponding milestones for each
of these projects, and delivered the appropriate offset.
<html:ul>
<html:li>Eclipse Platform SDK version 4.2</html:li>
<html:li>Eclipse Modeling Framework (EMF) version 2.8</html:li>
<html:li>Eclipse MDT OCL version 3.2</html:li>
<html:li>Eclipse MDT UML2 version 4.0</html:li>
</html:ul>
Therefore, the EMF Query initial release will be compatible with
these versions and will publish binary and source compatibilities
with migration guides on subsequent releases.
</html:div>
</compatibility_with_previous_releases>
<themes_and_priorities>
<preamble>
<html:div>
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:div>
</preamble>
<theme name="Eclipse 3.8">
<description>
<html:div>
No support, no testing on 3.8
</html:div>
</description>
</theme>
<theme name="Community Responsiveness">
<description>
<html:div>
The EMF Query project remains committed to accepting
contributions of new features from the community at large. Bugzilla
items with patches are encouraged, but other items may be
considered at the committers' discretion, according to their
availability.
</html:div>
</description>
<committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;field0-0-0=attachments.ispatch&amp;type0-0-0=equals&amp;value0-0-0=1&amp;classification=Modeling&amp;product=EMF&amp;component=Query&amp;target_milestone=RC&amp;target_milestone=M1&amp;target_milestone=M2&amp;target_milestone=M3&amp;target_milestone=M4&amp;target_milestone=M5&amp;target_milestone=M6&amp;target_milestone=M7&amp;keywords_type=allwords&amp;keywords=plan&amp;bug_status=NEW&amp;bug_status=ASSIGNED">
</committed>
<proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;field0-0-0=attachments.ispatch&amp;type0-0-0=equals&amp;value0-0-0=1&amp;classification=Modeling&amp;product=EMF&amp;component=Query&amp;target_milestone=Juno&amp;keywords_type=allwords&amp;keywords=plan&amp;bug_status=NEW&amp;bug_status=ASSIGNED">
</proposed>
<deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;field0-0-0=attachments.ispatch&amp;type0-0-0=equals&amp;value0-0-0=1&amp;classification=Modeling&amp;product=EMF&amp;component=Query&amp;target_milestone=---&amp;keywords_type=allwords&amp;keywords=plan&amp;bug_status=NEW&amp;bug_status=ASSIGNED">
</deferred>
</theme>
</themes_and_priorities>
<appendix name="A: Legal Notices">
<html:div>
<html:ul>
<html:li>Java is a trademark or a registered trademark of Sun
Microsystems, Inc.</html:li>
<html:li>All other products or company names are mentioned for
identification purposes only, and
may be trademarks or service marks
of their respective owners.
</html:li>
</html:ul>
</html:div>
</appendix>
</plan>