Location: http://www.eclipse.org/gef/plan/gef_plan_3_7.xml
Meta-data Tag: projectplanurl
Raw:
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="tools.gef" version="3.7.0" />
<introduction>
<html:p>This document lays out the feature and API set for the
next
feature release of the Graphical Editing Framework (GEF)
project,
designated release 3.7.0. The GEF Project is comprised of the GEF, Draw2d and Zest components.</html:p>
</introduction>
<release_deliverables>
<html:p>
The release deliverables are:
<html:ul>
<html:li>
GEF source code for the release is available in the eclipse.org
<html:a
href="http://dev.eclipse.org/viewcvs/index.cgi/?cvsroot=Tools_Project">CVS
repositories</html:a>
.
</html:li>
<html:li>GEF runtime binaries and SDK distributions
(downloadable).
</html:li>
<html:li>GEF runtime binaries and SDK features on eclipse.org
update
site
(install via Eclipse update manager).</html:li>
</html:ul>
</html:p>
</release_deliverables>
<release_milestones>
<preamble>
<html:p>
GEF builds are available weekly as Integration builds. GEF
Milestone
Releases are approximately one week after the
Eclipse Milestone
Releases. It is anticipated that GEF will synchronize its
release
milestones with the
<a href="http://wiki.eclipse.org/index.php/Indigo_Simultaneous_Release">
Indigo release schedule
</a>
.
</html:p>
</preamble>
<milestone date="08/16/2010" milestone="M1"></milestone>
<milestone date="09/27/2010" milestone="M2"></milestone>
<milestone date="11/08/2010" milestone="M3"></milestone>
<milestone date="12/13/2010" milestone="M4"></milestone>
<milestone date="01/31/2011" milestone="M5"></milestone>
<milestone date="03/14/2011" milestone="M6"><html:p>API freeze</html:p></milestone>
<milestone date="05/02/2011" milestone="M7"><html:p>Feature Freeze</html:p></milestone>
<milestone date="05/16/2011" milestone="RC1"></milestone>
<milestone date="05/23/2011" milestone="RC2"></milestone>
<milestone date="05/30/2011" milestone="RC3"></milestone>
<milestone date="06/06/2011" milestone="RC4"></milestone>
<milestone date="06/13/2011" milestone="Final"></milestone>
<milestone date="06/22/2011" milestone="Indigo GA"></milestone>
</release_milestones>
<target_environments>
<html:p>
GEF 3.7 will support all operating environments supported by the
Eclipse
Platform itself. For a list of supported environments, refer
to the Target Environments list in the
<html:a
href="http://www.eclipse.org/projects/project-plan.php?projectid=eclipse.platform">
Eclipse Project 3.7 plan</html:a>
</html:p>
</target_environments>
<compatibility_with_previous_releases>
<html:p>GEF 3.7 will be upwards compatible with GEF 3.6 to the
greatest
extent
possible. Any exceptions will be noted in the 3.7
release notes so that
clients
can assess the impact of these changes on
their plug-ins and products.</html:p>
<html:p>
<html:b>API Contract Compatibility:</html:b>
GEF 3.7 will be upwards
contract-compatible with GEF 3.6 unless noted.
This means that programs in full
compliance with contracts specified
in 3.6 APIs will automatically be
in full
compliance with 3.7 APIs.
Refer to
<html:a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs"> Evolving
Java-based APIs</html:a>
for a discussion of the kinds of API changes that maintain
contract
compatibility.
</html:p>
<html:p>
<html:b>Binary (plug-in) Compatibility:</html:b>
GEF 3.7 will be upwards binary-compatible with GEF 3.6 unless noted.
This means that plug-ins built for GEF 3.6 will continue to work
correctly in 3.7 without change. Plug-ins with hard-coded references
in
their plug-in manifest file to the 3.6 version of GEF
plug-ins will
work in 3.7 provided the version match rule is
"greaterOrEqual" or
"compatible" (the default); references using "perfect" or
"equivalent" match
rules will be broken. Refer to
<html:a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs"> Evolving
Java-based APIs</html:a>
for a discussion of the kinds of API changes that maintain
binary
compatibility.
</html:p>
<html:p>
<html:b>Source Compatibility:</html:b>
GEF 3.7 will be upwards source-compatible
with GEF 3.6 to the greatest
extent possible. This means that source
files
written to use 3.6 APIs
can often be successfully compiled and run against
GEF
3.7 APIs. Since
source incompatibilities are easy to deal with,
maintaining
source
compatibility is considered much less important than maintaining
contract
and binary compatibility. The addition of a single method
anywhere could
be an incompatible source change. For this reason,
source-incompatibilities will not be noted.
</html:p>
<html:p>
<html:b>Non-compliant usage of API's</html:b>
: All non-API methods and classes, and
certainly everything in a
package with "internal" in its name, are considered
implementation
details which may vary between operating environment
and are
subject to
change without notice. Client plug-ins that directly depend on
anything other than what is specified as API are inherently
unsupportable and
receive no guarantees about compatibility within a
single release much less
with
an earlier releases. Refer to
<html:a
href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">
How to Use the Eclipse API</html:a>
for information about how to write compliant
plug-ins.
</html:p>
<html:p>
<html:b>Ramp Down Policy</html:b>
</html:p>
<html:p>
The GEF project uses the <html:a href="http://wiki.eclipse.org/Modeling_Project_Ramp_Down_Policy/Indigo">Modeling Project Ramp Down Policy/Indigo</html:a>
following EMF as a 1+ component.
</html:p>
</compatibility_with_previous_releases>
<themes_and_priorities>
<preamble>
<html:p>
The project has identified major areas of work, that
will be the
priorities for this development cycle.
</html:p>
</preamble>
<theme name="Consumability">
<description>
<html:p>This work will make it easier to make effective use of
the
GEF components. We seek to deliver enhancements and
defect
fixes that are important for our consumers.
A list of
those plan items related to Consumability can be found by searching
Bugzilla for flag=Indigo.
</html:p>
</description>
<committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=substring&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=Indigo&field0-1-0=flagtypes.name&type0-1-0=notsubstring&value0-1-0=Indigo-&field0-2-0=target_milestone&type0-2-0=notequals&value0-2-0=---">
</committed>
<proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&target_milestone=---&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=substring&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=substring&value0-0-0=Indigo&field0-1-0=flagtypes.name&type0-1-0=notsubstring&value0-1-0=Indigo-">
</proposed>
<deferred
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=Indigo-">
</deferred>
</theme>
</themes_and_priorities>
</plan>