Re: [eclipse-pmc] Publishing 0.9 API's for new components

[Steve Northover <Steve_Northover@xxxxxxxxxx>]

Here is my initial position: Either
something is API or it is not.  If it is API, then it is not subject
to change.  If you are not sure, don't make it API.

Darin Wright/Ottawa/IBM@IBMCA
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

11/28/2007 12:56 PM

Please respond to
eclipse-pmc@xxxxxxxxxxx

To	eclipse-pmc@xxxxxxxxxxx
cc
Subject	[eclipse-pmc] Publishing 0.9 API's for new components

PMC,

API tooling work is progressing in the PDE incubator (
http://wiki.eclipse.org/PDE_UI_Incubator_ApiTools). We envision some form
of API tooling to ship with the 3.4 Eclipse release. API tooling itself
will have an API. As with any first release of a component we are hesitant
to commit to a public/stable API that will be supported for all versions
of API tooling to come. I believe there are other components that will
have similar issues in the 3.4 release (p2, for example). Is there some
style/guideline we can follow to publish these "0.9 APIs" that
are subject 
to change?

Thanks,

Darin Wright

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc