- 1 Juno Release Review - Modeling Amalgamation 1.3
- 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
Juno Release Review - Modeling Amalgamation 1.3
Cédric Brun (firstname.lastname@example.org)
Release Review : Mai 30, 2012
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
The package content did not change since the Indigo release but is now based on the Eclipse Juno platform.
A few components have been added in the discovery UI for Indigo:
- GMF Tooling
- EMF Store
The project migrated to GIT : http://git.eclipse.org/c/amalgam/org.eclipse.amalgam.git/
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 Juno yet. Any help is welcome.
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 been done during the Google Summer of Code 2011 to document the modeling projects, the result has not been integrated in Eclipse itself but is available through github : http://model-driven-blogging.blogspot.fr/2011/09/eclipse-modeling-definitive-tutorial.html
Severity FIXED INVALID WONTFIX WORKSFORME Total blocker . 1 . . . 1 major 1 1 . 1 . 2 normal 2 28 5 1 1 37 enhancement 2 3 1 2 . 7 Total 4 33 6 4 1 49
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, 2012)
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 Indigo/SR2 modeling package has been downloaded 161 679 times.
No committer change for this release.
Since the feature freeze our commitment was to follow the EMF.
Amalgam 1.3 Release Plan
RC1 05/22/2012 RC2 05/29/2012 RC3 06/05/2012 Final 06/12/2012 1.3 06/27/2012
The schedule used is matching the schelude of the release train for "+3" projects.
The Juno project plan is available at http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/amalgam/plan-juno.xml
The Modeling package is the most easiest entry point for end users and adopters. As such it has a fair share of downloads (5th package for Indigo SR2). The community at large gave pretty good feedback so far.
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)
The Eclipse Way
Presence in every Eclipse Conference.
Completely integrated with the Eclipse Build Infrastructure.
Part of the simultaneous release for 3 years now