[mdt-ocl.dev] MDT/OCL changes before and after M6.

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi Kenn

It is becoming clear that almost all API changes to be completed by M6 
will have to be done by me.

I had planned to do parser and editor areas, with others doing library 
and evaluator. I cannot get everything done by M6, so in order to avoid 
another major increment for next year, I'm trying to give myself more 
time and plan the following.

Java API changes on existing code as small and as early as possible by M6.
Non-Java (OCL behaviour) 'API' changes by M7.
Examples plugin changes by M8.

The new editor and console will be in examples plugins for Helios, 
allowing promotion to non-examples next year without incurring an API 
change and major version increment. The new examples plugin code will 
not be as thoroughly reviewed and tested as I would have liked, but a 
small number of determined users have already found them useful, so it 
is a shame to hide them.

The current OCL Examples has a little known OCL Console for model 
evaluation. I would like to ship the examples plugins within the main 
SDK, so that all users get the Console and Editor without having to do a 
further install.

Is it acceptable to (ab)use the examples plugins to create a kind of 
incubation status aspect of a mature project in this way?

The editor uses LPG2 and IMP.

Adolfo is making progress on getting LPG 2.0.17 into Orbit. Is a request 
to use LPG 2 required?

IMP at last has a planned Helios 1.0.0 release. Is a request for an 
examples plugin to use IMP required?

David Williams is querying Helios simultaneous release participation. Is 
MDT/OCL registered or is some action required?

   Regards

      Ed