Project Plan For EMF Compare, version 1.1.0

This document lays out the feature and API set for the 1.1.0 release of the EMF Compare project. This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.

The release deliverables have the same form as is found in most Eclipse projects, namely: EMF Compare source code release, available as versions tagged with "R1_0" in the project's CVS repository. EMF Compare SDK, which includes runtime, sources, examples, and documentation, and is available as a download or on the update site. EMF Compare binary distribution, available as a download or on the update site. EMF Compare tests available as a download.

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

EMF Compare will produce maintenance releases to align with the Galileo Service Releases which includes the Eclipse Platform's 3.4.1 and 3.4.2 releases. EMF Compare may produce additional interim maintenance releases. Maintenance releases will only be published if they contain new fixes. Friday, September 26, 2008 - EMF Compare 1.0.1 maintenance release for Galileo Service Release 1. Friday, February 28, 2009 - EMF Compare 1.0.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.0.x maintenance stream are available in the Release notes : 1.0.x release notes.

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The EMF Compare 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.4 of the Java Platform APIs, and targeted to run on version 1.4 of the Java Runtime Environment, Standard Edition. EMF Compare rely on EMF Core which is written and compiled against version 1.5 of the Java Platform APIs., EMF Compare relies on Java 5. Eclipse Platform SDK 3.6 will be tested and validated on a number of reference platforms. EMF Compare will be tested and validated against a subset of those listed for the platform. Given that there is no operating system dependent code in EMF Compare, it's expected that EMF Compare 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 EMF Compare 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.1.0: The EMF Compare project will be developed in parallel, and released simultaneously, with the following project. Eclipse Platform SDK version 3.6 EMF Core 2.6 Each milestone version of the EMF Compare project will be compatible with the corresponding milestone for this project and will be delivered within the appropriate time offset. The ultimate EMF Compare 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.

Right now EMF compare only provides Diff and Match models "on demand". Those models can't update themselves when the compared models are updated. We would like to achieve such a dynamic mode : leveraging the Diff and Match engine to be able to maintain diff and match models from the change notification a resourceset, resource or EObject, is giving to us.

We would like to ease reuse and customization of the compare editor so that it can integrate nicely with modeling environment. One should be able to easily adapt the compare editor views, extend it, and plug his own editing domain or command stack.

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.