rename release as July 2010 release
diff --git a/development/plan/e4_plan_1_0.xml b/development/plan/e4_plan_1_0.xml
index b008ec8..1fe23cb 100644
--- a/development/plan/e4_plan_1_0.xml
+++ b/development/plan/e4_plan_1_0.xml
@@ -9,7 +9,7 @@
xmlns:p="http://www.eclipse.org/project/plan" xmlns="http://www.w3.org/1999/xhtml"
name="e4 Project">
-<p:release projectid="eclipse.e4" version="1.0"/>
+<p:release projectid="eclipse.e4" version="July 2010"/>
<!-- ============================================== -->
@@ -17,13 +17,13 @@
<div>
<p>
-Last revised 15:00 ET February 12, 2010.
+Last revised 15:00 ET May 7, 2010.
</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 draft document lays out the feature and API set for the next feature release
- of the Eclipse e4 project, designated release 1.0.
+ of the Eclipse e4 project, designated the July 2010 release.
</p>
<p>Plans do not materialize out of nowhere, nor are they entirely static. To
@@ -99,16 +99,16 @@
</p>
</p:preamble>
-<p:milestone date="10/09/2009" milestone="M1"><div>1.0M1</div></p:milestone>
-<p:milestone date="11/20/2009" milestone="M2"><div>1.0M2</div></p:milestone>
-<p:milestone date="01/15/2010" milestone="M3"><div>1.0M3</div></p:milestone>
-<p:milestone date="02/26/2010" milestone="M4"><div>1.0M4</div></p:milestone>
-<p:milestone date="04/09/2010" milestone="M5"><div>1.0M5</div></p:milestone>
-<p:milestone date="05/21/2010" milestone="M6"><div>1.0M6 (Feature and API Freeze)</div></p:milestone>
+<p:milestone date="10/09/2009" milestone="M1"><div>M1</div></p:milestone>
+<p:milestone date="11/20/2009" milestone="M2"><div>M2</div></p:milestone>
+<p:milestone date="01/15/2010" milestone="M3"><div>M3</div></p:milestone>
+<p:milestone date="02/26/2010" milestone="M4"><div>M4</div></p:milestone>
+<p:milestone date="04/09/2010" milestone="M5"><div>M5</div></p:milestone>
+<p:milestone date="05/21/2010" milestone="M6"><div>M6 (Feature and API Freeze)</div></p:milestone>
<p:postamble>
<div>
-<p>Our target is to complete 1.0 in late July 2010, one month after the Helios release.
+<p>Our target is to complete the release in late July 2010, one month after the Helios 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>
@@ -128,7 +128,7 @@
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 1.0 release of the e4 Project is developed on Java SE 5.</p>
+ etc.). In general, the July 2010 release of the e4 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
@@ -144,7 +144,7 @@
<p>e4 also has dependencies on browser technologies such as JavaScript. The
reference platforms listed below show the versions of these technologies that we
are developing and testing against.</p>
-<p>e4 1.0 is tested and validated on the following reference platforms
+<p>e4 July 2010 is tested and validated on the following reference platforms
(this list is updated over the course of the release cycle):</p>
<style type="text/css">
@@ -239,16 +239,16 @@
<p:compatibility_with_previous_releases>
<div>
-<h3>Compatibility of e4 1.0 with previous Eclipse project releases</h3>
-<p>e4 1.0 will not be compatible with previous releases of e4, such as the e4 0.9 release.
+<h3>Compatibility of e4 July 2010 with previous Eclipse project releases</h3>
+<p>e4 July 2010 will not be compatible with previous releases of e4, such as the e4 0.9 release.
This includes binary compatibility, contract compatibility, workbench model compatibility,
and workspace compatibility.
</p>
<p>
-e4 1.0 includes a set of bundles that are binary and API contract compatible with Eclipse Platform UI
+e4 July 2010 includes a set of bundles that are binary and API contract compatible with Eclipse Platform UI
API from the Eclipse Helios (3.6) release. This set of bundles is known as the compatibility
layer, and is intended to be used to create a full Eclipse SDK release on e4 that is fully
-compatible with previous Eclipse project releases. Thus while e4 1.0 itself is not
+compatible with previous Eclipse project releases. Thus while e4 July 2010 itself is not
compatible with previous Eclipse project releases, it provides the necessary
infrastructure to allow a fully compatible e4-based release of the Eclipse SDK to be created.
</p>
@@ -353,7 +353,7 @@
<li>
<strong>Compatibility layer.</strong>
- Although the 1.0 release itself will not be backward compatible with earlier versions
+ Although the July 2010 release itself will not be backward compatible with earlier versions
of the Eclipse platform, we will develop a compatibility layer that will allow the
full Eclipse platform and all API-clean platform plug-ins to run without modification
on e4.
