[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-ocl.dev] MDT/OCL changes before and after M6.
|
Ed,
I don't see a problem with including "bleeding edge" code as part of the examples. However, I'm not sure whether it's necessarily a good idea to include the examples as part of the SDK if it hasn't been in the past. Consumers of OCL may be picking up the SDK explicitly expecting it not to include examples...
Regarding participation in Helios, yes, each project/subproject/component must update their portal metadata in order to indicate whether they are participating in the release train (there's a Helios field that must be set to "1"). I'll be sending out a reminder to the whole MDT team about this in the very near future...
Cheers,
Kenn
On Fri, Dec 11, 2009 at 1:29 PM, Ed Willink
<ed@xxxxxxxxxxxxx> wrote:
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
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
