Re: [cdt-dev] automatically updating API tooling baseline

[Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx>]

I had in mind that the API baseline and target platform could be two separate files but have the same format and similar editors. At any given point in time in the CDT, there is only one valid baseline but many valid target platforms. So I think they should be separate. The HEAD of the CDT repo would just contain the baseline that fits the current version in development. Regarding older CDTs, we could go back in a few older branches and add the appropriate baseline file. In any case, the work flow could be ironed out in the bugzilla, provided that someone can spend time to implement this :)

Marc-Andre
________________________________________
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Marc Khouzam [marc.khouzam@xxxxxxxxxxxx]
Sent: Friday, 28 November 2014 11:03 AM
To: 'CDT General developers list.'
Subject: Re: [cdt-dev] automatically updating API tooling baseline

That sounds like a nice improvement.

So the target definition file would need to be updated to a new API baseline at every CDT release?
We could easily add that as one of our manual release steps.

We only have target definition for each platform release, not each CDT release though.
Say we release CDT 8.6 and the cdt-e4.4.target file is updated to that new baseline,
what would people do when they want to patch the old CDT 8.5?  I guess they would
need to set the API baseline manually like we do now?  Sounds ok to me.


> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Marc-André Laperle
> Sent: Friday, November 28, 2014 10:50 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] automatically updating API tooling baseline
>
> One thing that could be done is to allow setting a baseline through a target
> definition. That way, you would just click a button and it would download
> everything for you. When the target file gets updated in the repo, it updates
> the baseline for you. That would be done in PDE, see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=324310.
>
> Marc-André
>
> ________________________________________
> From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on
> behalf of Nathan Ridge [zeratul976@xxxxxxxxxxx]
> Sent: Thursday, 27 November 2014 10:23 PM
> To: CDT Mailing List
> Subject: [cdt-dev] automatically updating API tooling baseline
>
> As the frequency of CDT releases has increased, so has the need to update
> the baseline for the API tooling, as described at [1].
>
> Is there a way to configure the API tooling to just always track the latest
> version on the 'master' branch, without having to update it each release?
>
> If not, what would be the appropriate component to file a bug requesting
> such a feature?
>
> Thanks,
> Nate
>
> [1] https://wiki.eclipse.org/CDT/policy#Using_API_Tooling
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev