Project Plan For BPMN modeler, version 1.2.0

This document describes the features and the API set for the 1.2.0 release of the BPMN Modeler project.

The release deliverables have the same form as is found in most Eclipse projects:

• BPMN Modeler SDK, which includes runtime, sources, examples, and documentation, and is available as a download or on the update site.
• BPMN Modeler, binary distribution, available as a download or on the update site.

Release milestones occur at roughly 6 week intervals and follow the Platform release milestone by the Helios-established +3 delta interval. The final BPMN Modeler 1.2.0 release will available simultaneously with the 3.6 release of the Platform and all the other Helios projects.

BPMN Modeler will produce maintenance releases to align with the Galileo Service Releases which includes the Eclipse Platform's 3.5.1 and 3.5.2 releases. BPMN Modeler may produce additional interim maintenance releases. Maintenance releases will only be published if they contain new fixes.

• Friday, September 25, 2009 - BPMN Modeler 1.1.1 maintenance release for Galileo Service Release 1.
• Friday, February 26, 2009 - BPMN Modeler 1.1.2 maintenance release for Galileo Service Release 2.
• Version numbers are subject to change should there be be any additional maintenance releases. A list of the issues addressed for the 1.1.x maintenance stream are available in the Release notes : 2.0.x release notes.

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The BPMN Modeler project depends upon on the Platform, which is mostly "pure" Java™. The 3.6 release of the Eclipse Platform Project is written and compiled against version 1.5 of the Java Platform APIs, and targeted to run on version 1.5 of the Java Runtime Environment, Standard Edition. BPMN Modeler rely on EMF Core which is written and compiled against version 1.5 of the Java Platform APIs., BPMN Modeler relies on Java 5. Eclipse Platform SDK 3.6 will be tested and validated on a number of reference platforms. BPMN Modeler will be tested and validated against a subset of those listed for the platform. Given that there is no operating system dependent code in BPMN Modeler, it's expected that BPMN Modeler will work anywhere the Eclipse Platform does.

The Eclipse Platform is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. Similarly, the BPMN Modeler project will externalize all its user interface elements, provide English strings for them in its default bundles, and localize a subset of the locales offered by the Platform. The download page will provide the details as the become available.

Compatibility of Release 1.2.0: The BPMN Modeler project will be developed in parallel, and released simultaneously, with the following project.

• Eclipse Platform SDK version 3.6
• EMF 2.5
• GMF 2.2

Each milestone version of the BPMN Modeler project will be compatible with the corresponding milestone for this project and will be delivered within the appropriate time offset. The ultimate BPMN Modeler release will be compatible with the released version of its dependencies and will publish binary and source compatibilities with migration guides on subsequent releases.

A list of project goals and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to indicate what major set of functionalities is expected to be the focus of each. These themes are presented below, while the goals of the associated Bugzilla entries are available for more detailed information.

Items related to the BPMN Model component are found in this section:

Items related to the BPMN Composite Designer component are found in this section:

Items related to the BPMN validation framework:

Java is a trademark or a registered trademark of Sun Microsystems, Inc. All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.