This document lays out the feature and API set for the
2.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 "R2_1" in the project's GIT 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.

The 2.1 release for EMF Compare is scheduled synchronized with the Kepler release train schedule.

available with Kepler M5

available with Kepler M6

available with Kepler M7

available with Kepler RC1

available with Kepler RC2

available with Kepler RC3

available with Kepler RC4

available with Kepler

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 4.3 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.
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 4.3 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 they become available.

EMF Compare 2.0 was a full overhaul of the project, including its design and architecture.
As such, the project's API is not compatible with its previous 1.* versions. Version 2.1 brings few API
breakages and new features but is mostly compatible with 2.0 version. A migration guide
will be provided in order to ease the adoption effort to this new version.
EMF Compare is developped with and targets the following projects :

Eclipse Platform SDK version 4.3

EMF Core 2.9

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.

Not all plan items represent the same amount of work; some may be quite large, others, quite small. Although some plan items are for work that is more pressing than others, the plan items appear in no particular order. See the corresponding bugzilla items for up-to-date status information on ongoing work and planned delivery milestones.

The current status of each plan item is noted:

Committed plan item - A committed plan item is one that we have decided to address for the release. In bugzilla, this is reflected by having a concrete target milestone assigned (but not equals to "Kepler").

Proposed plan item - A proposed plan item is one that we are considering addressing for the release. Although we are actively investigating it, we are not yet in a position to commit to it, or to say that we won't be able to address it. After due consideration, a proposal will either be committed or deferred. In bugzilla, such items are reflected by having a target milestone "Kepler" assigned.

Deferred plan item - A reasonable proposal that will not make it in to this release for some reason is marked as deferred with a brief note as to why it was deferred. Deferred plan items may resurface as committed plan items at a later point. In bugzilla, such items are reflected by having a target milestone "---" or a post Kepler target version assigned (e.g., Kepler SR1).

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

All other products or company names are mentioned for identification purposes only,
and may be trademarks or service marks of their respective owners.