Jump to: navigation, search

Difference between revisions of "ModelingAmalgam/ReleaseReview/1.2"

(New and noteworthy)
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
=Indigo Release and Graduation Review - Modeling Amalgamation 1.2=
 
=Indigo Release and Graduation Review - Modeling Amalgamation 1.2=
'''Indigo Simultaneous Release'''
 
 
'''Release Review and Graduation Review'''
 
  
 
== Contact ==
 
== Contact ==
Line 22: Line 19:
  
  
===New and noteworthy===
+
==New and noteworthy==
  
 
==== No More Incubation ====  
 
==== No More Incubation ====  
Line 36: Line 33:
 
* EGit
 
* EGit
 
* EMF-EEF Ecore codegen
 
* EMF-EEF Ecore codegen
 +
 +
== Talking Points ==
  
 
=== Quality of APIs ===
 
=== Quality of APIs ===
Line 52: Line 51:
 
===End of Life Issues===
 
===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 Helios yet.
+
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.
 
+
  
 
===Committer Diversity===
 
===Committer Diversity===
Line 73: Line 71:
 
The Modeling Amalgam IP log is located at http://www.eclipse.org/projects/ip_log.php?projectid=modeling.amalgam
 
The Modeling Amalgam IP log is located at http://www.eclipse.org/projects/ip_log.php?projectid=modeling.amalgam
  
==Non-Code Aspects==
+
===Non-Code Aspects===
  
===Unit tests===
+
====Unit tests====
  
 
The Modeling Package is tested manually with each milestone.
 
The Modeling Package is tested manually with each milestone.
  
===Code quality===
+
====APIs====
 
+
==APIs==
+
 
Metamodel definitions and interfaces of the modeling discovery are considered APIs.
 
Metamodel definitions and interfaces of the modeling discovery are considered APIs.
  
Line 88: Line 84:
 
Non-API packages are exported with an internal visibility as such they are visible but with an illegal access warning.
 
Non-API packages are exported with an internal visibility as such they are visible but with an illegal access warning.
  
==Documentation==
+
====Documentation====
  
 
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.
 
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.
  
==Bugzilla==
+
====Bugzilla====
 +
 
 +
 
 +
Severity FIXED INVALID WONTFIX WORKSFORME  Total
 +
blocker          . 1 . . . 1
 +
major           . . . 1 . 1
 +
normal           3 23 5 1 1 33
 +
enhancement   2 3 . 2 . 7
 +
Total           5 27 5 4 1 42
  
{| border="1" cellpadding="5" cellspacing="0"
 
|-
 
|
 
! style="background: #CECEF2;" | NEW
 
| RESOLVED
 
| VERIFIED
 
! style="background: #CECEF2;" | CLOSED
 
! style="background: #CEF2CE;" | TOTAL
 
|-
 
| blocker
 
! style="background: #CECEF2;" | 0
 
| 1
 
| 0
 
! style="background: #CECEF2;" | 4
 
! style="background: #CEF2CE;" | 5
 
|-
 
| critical
 
! style="background: #CECEF2;" | 2
 
| 0
 
| 0
 
! style="background: #CECEF2;" | 3
 
! style="background: #CEF2CE;" | 5
 
|-
 
| major
 
! style="background: #CECEF2;" | 5
 
| 0
 
| 0
 
! style="background: #CECEF2;" | 19
 
! style="background: #CEF2CE;" | 24
 
|-
 
| normal
 
! style="background: #CECEF2;" | 38
 
| 4
 
| 0
 
! style="background: #CECEF2;" | 129
 
! style="background: #CEF2CE;" | 171
 
|-
 
| minor
 
! style="background: #CECEF2;" | 5
 
| 0
 
| 0
 
! style="background: #CECEF2;" | 10
 
! style="background: #CEF2CE;" | 15
 
|-
 
| enhancement
 
! style="background: #CECEF2;" | 15
 
| 3
 
| 0
 
! style="background: #CECEF2;" | 26
 
! style="background: #CEF2CE;" | 44
 
|-
 
! style="background: #CEF2CE;" | TOTAL
 
! style="background: #CEF2CE;" | 65
 
! style="background: #CEF2CE;" | 8
 
! style="background: #CEF2CE;" | 0
 
! style="background: #CEF2CE;" | 191
 
! style="background: #CEF2CE;" | 264
 
|}
 
  
 
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)‏
 
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)‏
  
==Tool usability==
+
https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=resolution&y_axis_field=bug_severity&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=Modeling&product=Amalgam&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=
Localization : integrated into Babel
+
  
==Standards==
+
====Standards====
  
 
No standard exists concerning the modeling amalgam project scope..
 
No standard exists concerning the modeling amalgam project scope..
  
  
==UI Usability==
+
====UI Usability====
  
 
The Amalgam integration code is conforming to the user interface guidelines.
 
The Amalgam integration code is conforming to the user interface guidelines.
  
  
==Communities==
+
====Communities====
 
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.
 
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.
 
The Helios/SR2 modeling package has been downloaded 50 000 times.
  
== Committer Changes ==
+
==== Committer Changes ====
  
 
No committer change for this release.
 
No committer change for this release.
 
  
 
==Schedule==
 
==Schedule==
Line 201: Line 145:
 
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
 
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
  
What's next?
+
== 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 :
 +
 
 +
http://model-driven-blogging.blogspot.com/2011/05/eclipse-modeling-package-sdk-or-not.html
 +
 
 +
 
 +
http://model-driven-blogging.blogspot.com/2010/06/modeling-survey-results.html
 +
 
 +
 
 +
===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 2 years now
  
{{Acceleo-index}}
 
  
 
[[Category:Modeling]]
 
[[Category:Modeling]]
[[Category:M2T]]
 
[[Category:Acceleo]]
 

Latest revision as of 08:15, 31 May 2011

Indigo Release and Graduation Review - Modeling Amalgamation 1.2

Contact

Cédric Brun (cedric.brun@obeo.fr)

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

Project Plan : http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/m2t/acceleo/plan-indigo.xml

Focus

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 :

  • EGit
  • EMF-EEF Ecore codegen

Talking Points

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.

Architecture

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.

Tool Usability

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.

Committer Diversity

1 Committer from Obeo, 1 from Borland and 1 from Itemis.

IP Issues

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

Non-Code Aspects

Unit tests

The Modeling Package is tested manually with each milestone.

APIs

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

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.

Bugzilla

Severity	FIXED	INVALID	WONTFIX	WORKSFORME  Total
blocker           .	1	 .	 .	 .	1
major	          .	 .	 .	1	 .	1
normal	          3	23	5	1	1	33
enhancement	  2	3	 .	2	 .	7
Total	          5	27	5	4	1	42


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)‏

https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=resolution&y_axis_field=bug_severity&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=Modeling&product=Amalgam&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=

Standards

No standard exists concerning the modeling amalgam project scope..


UI Usability

The Amalgam integration code is conforming to the user interface guidelines.


Communities

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.

Committer Changes

No committer change for this release.

Schedule

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.

Project Plan

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 :

http://model-driven-blogging.blogspot.com/2011/05/eclipse-modeling-package-sdk-or-not.html


http://model-driven-blogging.blogspot.com/2010/06/modeling-survey-results.html


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 2 years now