Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
QVTOML/IndigoReview
This page provides the required docuware for the M2M QVT Operational 3.0.0 Release Review, as part of the upcoming Helios Simultaneous Release.
Contents
Overview
QVT Operational is M2M component which provides an implementation of the QVT Operational Mapping language defined by the OMG Query/View/Transformation Specification (QVT).
The component integrates with other technologies from Eclipse Modeling such as EMF, OCL.
Features
- Semantically sensitive editor for QVT Operational language
- QVT Operational project nature, builder
- Support for black-box libraries (Java code accessible from QVT)
- Transformation invocation Java API
- Execution engine & debugger
Non-Code Aspects
Documentation hosted at http://www.eclipse.org/m2m/qvto/doc/
Standards
QVT Operational is mostly compliant with [QVT OMG 1.1 standard | http://www.omg.org/technology/documents/modeling_spec_catalog.htm#MOF_QVT].
UI Usability
QVT Operational is conforming to the user interface guidelines.
Schedule
QVT Operational is a “+2” component in the Helios simultaneous release.
M1 08/17/2009 M2 09/28/2009 M3 11/09/2009 M4 12/14/2009 M5 02/01/2010 M6 03/15/2010 API freeze M7 05/03/2010 Feature Freeze RC1 05/17/2010 RC2 05/24/2010 RC3 05/31/2010 RC4 06/07/2010 RC5 06/14/2010 Helios 06/23/2010
Testing & Packaging
- Approx. 1017 tests launched on every continuous build
- Integrated with eclipse.org Hudson new continuous build system
Communities
- Interaction in Bugzilla
- Activity on the M2M newsgroup: roughly 583 messages from June 2009 to May 2010
- Collaboration with other projects (MDT OCL, GMF) at Eclipse
Bugzilla
Bugzilla snapshot for Helios as of 28 May 2010:
Commiter Changes
No commiter change.
IP Issues
The QVT Operational component leadership verifies that:
- the about files and use licenses are in place as per the Guidelines to Legal Documentation.
- all 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.
- all significant contributions have been reviewed by the Foundation's legal staff.
- all non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff.
- all Contribution Questionnaires have been completed.
- the "provider" field of each plug-in is set to "Eclipse Modeling Project“.
- the "copyright" field of each feature is set to the copyright owner (the Eclipse Foundation is rarely the copyright owner).
- any third-party logos or trademarks included in the distribution (icons, help file logos, etc) have been licensed under the EPL.
- any fonts or similar third-party images included in the distribution (e.g. in PDF or EPS files) have been licensed under the EPL.
The QVT Operational Project IP log in located at http://www.eclipse.org/projects/ip_log.php?projectid=modeling.m2m.qvt-oml
Project Plan
The current project plan is available from http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/m2m/qvtoml/project-info/plan.xml&component=QVT Operational.