Re: [platform-releng-dev] APITooling baseline for 3.6 maintenance develo

[Kim Moir <Kim_Moir@xxxxxxxxxx>]

I've opened a bug to enabled this in
the 3.6.x stream builds.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=319786

Kim

Darin Wright/Ottawa/IBM@IBMCA
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx

07/13/2010 03:14 PM

Please respond to
"Eclipse platform release engineering list."        <platform-releng-dev@xxxxxxxxxxx>

To	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
cc
Subject	Re: [platform-releng-dev] APITooling baseline for 3.6 maintenance        development

> In order to get everyone to use the appropriate
baseline for 3.6 
> maintenance development, I am sending this message to the releng list.
> The right baseline for the 3.6 maintenance stream is 3.6.0 and not
3.5.2. 
> The reason for this is that no new APIs should be added in a dot 
release. 
> In order to prevent this from happening, 3.6.0 should be the baseline
to 

> use. So if any new API is added, the tooling will suggest moving the
> version to 3.7.qualifier and this is forbidden.
> If you use 3.5.2 as the baseline, you can end up introducing new APIs
> without noticing since the minor version is already incremented.
> 
> 
> The API freeze check can be removed from the 3.6 maintenance build
page 
> since no new API can be added if everybody is using this setting.
> 
Or, the API freeze check could use 3.6.0 as the reference baseline to 
catch any illegal API changes/additions in 3.6.1.

Darin

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