RE: [mdt-ocl.dev] Re: MDT OCL Project Plan

[Alexander Igdalov <alexander.igdalov@xxxxxxxxx>]

Hi Ed,

 

I corrected the typos. As regards the introduction, I think it is a little confusing. The reader might think that MDT OCL 1.4.0 is compliant with the OCL 2.0 standard except for the places where the standard is unimplementable/self-contradicting/etc. This is wrong because MDT OCL 1.4.0 is in fact the 1.3.0 implementation targeted for Helios. We do not fix bugs like invalid/OclInvalid confusion, do not change erroneous behaviour for operations on null/invalid, etc. This is why we cannot say that either MDT OCL 1.3.0 or 1.4.0 are best endeavours to establish a coherent interpretation of the OCL 2.0 standard.

 

Regards,

- Alex.

---

From: mdt-ocl.dev-bounces@xxxxxxxxxxx [mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Ed Willink
Sent: Wednesday, September 23, 2009 10:53 AM
To: MDT OCL mailing list
Subject: [mdt-ocl.dev] Re: MDT OCL Project Plan

Hi Alex

Looks good. Is there a deadline for adding bugs? I would hope to clear most for Helios.

Two typos:

Intro: implemenation
Useability theme: imporvements

------

I think we need to be clearer about relationships to OCL standards.

I would clarify the Introduction as:

This document lays out the feature and API set for the fifth release of the Eclipse Object Constraint Language (MDT OCL) Project, versions 3.0.0 and 1.4.0.

Note that the OMG OCL 2.0 standard and the OMG OCL 2.1 proposed standard suffer from significant ambiguities and conflicts making a compliant implementation impossible. MDT OCL releases are therefore best endeavours to establish a coherent interpretation of a corresponding standard. MDT OCL releases are described as heavily influenced by a particular OCL version. Deviations from the OCL standard are submitted to the OMG as Issues.

Note that, MDT OCL 3.0.0 is heavily infliuenced by OCL 2.1 proposals and associated Issues. It is not intended to be backwards compatible with MDT OCL 1.3.0 (Galileo release). The major part of bug fixes and feature development is done in MDT OCL 3.0.0.

Note that, MDT OCL 1.4.0 is an implementation of OCL which is fully backwards compatible with MDT OCL 1.3.0 (Galileo release). Since this release inherits the behaviour of MDT OCL 1.3.0, MDT OCL 1.4.0 can be considered a maintenance release of the best endeavours to respond to OCL 2.0 influences. Some of these best  endeavours are endorsed by OCL 2.1, others remain to be clarified by a future standard. In Helios release the OCL team mostly focuses on the implementation of the OMG OCL 2.1 standard which is released as MDT OCL 3.0.0.

    Ed


Alexander Igdalov wrote:

Hi All,

 

Please take a look at our project plan.

 

http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/mdt/ocl/project-info/plan_helios.xml&component=OCL

 

It is a united plan for both 1.4.0 and 3.0.0 versions. Kenn, thanks for this idea - the plan xml was probably designed for one version only but I managed to unite the plans though))

 

If you want to update the project plan text or add a new theme under the "Themes and Priorities" section - please write to me about it. This is because this requires modification to plan xml and since then it needs specific committer rights.

 

However, for exisiting themes bugs can be added/modified without special rights. For example, to add a new bug under the "OCL 2.1 standard adoption" theme you will need to perform the following modifications in bugzilla:

 

1. Set target milestone to 3.0.0

2. Add to whiteboard field: OCL 2.1

3. Add keyword: plan

4. Set helios flag to: +

 

Cheers,

- Alex.

 

P.S. Kenn, the links to adopt improvements like https://bugs.eclipse.org/bugs/show_bug.cgi?id=255786 are a part of a more general bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=290103 .

Please ping me if a more fine-grained structure is needed.