Re: [cdt-dev] RE: API tooling for CDT 8.0 and CDT 7.0.1

["Christian W. Damus" <cdamus@xxxxxxx>]

Hi, Marc,

If you add new functionality in a maintenance release, then you may run into problems with the Eclipse Development Process.  Any release that introduces new function (not just bug fixes) is subject to the full release review procedure.  The reason why a maintenance release is exempt from review is that it is understood not to have new function, and therefor not to present any IP/legal liabilities.

I suppose there is grey area in refactoring of existing APIs that continue to provide the same function, but presenting a different API may be construed as new function in and of itself.  ;-)

And I suppose also that it's a numbers game:  how much of what kind of new stuff constitutes "new function."?

http://www.eclipse.org/projects/dev_process/development_process.php#6_4_Releases

Cheers,

Christian


On 17/06/10 09:58 AM, Marc Khouzam wrote:

If I understand correctly the API tooling, if we want to avoid all API changes
for 7.0.1, then I think we really should be on a 7.0 baseline.
If we remain on 6.0, someone can remove a method that was added in 7.0 and that will be
ignored by the API tooling.
But if we move to a 7.0 baseline, removing such a method will give an error that will
require incrementing the plugin to 8.0.

About the maintenance release, the policy for a maintenance release is no API changes
at all?  So we can't add new classes or methods?

Thanks

Marc


  

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx 
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Thursday, June 17, 2010 9:47 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] RE: API tooling for CDT 8.0 and CDT 7.0.1

Actually, 7.0.1 should still be against the 6.0 baseline, no? There
are no API changes at all allowed on the maintenance stream.

On Thu, Jun 17, 2010 at 9:35 AM, Marc Khouzam 
<marc.khouzam@xxxxxxxxxxxx> wrote:
    

I've updated our policy wiki with this procedure.
http://wiki.eclipse.org/CDT/policy


________________________________
From: cdt-dev-bounces@xxxxxxxxxxx 
      

[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
    

Behalf Of Marc Khouzam
Sent: Thursday, June 17, 2010 8:29 AM
To: 'CDT General developers list.'
Subject: [cdt-dev] API tooling for CDT 8.0 and CDT 7.0.1

Hi all,

just a reminder that now that we have moved to developing 
      

new CDT versions,
    

you should update
your API baselines to the CDT 7.0 code for both 8.0 and 7.0.1.

There has already been some commits to CDT 8.0 that broke 
      

API tooling :-)
    

Here is how I do it, takes 30 seconds:

1- download CDT 7.0 from

      

http://download.eclipse.org/tools/cdt/builds/7.0.0/I.I20100614
1710/index.html
    

2- unzip it in some directory (I create a CDT7.0 dir)
3- in eclipse go to Preferences->Plug-in Development->API Baselines
4- Press the Add Baselines... button
5- Name your new baseline (I use CDT7.0)
6- Choose the directory of point #2 and press OK
7- make sure the new baseline is the selected one.

Thanks

Marc


_______________________________________________
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
  

--
Christian W. Damus
Software Developer, IDE Team
QNX Software Systems