Re: [mdt-ocl.dev] Do we need a major version change after Indigo?

[Laurent Goubet <laurent.goubet@xxxxxxx>]

Hi team,

Keeping the obsolete namespaces riddled of @Deprecated annotations seem 
to me like the best solution as far as API retention policy is concerned 
(deprecated for x releases after we announce our intent to remove it, 
then removed 
http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy). That 
will greatly ease the migration pain for client projects.

+1 for "3.2" in Indigo +1.

Laurent Goubet
Obeo

On 01/02/2011 20:03, Axel Uhl wrote:
> No problem with that. +1.
>
> Best,
> -- Axel
>
> On 2/1/2011 6:35 PM, Ed Willink wrote:
> > 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
> _______________________________________________
> mdt-ocl.dev mailing list
> mdt-ocl.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev

begin:vcard
fn:Laurent Goubet
n:Goubet;Laurent
org:<a href="http://www.obeo.fr";>Obeo</a>
email;internet:laurent.goubet@xxxxxxx
url:http://www.obeo.fr
version:2.1
end:vcard