- 1 Indigo Release/Graduation Review - Ecore Tools 1.0
- 1.1 Indigo Release Highlights
- 1.2 IP Issues
- 1.3 Non-Code Aspects
- 1.4 Documentation
- 1.5 Bugzilla
- 1.6 Standards
- 1.7 UI Usability
- 1.8 End of Life
- 1.9 Communities
- 1.10 Schedule
- 1.11 Project Plan
Indigo Release/Graduation Review - Ecore Tools 1.0
Indigo Simultaneous Release
Release Review and Graduation Review
Vincent Hémery (email@example.com)
Graduation Review : May 16th, 2011
Process Documentation : http://www.eclipse.org/projects/dev_process/development_process.php
Indigo Release Highlights
New and noteworthy
Ecore Tools 1.0 is compatible with Eclipse 3.4 (Ganymede), Eclipse 3.5 (Galileo), Eclipse 3.6 (Helios) and Eclipse 3.7 (Indigo).
Quality of APIs
The component lead certifies that the requirements for Eclipse Quality APIs have been met for this release. All non-API code is in « internal » packages. There is no « discouraged access » warning on the code.
Architectural Issues & End-of-Life Issues
No new architectural issue in this release No End-of-Life issue in this release.
Anyware Technologies, Atos Origin, Individual.
The about files and use licenses are in place as per the Guidelines to Legal Documentation.
CQ 2518 - The Content includes items that have been sourced from the OMG MTL 1.0 specification : http://www.omg.org/spec/MOFM2T/1.0/
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 or feature is set to "Eclipse Modeling Project".
The "copyright" field of each plugin or feature 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.
The Ecore Tools IP log is located at http://www.eclipse.org/projects/ip_log.php?projectid=modeling.emft.ecoretools
13 Junit tests cover the UI aspects of the editor. These JUnit tests execute successfully in a workspace, but since the Indigo migration, there is a configuration issue preventing their automatic launch on the build server.
Comments represent 32% of the Java source code.
An Ohloh page is available at http://www.ohloh.net/p/9584/analyses/latest
A documentation is available in the Help menu : EMF Ecore Tools Developer Guide.
Note : These figures are a snapshot taken on May 17th, 2011. See the generated Bugzilla report for up to date information
EcoreTools is based on the following standards :
- JavaTM 1.5 - Ecore - Based on GMF 2.2
Filters, Navigability, Multi-diagrams... Internationalization Ecore Tools uses Eclipse i18n support Localization Ecore Tools map added to Babel
End of Life
There are no specific end of life concerns for this release.
Committer diversity Sierra Wireless (3), Atos Origin (2), Individual (2) Conference Participation : - Committers attended and/or presented at Eclipse Summit Europe 2009 and EclipseCon 2009 - Some committers also actively participate in MDT-Papyrus.
The schedule should match the release train for "+2" projects. As there has been very few evolutions recently on EcoreTools, we schedule very few candidate builds. There should be no major change between these versions.
Ecore Tools 1.0 Release Plan
RC2 (matching Indigo RC2 and used for Indigo RC3) 2011-05-25 RC4 (matching Indigo RC4) 2011-06-08 Final 1.0 (should be similar to RC4) 2011-06-22
The Helios project plan is available at http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/emft/ecoretools/project-info/plan.xml&component=EcoreTools