Ecore Tools 1.2.0 Release Review

Type: 
Release
State: 
Successful
End Date of the Review Period: 

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Wednesday, June 12, 2013
Project: 

Release Review

Release: 

Ecore Tools 1.2.0

Description: 

This release brings the ability to create diagrams from XCore files and is compatible with Eclipse Kepler.

API Certification: 

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Non-Code Aspects: 

Build
The build is compliant with the CBI and can be triggered with a simple:

mvn clean package.
Unit tests
13 Junit tests cover the UI aspects of the editor and are run on the Eclipse build server.
Code quality
Comments represent 32% of the Java source code.
 
Documenation
A documentation is available in the Help menu : EMF Ecore Tools Developer Guide.
 

Usability: 

Ecore Tools uses Eclipse i18n support Localization Ecore Tools map added to Babel.

End of Life: 

The next EcoreTools release will be a 2.0 version. It will leverage the new Eclipse Sirius project and will provide no compatibility with the previous stream. End users will have to re-create new diagrams from their Ecore models and EcoreTools 1.x APIs will not be maintained. On the other hand leveraging the Sirius platform means EcoreTools 2.x will be richer feature-wise, more robust and scale better on bigger Ecore models.

Standards: 

 
EcoreTools is based on the following standards :

  • JavaTM 1.5
  • Ecore
  • Based on GMF 2.2
Communities: 

 
The project has quite a lot of adopters looking at the feedback sources (bugzilla and Eclipse forums). It is one of best graphical modelers available through the Kepler update site.
The previous team could maintain the minimum effort level to get the build up and running to be part of the simultaneous release. Ed Merks and Cédric Brun offered to keep the project alive caring for the builds and the Kepler requirements.
The git migration and easily reproducible build tasks have been done in the idea of lowering the step to get into the project.
Anybody having incentives to contribute to this project will be gladly welcome.
Committer diversity: 2 committers : 1 Individual committers and one from Obeo