[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[sirius-dev] Status update for Sirius 1.0.0M6
|
Hi all,
The next milestone, Sirius 1.0.0M6, will be released on 2014-03-14. Note
that this date is for the whole Luna M6 release. Platform is released
one week earlier, and Sirius having an offset of +3 must be released and
contributed to the aggregation by March 12 (earlier is better). We want
to keep the last week before the release for stabilization only, so this
gives us this calendar:
* March 5: feature freeze, last date to merge impacting changes on
master for M6, start of stabilization period.
* March 12: Sirius 1.0.0M6 released and contributed to Luna M6.
* March 14: Luna M6 released.
The major items being worked on or planned for this release are:
* Modularization: the continuation of the split of all diagram-specific
code out of the core of the Sirius platform.
- M5 already included the first step in this work (bug #423037),
which involved moving diagram-specific types in our meta-model into
their own Ecore package.
- M6 will include step 2 (bug #423052), which physically separates
the new EPackages into their own diagram.ecore file and in doing so
removes all reference from the core meta-model to diagram-specific
concepts (in other words, diagram.ecore depends on viewpoint.ecore but
viewpoint.ecore no longer references concepts which are now in
diagram.ecore). This step is done and has been merged on master.
- The next and final step is to move the diagram meta-model and the
corresponding Java code out of the main org.eclipse.sirius plug-in and
into org.eclipse.sirius.diagram (bug #427803). This is by far the most
complex step, as a lot of code in org.eclipse.sirius contains explicit
or implicit assumptions about the presence of the diagram dialect in the
core. Laurent is currently studying how best to approach this task. It
is not clear yet if this will be ready for M6. As for the previous
steps, the work will be done in a separate branch and merged on master
for M6 only if considered stable enough before the feature freeze;
otherwise it will wait for M7.
* Performance: several small and large tickets in M6 should improve
performances in various areas. They should not modify the behavior of
the system, except maybe in corner cases which will be documented. See
[1] for the complete list, but the more important ones should be #425561
and #426687.
* Cleanup and architecture work. Two longer-term tasks have been
started: #427247 deals with cleaning up our meta-model definitions from
legacy stuff and #427799 is about providing a new, simpler and more
efficient implementation of the session APIs. Both are currently in
early phases of gathering requirements and identifying more clearly the
concrete tasks to perform. They will probably be split into several
sub-tickets, some of which may appear in M6. We can reasonably expect
the meta-model cleanup to be done for 1.0 (maybe M7), but the rewrite of
the session implementation is on a different scale and will take much
longer. I encourage anyone interested in this particular work to get
involved in the bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=427799
The complete list of bugs currently fixed or planned for M6 can be seen
at [2].
Regards,
Pierre-Charles David (Sirius co-lead)
[1]
https://bugs.eclipse.org/bugs/buglist.cgi?classification=Modeling&keywords=performance%2C%20&keywords_type=allwords&list_id=8229336&product=Sirius&query_format=advanced&target_milestone=1.0.0M6
[2]
https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&list_id=8228357&namedcmd=Sirius%201.0.0M6
