Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "MoDisco/Restructuring Reviews MetaclassInstancesAdapter From MoDisco To EMF Facet"

(Move Plan)
(Move Plan)
Line 19: Line 19:
 
== Move Plan ==
 
== Move Plan ==
  
This restructuring will be embedded into Luna.
+
The result of this restructuring will be integrated as part of the next simultaneous release (Luna).
 
+
 
The modifications required to achieve this restructuring are tracked by [https://bugs.eclipse.org/bugs/show_bug.cgi?id=405858 Bug 405858].
 
The modifications required to achieve this restructuring are tracked by [https://bugs.eclipse.org/bugs/show_bug.cgi?id=405858 Bug 405858].
  
Line 26: Line 25:
 
=== List the CQs from IPzilla that need to be moved to the "new" project ===
 
=== List the CQs from IPzilla that need to be moved to the "new" project ===
  
No CQ move is required : all the code has been written by full MoDisco committers.
+
No CQ move is required : all the corresponding code has been written by full MoDisco committers.
  
 
Here are the contributor declarations containing a bug id :
 
Here are the contributor declarations containing a bug id :

Revision as of 05:24, 30 April 2013

DRAFT


This document has to be conform to Development_Resources/HOWTO/Restructuring_Reviews

Opened CQs

No CQs are currently opened for MoDisco (cf. MoDisco CQs into IPZilla).

PMC Approval(s)

Project Plan

IP Log Approval

Review Documentation

Reasons for the move

The code to be moved implements the capability to know the instances of an EClass. This feature is required by both MoDisco and EMF Facet projects, and MoDisco actually depends on EMF Facet. That is why the best location for the corresponding implementation classes is into EMF Facet.

Move Plan

The result of this restructuring will be integrated as part of the next simultaneous release (Luna). The modifications required to achieve this restructuring are tracked by Bug 405858.


List the CQs from IPzilla that need to be moved to the "new" project

No CQ move is required : all the corresponding code has been written by full MoDisco committers.

Here are the contributor declarations containing a bug id :

  • Nicolas Bros (Mia-Software) - Bug 339930 - Anticipate UI freeze : MoDisco project & externalize Strings
  • Nicolas Bros (Mia-Software) - Bug 339930 - Anticipate UI freeze : MoDisco project & externalize Strings
  • Gregoire Dupe (Mia-Software) - Bug 405858 - Copy of MetaclassInstancesAdapter files from MoDisco
  • Gregoire Dupe (Mia-Software) - Bug 405858 - Copy of MetaclassInstancesAdapter files from MoDisco
  • Nicolas Bros (Mia-Software) - Bug 308234 - NPE with Facet when saving
  • Nicolas Bros (Mia-Software) - Bug 307999 - [Facet] Not real time update face
  • Nicolas Bros (Mia-Software) - Bug 327633 - [Model Browser] avoid blocking the UI
  • Fabien Giquel (Mia-Software) - Bug 336903 - [Model Browser] : metaclasses cache issue with some model update events
  • Gregoire Dupe (Mia-Software) - Bug 405858 - Copy of MetaclassInstancesAdapter files from MoDisco
  • Gregoire Dupe (Mia-Software) - Bug 405858 - Copy of MetaclassInstancesAdapter files from MoDisco

None of the bug id are decatred in the MoDiso IP log

Here are the contributor declarations which does not any containing a bug id :

  • Nicolas Bros (Mia-Software) - initial API and implementation
  • Nicolas Bros (Mia-Software) - initial API and implementation
  • Nicolas Bros (Mia-Software) - initial API and implementation

Nicolas Bros is a MoDisco committer since July 2009, so those "initial API and implementation" are not associated to any CQ.

List committers who will be on the "new" project

This restructuring does not imply any committer change.

List any committers who should be removed from the "old" project

This restructuring does not imply any committer change.

Describe the project infrastructure changes that you need to support the move

This restructuring does not imply any infrastructure change.

Back to the top