updated project plan
diff --git a/project-info/JWT_ProjectPlan_2012.xml b/project-info/JWT_ProjectPlan_2012.xml
index 9079820..c0e43fc 100644
--- a/project-info/JWT_ProjectPlan_2012.xml
+++ b/project-info/JWT_ProjectPlan_2012.xml
@@ -17,8 +17,8 @@
<milestone date="06/24/2009" milestone="0.6"></milestone>
<milestone date="12/18/2009" milestone="0.7"></milestone>
<milestone date="06/20/2010" milestone="1.0"></milestone>
- <milestone milestone="1.1" date="06/22/2011"></milestone>
- <milestone milestone="1.2" date="06/27/2012"></milestone>
+ <milestone date="06/22/2011" milestone="1.1"></milestone>
+ <milestone date="06/27/2012" milestone="1.2"></milestone>
</release_milestones>
<target_environments>
<html:div>We are targeting all Eclipse users who wish to create their process models and have a unified toolset to model, analyze, deploy and monitor their processes and workflows. Since it is in Eclipse we aim to be compatible with all plattforms Eclipse is already compatible with. For the beginning we are working on compatibility with the process engines Nova Bonita 4.0 as well as JBoss jBPM, but the framework shall be very generic so that every other process engine can be used as well.</html:div>
@@ -27,7 +27,8 @@
</internationalization>
</target_environments>
<compatibility_with_previous_releases>
- <html:div>All releases shall be backwards compatible with the older releases.</html:div>
+ <html:div>All releases shall be backwards compatible with the older releases. Since JWT 1.2 is a release focused on bug fixes
+ an stability, no breaking API changes are to be expected.</html:div>
</compatibility_with_previous_releases>
<themes_and_priorities>
<preamble>
@@ -72,7 +73,15 @@
<committed bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=RESOLVED&bug_status=CLOSED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=SOA&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=JWT&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&=&version=1.3.0"></committed>
<proposed bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=SOA&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=JWT&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&=&version=1.3.0"></proposed>
</theme>
-
+ <p:theme name="Support for Eclipse 3.8 workbench">
+ <p:description>
+ <p id="support38"> We aim to support both Eclipse 3.8 and 4.2 platforms with the goal of completing the switch to
+ 4.2 in the next release. The 4.2 support is intended to provide a fully featured JWT platform although we expect
+ minor issues, thereby making 3.8 the preferred platform for the 1.2 release. We will accept bug reports for either
+ 3.8 or 4.2 with a special focus on 4.2 compatibility issues.
+ </p>
+ </p:description>
+ </p:theme>
</themes_and_priorities>
</plan>
