Eclipse Sirius 1.0.0 Release Review

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.




Sirius allows architects to easily create their own graphical modeling workbenches for specific domains (industrial systems, software applications or the organization of major companies). Based on a viewpoint approach, it enables the specification of custom Eclipse editors (diagrams, tables and trees) to create, edit and visualize EMF models.

Leaving Incubation Status.

API Certification

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

Architectural Issues

Sirius 1.0.0 includes the first phase of a long-term plan towards a more modular platform. In particular it sets up a standardize structure to organize pure technical code (i.e. helpers and extensions of other libraries and frameworks) out of the core of Sirius. This version also moves all the code specific to the diagram representations out of the core plug-ins. Sirius 1.0.0 also removes almost all the code which was marked as deprecated in earlier releases, with detailed descriptions of the changes required to adapt existing code in the release notes.

Sirius 1.0.0 uses Guava internally, but except for the test support APIs (which are not needed in a typical usage), does not expose any Guava-specific type in its APIs. Sirius 1.0.0 is compatible with Guava versions from 11.0 to 15.0 (included).

Non-Code Aspects

Sirius is built using Tycho/CBI on the Sirius HIPP. A "nightly" is built (against Juno, Kepler and Luna) several times a day when the SCM polling sees a change from the last build. The results are automatically published at well-defined URLs, described on the Sirius wiki. The published repositories also contain descriptions of the target platforms used for the build, in a form the can be consumed by downstream projects to include all the required dependencies into their target platforms

A separate job is built once a day against the lastest integration/nightly builds of all the Sirius dependencies to detect integration issues and API breakage as early as possible.

Gerrit is used for almost all contributions, with a corresponding validation job on the Sirius HIPP.

The complete documentation is published for each milestone on the Sirius website. It includes the detailed release notes for all changes between releases and milestones.

End of Life

Sirius 1.0.0 removes many of the APIs which were marked as deprecated in previous releases. The release notes include detailed information about every such change and how users can adapt existing code. More removal of deprecated APIs are planned for the next major release, especially in the metamodels defined by SIrius.


Gerrit is enabled to accept external patches; we use standard build technology (Tycho/CBI).

Sirius participates to the GSoC 2014 program, with one student.

Several Sirius-related talks and BoFs were presented in all recent EclipseCon: EclipseCon France 2013 (e.g. Sirius by Example), EclipseCon Europe 2013 (e.g. Ecore Tools 2.0), EclipseCon NA 2014 (e.g. Sirius Role-Playing Game). At EclipseCon NA 2014 several Sirius commiters participated to the hackaton.

The Sirius forum has seen more than 350 messages since its creation (last June), and the team is reactive in answering user questions.


This release is part of Luna