Project Plan For EMF, version 2.6.0

Introduction

This document lays out the feature and API set for the 2.6.0 release of the Eclipse Modeling Framework Core (EMF Core) project. This project plan inherits from the Eclipse Modeling Framework Project Plan, which should be referenced when consulting this individual project plan.

Release Deliverables

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

Table of Contents

Release Milestones

Release milestones occur at roughly 6 week intervals and follow the Platform release milestone by the Helios-established +1 delta interval, though all effort will be made to reduce this to +1 business day regardless of the size of the established +1 delta interval.. The final EMF Core 2.6 release will available simultaneously with the 3.5 release of the Platform and all the other Helios projects. It is anticipated that EMF Core will synchronize its milestones with any changes to the Helios milestone schedule.
M108/17/2009
M209/28/2009
M311/09/2009
M412/14/2009
M502/01/2010
M603/15/2010
API Freeze
M705/03/2010
Feature Freeze
RC105/17/2010
RC205/24/2010
RC305/31/2010
RC406/07/2010
Final06/14/2010
Helios06/23/2010
EMF Core will produce maintenance releases to align with the Galileo Service Releases as needed which includes the Eclipse Platform's 3.5.1 and 3.5.2 releases. EMF Core may produce additional interim maintenance releases. Maintenance releases will only be published if they contain new fixes.
  • Friday, September 26, 2008 - EMF Core 2.5.1 maintenance release for Galileo Service Release 1.
  • Friday, February 27, 2009 - EMF Core 2.5.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 2.4.x maintenance stream are available in the 2.4.x release notes.

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The EMF Core project depends upon on the Platform, which is mostly "pure" Java™. The 3.5 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 Core, with its runtime support for generics, relies on Java 5. Eclipse Platform SDK 3.5 will be tested and validated on a number of reference platforms. EMF Core 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 Core, it's expected that EMF Core will work anywhere the Eclipse Platform does.

Internationalization

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 Core 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.

Table of Contents

Compatibility with Previous Releases

Compatibility of Release 2.6: The EMF Core project will be developed in parallel, and released simultaneously, with the following project:
  • Eclipse Platform SDK version 3.6
Each milestone version of the EMF Core project will be compatible with the corresponding milestone for this project and will be delivered within the appropriate time offset. The ultimate EMF Core release will be compatible with the released version of its dependencies and will publish binary and source compatibilities with migration guides on subsequent releases.

Table of Contents

Themes and Priorities

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.

Lighter, Faster and Better

The EMF Core project has a proven track record of quality, reliability, and extensibility but all these aspects can be continuously improved. Existing and new clients often desire more functionality from the framework while long established clients generally desire mostly improvements in performance. Often these two are at odds since additional extensibility often has a performance cost and any changes, even performance boosting ones, potentially impact reliability. Every effort will be made to introduce new capabilities so that they have negligible impact on established clients based on the guiding principle: if you don't use it, you don't pay for it. Because service and support has and always will take priority over new development work, development commitments and schedules are subject to arbitrary change, slippage, or even deferral. Be sure to establish direct communication to ensure that any hard commitments are seen as that by the development team itself!
  • Committed

    • Investigate support for specifying the behavior of a derived feature [216701] (target milestone: M4)

Table of Contents

Appendix Legal Notices

  • 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.

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"