Location: http://www.eclipse.org/stardust/plan/stardust-project-plan-Kepler.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="project-plan-render.xsl"?>-->
<?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="Stardust">
<release projectid="soa.stardust" version="Kepler"/>
<introduction>
<html:div>Project Stardust provides a fully-fledged BPM platform providing:
<html:ul>
<html:li>business processes functinality in Eclipse or alternatively in a browser-based environment,</html:li>
<html:li>integration functionality for applications, services and UI components,</html:li>
<html:li>runtime exection of processes</html:li>
<html:li>browser-based access to BPM functionality via portal applications</html:li>
</html:ul>
</html:div>
<html:p>This project plan lays out features and schedule for the Kepler release of project Stardust. </html:p>
</introduction>
<release_deliverables>
<html:p>Stardust Kepler will deliver the following main components:</html:p>
<html:ul>
<html:li>Modeling plugins to create and debug workflow models from within eclipse.</html:li>
<html:li>Stardust process engine to execute BPM applications on various java-based runtime environments.</html:li>
<html:li>Stardust web portals for browser-based execution and monitoring of business processes and associated applications.</html:li>
<html:li>Browser-based modeler for creating and deploying workflow models directly in browser environments.</html:li>
<html:li>Reporting component (BIRT based) for runtime monitoring and reporting of BPM applications.</html:li>
<html:li>Integrated rapid application environment (RAD) for deploying and executing BPM applications in an embedded Tomcat server within
the eclipse modeling environment.</html:li>
<html:li>Possibility to consume the Stardust runtime as a Maven dependency in build files of consuming projects and to automatically configure
runtime deployments by consuming Maven archetypes.</html:li>
<html:li>Documentation</html:li>
</html:ul>
</release_deliverables>
<release_milestones>
<preamble>
<html:div>The milestone plan for the Stardust Kepler release will follow the Kepler release schedule:</html:div>
</preamble>
<milestone date="12/21/2012" milestone="M4"><html:div>First integration build</html:div></milestone>
<milestone date="02/08/2013" milestone="M5"><html:div>Juno support established. Main platform issues known to date addressed for Kepler.</html:div></milestone>
<milestone date="03/22/2013" milestone="M6"><html:div></html:div></milestone>
<milestone date="05/10/2013" milestone="M7"><html:div></html:div></milestone>
<milestone date="05/24/2013" milestone="RC1"><html:div></html:div></milestone>
<milestone date="05/31/2013" milestone="RC2"><html:div></html:div></milestone>
<milestone date="06/07/2013" milestone="RC3"><html:div></html:div></milestone>
<milestone date="06/14/2013" milestone="RC4"><html:div></html:div></milestone>
<postamble><html:div></html:div></postamble>
</release_milestones>
<target_environments>
<html:h3>Supported Eclipse Platform</html:h3>
<html:p>Goal is that the Stardust Kepler Release will be compatible with eclipse platform versions Kepler (4.3) as well as Juno (4.2).</html:p>
<internationalization>
<html:div>All Stardust components support full internationalization via resource bundles. The Kepler version will at least contain language bundles
in English and German.</html:div>
</internationalization>
</target_environments>
<compatibility_with_previous_releases>
<html:div>
Stardust Kepler will be able to process workflow models and audit trail databases created with previous Stardust versions.
Compatibility may be provided via migration tooling (upgrade jobs).
Whether eclipse workspace compatibility will be provided has not been decided yet.
</html:div>
</compatibility_with_previous_releases>
<themes_and_priorities>
<preamble>
<html:div>Aside of working on features, the main priority of this release will be to establish support for the Kepler and Juno platform versions and
perform all necessary version upgrades to upstream eclipse plugins and other third party libraries that will be required in the process.
</html:div>
</preamble>
<theme name="Runtime Platform Upgrades">
<description>
<html:div>
Some of the supported runtime platforms will be modernized. This will likely include support for:
<html:ul>
<html:li>MS SQL Server 2012 </html:li>
<html:li>JBoss Application Server 7.1</html:li>
<html:li>Tomcat 7</html:li>
</html:ul>
</html:div>
</description>
</theme>
<theme name="Enhanced Maven Support">
<description>
<html:ul>
<html:li>The Stardust build files will be refactored to fully rely on Maven mechanisms and eliminate other
build technologies wherever possible.</html:li>
<html:li>Consumption of the Stardust engine with its transient dependencies via Maven will be further simplified
for consuming projects.</html:li>
<html:li>Maven archetypes will be provided that allow for automated assembly of Stardust server deployments.</html:li>
</html:ul>
</description>
</theme>
<theme name="Various Minor Fixes and Enhancements">
<description>
<html:div>
A considerable part of the effort spent on the Stardsut Kepler release will go into minor fixes and enhancemensts as well as
code refactoring.
Detail planning to be added.
</html:div>
</description>
</theme>
</themes_and_priorities>
</plan>