Re: [platform-releng-dev] Philosophical Question: What approval do we ne

[Jim des Rivieres <Jim_des_Rivieres@xxxxxxxxxx>]

As a general rule, API changes in the maintenance stream are not kosher. 
The problem is that consumers need flexibility wrt to which service 
release they run atop. Even additions to the API can interfere with this, 
because binaries compiled against a new API method added in 3.1.2, say, 
would not link, much less run, atop the binaries for 3.1.0 or 3.1.1.

API changes in the maintenance stream do need PMC approval, and will be 
considered as *breaking* changes. Like all breaking API changes, proposals 
are judged on their merits.

As for adding a "do not implement, do not extend" method to an API class, 
it sounds like this method is not really API at all. I recommend finding 
it a nice home inside an internal package :-)

---jim




Douglas Pollock <douglas.pollock@xxxxxxxx> 
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx
08/10/2005 03:01 PM
Please respond to
dpollock and "Eclipse platform release engineering list."


To
platform-releng-dev@xxxxxxxxxxx
cc

Subject
[platform-releng-dev] Philosophical Question: What approval do we need for 
API changes in 3.1.1?






Is at all kosher to put API changes in to a maintenance build?  Or, how 
minor 
does the API change have to be?  If we add a method to an interface that 
is 
marked "do not implement, do not extend", is that kosher?  Do we need to 
get 
approval from team leads or the PMC?

While we don't actually need to make an API change (there is another way 
to 
get the same effect), I'm curious about this....



d.
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev