Ed,
In principle, your exposition makes sense.
I'm only wondering if Xtext should also be considered... I mean, Are
we freely allowed to forget the major version increasing giving the
fact the code is hosted under the examples ?.
Cheers,
Adolfo.
El 01/02/2011 17:35, Ed Willink escribió:
Hi
I have assumed that we would move to 4.0 after Indigo in order to
make breaking API changes as the pivot model is introduced.
However if, as I've recently been suggesting, we promote
org.eclipse.ocl.examples.{library,pivot,xtext} to
org.eclipse.ocl.{library,pivot,xtext}, we break nothing. The new
namespaces provides alternate functionality that GUI tooling uses
and so users will probably migrate to.
We will cause much less aggravation if we leave
org.eclipse.ocl.{,ecore,uml} to gently obsolesce in optional
features. Perhaps we just splatter it with @Deprecated's to
encourage migration.
I suggest we therefore now plan for OCL 3.2 for Indigo+1, unless
some breaking EMF/UML2/e4 change requires 4.0.
Regards
Ed Willink
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
