Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] process question about API

Yes, for changes that are visible in the API, you need to increment the
minor version of the plugin. Therefore a plugin with version 5.0.2 
does not allow for any API change compared to 5.0.0.

Markus.

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Elena Laskavaia
> Sent: Monday, November 17, 2008 3:36 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] process question about API
> Importance: Low
> 
> So does this mean in 5.0.2 we cannot create any non-private 
> functions in public packages?
> (Sorry I cannot still put it all together).
> 
> Schorn, Markus wrote:
> > 5.0.2 increments the micro version. With that you are 
> allowed to make 
> > changes that are not visible in the API.
> > 
> > 5.1 would increment the minor version allowing for binary 
> compatible 
> > API changes.
> > 
> > Markus.
> > 
> >> -----Original Message-----
> >> From: cdt-dev-bounces@xxxxxxxxxxx
> >> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Elena Laskavaia
> >> Sent: Friday, November 14, 2008 3:28 PM
> >> To: CDT General developers list.
> >> Subject: Re: [cdt-dev] process question about API
> >> Importance: Low
> >>
> >> So it we change plugin to 5.0.2 (which is the plan) we can 
> put since 
> >> 5.0.2 tag right?
> >>
> >>
> >> Schorn, Markus wrote:
> >>> You are not allowed to change API without increasing the 
> >>> minor-version, even if the change is binary compatible. See for
> >>> instance:
> >>> http://wiki.eclipse.org/index.php/Version_Numbering
> >>>
> >>> Markus.
> >>>  
> >>>
> >>>> -----Original Message-----
> >>>> From: cdt-dev-bounces@xxxxxxxxxxx
> >>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Elena Laskavaia
> >>>> Sent: Thursday, November 13, 2008 9:12 PM
> >>>> To: CDT General developers list.
> >>>> Subject: [cdt-dev] process question about API
> >>>> Importance: Low
> >>>>
> >>>> This is question to CDT commiters.
> >>>>
> >>>> Lets say I have a bug that I want to fix in 5.0.2 (this is
> >> version we
> >>>> are integrating with) and to fix it properly I really need 
> >>>> non-breaking API change. But if I do that API tooling
> >> would complain
> >>>> that there is no @since tag.
> >>>> But I only can add @since 5.0 which is not really true,
> >> and it won't
> >>>> work for 6.0 with pure 5.0 baseline (it would be error
> >> that since tag
> >>>> is wrong)...
> >>>>
> >>>> What do we do in this case?
> >>>> _______________________________________________
> >>>> cdt-dev mailing list
> >>>> cdt-dev@xxxxxxxxxxx
> >>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >>>>
> >>> _______________________________________________
> >>> cdt-dev mailing list
> >>> cdt-dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >> _______________________________________________
> >> cdt-dev mailing list
> >> cdt-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >>
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 


Back to the top