Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
- 1 Indigo Release and Graduation Review - Modeling Amalgamation 1.2
- 1.1 Contact
- 1.2 Focus
- 1.3 New and noteworthy
- 1.4 Talking Points
- 1.5 IP Issues
- 1.6 Schedule
- 1.7 Project Plan
- 1.8 Graduation : Active Community
- 1.9 Graduation : Open and Transparent
- 1.10 Graduation : The Eclipse Way
Indigo Release and Graduation Review - Modeling Amalgamation 1.2
Indigo Simultaneous Release
Release Review and Graduation Review
Cédric Brun (firstname.lastname@example.org)
Release Review : Mai 11, 2011
Communication Channel : http://www.eclipse.org/forums/index.php/f/182/
Process Documentation : http://www.eclipse.org/projects/dev_process/development_process.php
The Amalgam project provides :
- the Eclipse Modeling Package
- integration code and tools for the Modeling Projects
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 :
- EMF-EEF Ecore codegen
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.
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.
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.
1 Committer from Obeo, 1 from Borland and 1 from Itemis.
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.
The Modeling Amalgam IP log is located at http://www.eclipse.org/projects/ip_log.php?projectid=modeling.amalgam
The Modeling Package is tested manually with each milestone.
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 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.
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)
No standard exists concerning the modeling amalgam project scope..
The Amalgam integration code is conforming to the user interface guidelines.
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.
The Helios/SR2 modeling package has been downloaded 50 000 times.
No committer change for this release.
Since the feature freeze our commitment was to follow the EMF.
Amalgam 1.2 Release Plan
M1 09/18/2009 M2 10/29/2009 M3 12/10/2009 M4 13/15/2009 M5 03/02/2010 M6 04/16/2010 M7 06/04/2010 RC1 06/17/2010 RC2 06/25/2010 RC3 07/01/2010 RC4 07/08/2010 Final 06/16/2010 3.1 06/23/2010
The schedule used is matching the schelude of the release train for "+3" projects.
The Indigo project plan is available at http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/m2t/acceleo/plan-indigo.xml
Graduation : Active Community
The Modeling package is the most easiest entry point for end users and adopters. As such it has a fair share of downloads (7th package for Helios SR2). The community at large gave pretty good feedback using 2 surveys :
Graduation : Open and Transparent
The project has a small and diverse commiter team but involve all the other Eclipse Modeling projects through bugzillas to tackle integration issues and enhance the end user experience.
Open discussion through forums, blogs and bugzilla.
Project materials are all available to the public
Follow IP-policy (e.g. approval for major contributions)
Graduation : The Eclipse Way
Presence in every Eclipse Conference.
Completely integrated with the Eclipse Build Infrastructure.
Part of the simultaneous release for 2 years now