blob: c30fbfb76fa6788362d8f23f481d0dda4bc32b60 [file] [log] [blame]
<?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"?>
<p:plan
plan-format="1.0"
xmlns:p="http://www.eclipse.org/project/plan" xmlns="http://www.w3.org/1999/xhtml"
name="e4 Project">
<p:release projectid="eclipse.e4" version="0.9"/>
<!-- ============================================== -->
<p:introduction>
<div>
<p>
Last revised 16:00 ET July 13, 2009 (<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> marks
interesting changes since the previous draft of Feb 2, 2009)
</p>
<p><i>Please send comments about this plan to the</i> <a href="mailto:e4-dev@eclipse.org">e4-dev@eclipse.org</a> <i>developer
mailing list.</i>
</p>
<p>This document lays out the feature and API set for the first feature release
of the Eclipse e4 project, designated release 0.9.
</p>
<p>Plans do not materialize out of nowhere, nor are they entirely static. To
ensure the planning process is transparent and open to the entire Eclipse community,
we (the e4 team) post plans in an embryonic form and revise them
throughout the release cycle. </p>
<p>The first part of the plan deals with the important matters of release deliverables,
release milestones, target operating environments, and release-to-release compatibility.
These are all things that need to be clear for any release, even if no features
were to change. </p>
<p>The remainder of the plan consists of plan items for all of the component areas
under the e4 Project. Each plan item covers a feature or API
that is to be added to the e4 Project deliverables, or some aspect of
the e4 Project that is to be improved. Each plan item has its own entry
in the Eclipse bugzilla database, with a title and a concise summary (usually
a single paragraph) that explains the work item at a suitably high enough level
so that everyone can readily understand what the work item is without having
to understand the nitty-gritty detail. </p>
<p>Not all plan items represent the same amount of work; some may be quite large,
others, quite small. Some plan items may involve work that is localized to
a single component; others may involve coordinated changes to several components;
other may pervade the entire project. Although some plan items are for work that
is more pressing than others, the plan items appear in no particular order. </p>
<p>Fixing bugs, improving test coverage, documentation,
examples, performance tuning, usability, etc. are considered routine ongoing
maintenance activities and are not included in this plan unless they would
also involve a significant change to the API or feature set, or involve a significant
amount of work. The intent of the plan is to account for all interesting feature work. </p>
<p>The current status of each plan item is noted: </p>
<ul>
<li><b>Committed</b> plan item - A committed plan item is one that we have
decided to address for the release.</li>
<li><b>Proposed</b> plan item - A proposed plan item is one that we are considering
addressing for the release. Although we are actively investigating it, we
are not yet in a position to commit to it, or to say that we won't be able
to address it. After due consideration, a proposal will either be committed
or deferred.</li>
<li><b>Deferred</b> plan item - A reasonable proposal that will not make it
in to this release for some reason is marked as deferred with a brief note
as to why it was deferred. Deferred plan items may resurface as committed
plan items at a later point.</li>
</ul>
</div>
</p:introduction>
<!-- ============================================== -->
<p:release_deliverables>
<div>
<p>The complete set of release deliverables for the e4 project have not yet been determined.
However, deliverables will include:</p>
<ul>
<li>Source code release for all e4 Project deliverables, available as
versions tagged &quot;R0_9&quot; in the e4 Project <a href="http://dev.eclipse.org/viewcvs/">CVS
repository</a>.</li>
<li>e4 master zip (downloadable). Contains all source code, e4 bundles in binary form,
and patches for applying portions of e4 onto an existing instance of the Eclipse Platform.</li>
</ul>
</div>
</p:release_deliverables>
<!-- ============================================== -->
<p:release_milestones>
<p:preamble><p>
Release milestones will be occurring at roughly 6 week intervals, and will generally occur
one week after an Eclipse project milestone.
</p>
</p:preamble>
<p:milestone date="02/06/2009" milestone="M1"><div>0.9M1</div></p:milestone>
<p:milestone date="03/20/2009" milestone="M2"><div>0.9M2</div></p:milestone>
<p:milestone date="05/08/2009" milestone="M3"><div>0.9M3</div></p:milestone>
<p:milestone date="06/26/2009" milestone="M4"><div>0.9M4</div></p:milestone>
<p:milestone date="07/10/2009" milestone="M5"><div>0.9M5 (Feature Freeze)</div></p:milestone>
<p:milestone date="07/17/2009" milestone="RC1"><div>0.9RC1</div></p:milestone>
<p:milestone date="07/24/2009" milestone="RC2"><div>0.9RC2</div></p:milestone>
<p:postamble>
<div>
<p>Our target is to complete 0.9 in late July 2009, one month after the Galileo release.
All release deliverables will be available for download as soon as the release has been
tested and validated in the target operating configurations listed below.</p>
</div>
</p:postamble>
</p:release_milestones>
<!-- ============================================== -->
<p:target_environments>
<div>
<p>In order to remain current, each e4 Project release targets reasonably current
operating environments.</p>
<p>Most of the e4 Project is &quot;pure&quot; Java code and has no direct dependence
on the underlying operating system. The chief dependence is therefore on the
Java Platform itself. Portions are targeted to specific classes of operating
environments, requiring their source code to only reference facilities available
in particular class libraries (e.g. J2ME Foundation 1.0, J2SE 1.3 and 1.4,
etc.). In general, the 0.9 release of the Eclipse Project is developed on Java SE 5.</p>
<p>e4 has dependencies on components from other Eclipse projects, notably the Platform
project, and the EMF project. While specific version dependencies may specify
a wider range, e4 is generally built and tested against the versions contained in the
Galileo release train.</p>
<p>There are many different implementations of the Java Platform running atop
a variety of operating systems. We focus our testing on a handful of
popular combinations of operating system and Java Platform; these are our <em>reference
platforms</em>. Eclipse undoubtedly runs fine in many operating environments
beyond the reference platforms we test. However, since we do not systematically test
them we cannot vouch for them. Problems encountered when running Eclipse on a
non-reference platform that cannot be recreated on any reference platform will
be given lower priority than problems with running Eclipse on a reference platform.</p>
<p>e4 also has dependencies on browser technologies such as Javascript and Flash. The
reference platforms listed below show the versions of these technologies that we
are developing and testing against.</p>
<p>e4 0.9 is tested and validated on the following reference platforms
(this list is updated over the course of the release cycle):</p>
<center>
<table border="1" cellpadding="2" cellspacing="2" width="80%" summary="Reference Platforms">
<tbody>
<tr align="center">
<td><b>Reference Platforms</b></td>
</tr>
<tr>
<td><b>Microsoft Windows Vista, x86-32, Win32</b> running (any of):
<ul>
<li>Sun Java Standard Edition 5 Update 14 for Microsoft Windows</li>
<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li>
</ul></td>
</tr>
<tr>
<td><b>Microsoft Windows XP, x86-32, Win32</b> running (any of):
<ul>
<li>Sun Java Standard Edition 5 Update 14 for Microsoft Windows</li>
<li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li>
</ul></td>
</tr>
<tr>
<td><b>Red Hat Enterprise Linux 5.0, x86-32, GTK</b> running (any of):
<ul>
<li>Sun Java Standard Edition 5 Update 14 for Linux x86</li>
<li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b</li>
</ul></td>
</tr>
<tr>
<td><b>Apple Mac OS X 10.5, Universal, Cocoa</b> running:
<ul>
<li>Apple Java for Mac OS X 10.5, Update 1</li>
</ul></td>
</tr>
</tbody>
</table>
</center>
<p>As stated above, <i>we expect that e4 works fine on other current
Java VM and OS versions but we cannot flag these as reference platforms without
significant community support for testing them.</i></p>
</div>
<p:internationalization>
<p>The e4 platform is designed as the basis for internationalized products. The
user interface elements provided by the e4 components, including dialogs
and error messages, are externalized. The English strings are provided as the
default resource bundles.</p>
<p>Latin-1 and DBCS locales are supported by e4 on all reference platforms;
BIDI locales are supported by e4 everywhere but on Motif.</p>
<p>e4 supports GB 18030 (level 1), the Chinese code page standard,
on Windows XP and 2000, Linux/GTK and the Macintosh.</p>
<p>German and Japanese locales are tested.</p>
</p:internationalization>
</p:target_environments>
<!-- ============================================== -->
<p:compatibility_with_previous_releases>
<div>
<h3>Compatibility of e4 0.9 with previous Eclipse project releases</h3>
<p>Portions of e4 will be compatible with Eclipse 3.5 (and all earlier 3.x versions).
However, compatibility is not a primary focus for this initial release of e4, and there
is no firm promise of compatibility between e4 and earlier Eclipse releases of any kind.
Compatibility with Eclipse 3.x is anticipated to be a major focus of the subsequent e4 release.
</p>
<p><strong>Workspace Compatibility:</strong> e4 0.9 will be upwards
workspace-compatible with ealier 3.x versions of the Eclipse SDK unless noted.
This means that workspaces and projects created with Eclipse SDK 3.4 .. 3.0 can be successfully
opened by e4 0.9 and upgraded to an e4 workspace. This includes both
hidden metadata, which is localized to a particular workspace, as well as metadata
files found within a workspace project (e.g., the .project file), which may
propagate between workspaces via file copying or team repositories. Individual
plug-ins developed for e4 0.9 should provide similar upwards compatibility
for their hidden and visible workspace metadata created by earlier versions;
0.9 plug-in developers are responsible for ensuring that their plug-ins recognize
metadata from earlier versions and process it appropriately. User
interface session state may be discarded when a workspace is upgraded. Downward
workspace compatibility is not supported. A workspace created (or opened) by
a product based on e4 0.9 will be unusable with a product based an earlier
version of Eclipse. Visible metadata files created (or overwritten) by e4 0.9
will generally be unusable with earlier versions of Eclipse. </p>
<p><strong>Non-compliant usage of API's</strong>: All non-API methods and classes,
and certainly everything in a package with &quot;internal&quot; 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 in the Eclipse SDK API are inherently
unsupportable and receive no guarantees about compatibility within a single
release much less with earlier releases. Refer to
<a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">
<em>How to Use the Eclipse API</em>
</a> for information about how to write compliant plug-ins. </p>
</div>
</p:compatibility_with_previous_releases>
<!-- ============================================== -->
<p:themes_and_priorities>
<p:preamble>
<div>
<p>The plan items listed below were defined according to contributor requirements and the Eclipse
<a href="http://wiki.eclipse.org/RequirementsCouncilThemesAndPriorities">Themes and Priorities</a>
set forth by the Eclipse Requirements Council. Each plan item covers a feature or API that is
to be added to the e4 Project deliverables, or some aspect of the e4 Project that is
to be improved. Each plan item has its own entry in the Eclipse bugzilla database, with a title
and a concise summary (usually a single paragraph) that explains the work item at a suitably
high enough level so that everyone can readily understand what the work item.</p>
<p> Although there are several components under the e4 project, there
is a significant amount of commonality and shared effort between them. In general,
many plan items involve coordinated changes to multiple components, and thus
attempting to separate the items into sections based on sub-project leads to
artificial distinctions between them. As such, this plan covers the work of all components
under the e4 Project.</p>
<p>Not all plan items represent the same amount of work; some may be quite
large, others, quite small. Although some plan items are for work that is
more pressing than others, the plan items appear in no particular order.
See the corresponding bugzilla items for up-to-date status information on
ongoing work and planned delivery milestones.</p>
<p>The current status of each plan item is noted:</p>
<ul>
<li><b>Committed</b> plan item - A committed plan item is one that we have
decided to address for the release. In bugzilla, this is reflected by
having a concrete target milestone assigned.</li>
<li><b>Proposed</b> plan item - A proposed plan item is one that we are
considering addressing for the release. Although we are actively
investigating it, we are not yet in a position to commit to it, or to say
that we won't be able to address it. After due consideration, a proposal
will either be committed or deferred. In bugzilla, such items are reflected
by having a target milestone "0.9" or "---" assigned.</li>
<li><b>Deferred</b> plan item - A reasonable proposal that will not make it in
to this release for some reason is marked as deferred with a brief note as
to why it was deferred. Deferred plan items may resurface as committed plan
items at a later point. In bugzilla, such items are reflected by having
a target milestone "Future" assigned.</li>
</ul>
</div>
</p:preamble>
<!-- ============================================== -->
<p:theme name="Design for Extensibility">
<p:description>
<p>Over the years the Eclipse platform has accumulated a large body of API,
resulting in a platform that is very powerful, but also very difficult for non-experts
to extend. This theme encompasses work to make the Eclipse platform much
easier to build applications and extensions upon.
</p>
</p:description>
<p:committed>
<ul>
<li>(<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> committed)
<strong>Support declarative definition of user-interfaces.</strong>
We will work with the community to identify and provide access to a best-of-breed
declarative mechanism for defining widget-based user-interfaces in Eclipse. [Platform UI, SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252648">252648</a>)</li>
<li>(<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> committed)
<strong>Model-based workbench.</strong>
The functionality of the Eclipse Workbench and IDE have grown significantly
since they were created. In some cases, older capabilities have been superceded
by newer ones or have been proven to be unwieldy or otherwise unsatisfying.
We will create a new model of the underlying structure of the Eclipse UI, which
will make development simpler, but more flexible and dynamic. [Platform UI]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id= 252650"> 252650</a>) </li>
<li>(<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> committed)
<strong>Skinnable UI.</strong>
We will enable developers to have greater control over the Eclipse UI,
making it simple to customize the appearance of Eclipse-based applications
using industry standard mechanisms such as CSS. [Platform UI, SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id= 252653"> 252653</a>) </li>
<li>(<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> committed)
<strong>Investigate scripting languages for Eclipse programmability.</strong>
We will investigate the use of scripting languages such as JavaScript, Ruby, etc.,
in Eclipse development. Since this capability will require function from the
model-based workbench, as well as support from the Equinox project, and
will potentially impact many other areas, only the initial investigation
is planned during the R3.5 cycle. [All]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252654">252654</a>)</li>
<li>(<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> committed)
<strong>Compatibility layer.</strong>
Although the 0.9 release will not itself be backward compatible with earlier versions
of the Eclipse platform, we will develop a compatibility layer that will allow
plug-ins built against earlier versions of the platform to run without modification
in e4. [All]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=XXXXXX">XXXXXX</a>)</li>
</ul>
</p:committed>
<p:proposed>
<p><i>None at this time.</i></p>
</p:proposed>
<p:deferred>
<p><i>None at this time.</i></p>
</p:deferred>
</p:theme>
<!-- ============================================== -->
<p:theme name="Rich Internet Applications">
<p:description>
<p>Eclipse is well-established as the cross-platform IDE of choice, but it has become
much more than that. The extensive and diverse range of applications that are being
built on the Eclipse code base, and the constantly changing capabilities of the
underlying systems on which it runs, are driving us to push the limits of our
technology in almost every dimension. In particular, there is increasing demand for an equivalent
of the Eclipse platform in the Rich Internet Application (RIA) space. Having a single
platform that can be used to build and run applications on a wide variety of web and desktop
technologies, would enable application writers to exploit a wide range of
deployment options from a common code base.</p>
</p:description>
<p:committed>
<ul>
<li>(<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> committed)
<strong>Support running SWT in a browser.</strong>
The RAP project has shown that it is possible to achieve good performance
and function for server-side, widget-based web applications. Investigations
have also been made into client-side technologies. Based on these efforts,
we will provide first-class support for the ability to run SWT applications
in web browsers. [SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252659">252659</a>)</li>
</ul>
</p:committed>
<p:proposed>
<p><i>None at this time.</i></p>
</p:proposed>
<p:deferred>
<ul>
<li>(<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> deferred)
<strong>Support advanced animation API in SWT.</strong>
A prototype API was developed during the R3.3 cycle that was implemented
on top of several desktop and web UI technologies. This work needs to be
completed. [SWT]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252656">252656</a>)</li>
</ul>
</p:deferred>
</p:theme>
<!-- ============================================== -->
<p:theme name="Ease of Use">
<p:description>
<p>The Eclipse IDE platform provides sufficient capabilities for a wide range of
developers, but has limitations that make it difficult to use as an IDE for certain kinds of development.
This theme encompasses work to make the Eclipse IDE easier to use for embedded,
C/C++, parallel, and server-side developer environments.</p>
</p:description>
<p:committed>
<ul>
<li>(<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12" /> committed)
<strong>Flexible resources</strong>
The Resource architecture that Eclipse uses has been criticized for being
overly Java-centric and constraining for some use cases. We will
generalize the Resource layer (and related areas, such as EFS) to better
address these uses. [Workspace, Platform UI]
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=252647">252647</a>)</li>
</ul>
</p:committed>
<p:proposed>
<p><i>None at this time.</i></p>
</p:proposed>
<p:deferred>
<p><i>None at this time.</i></p>
</p:deferred>
</p:theme>
</p:themes_and_priorities>
</p:plan>