Focus

New and noteworthy

No More Incubation

Components can now only be included in the Modeling Package if they are not in incubation.

Eclipse Modeling Package Content Change

The following component has been removed from the package :

EMFT Mint

The following components have been added to the package :

EGit

EMF-EEF Ecore codegen

Talking Points

Quality of APIs

The component lead certifies that the requirements for Eclipse Quality APIs have been met for this release.

Non-API classes are separated from the exposed API through an internal package in the namespace.

Architecture

The discovery UI is leveraging a model describing its contribution and hosted on the Eclipse.org server. This model might be updated after the release to provide new installable components for the package.

Tool Usability

Amalgam address the need of a common integrated platform for Eclipse Modeling. This platform is completely focused on the EMF runtime and technologies. The discovery UI integrated in the package address the need to find its way through the so diverse modeling project and to install the needed technologies.

End of Life Issues

The Modeling Examples developed for the Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit (ISBN-13: 978-0321534071) book have not been maintained since the Ganymede release and have not been updated for Indigo yet.

Committer Diversity

1 Committer from Obeo, 1 from Borland and 1 from Itemis.

IP Issues

The about files and use licenses are in place as per the Guidelines to Legal Documentation.

All other contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy. The other contributions of the IP log are not significant or are written 100% by employees of the same employer (Obeo) as the Submitting Committer (http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf).

All contribution Questionnaires have been completed.

The "provider" field of each plugin is set to "Eclipse Modeling Project".

The "copyright" field of each plugin is set to the copyright owner.

Any third-party logos or trademarks included in the distribution (icons, logos, etc) have been licensed under the EPL.

Non-Code Aspects

Unit tests

APIs

Metamodel definitions and interfaces of the modeling discovery are considered APIs.

Non-API classes are separated from the exposed API through an "internal" namespace.

Non-API packages are exported with an internal visibility as such they are visible but with an illegal access warning.

Documentation

Documentation is kept on the Eclipse Wiki http://wiki.eclipse.org/ModelingAmalgam . Work has started to provide a cross-modeling-projects documentation through the Google Summer of Code 2011, the results should be part of the Juno release.

Bugzilla

NEW

RESOLVED

VERIFIED

CLOSED

TOTAL

blocker

0

1

0

4

5

critical

2

0

0

3

5

major

5

0

0

19

24

normal

38

4

0

129

171

minor

5

0

0

10

15

enhancement

15

3

0

26

44

TOTAL

65

8

0

191

264

Note : these figures are subject to changes as the whole team is in the process of fixing bugs until the final release (this snapshot has been taken on May 17, 2011)‏

Standards

No standard exists concerning the modeling amalgam project scope..

UI Usability

The Amalgam integration code is conforming to the user interface guidelines.

Communities

Talks have been given submitted to EclipseCon but not accepted. A Google Summer of Code project has been accepted and is going on and several blog posts and surveys have been done during the year.