Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] automatically updating API tooling baseline

Maybe setting the API to the latest master could work for an individual committer, but if everyone did that then we would never notice when the API was broken by mistake.  For example, if someone commits a change that breaks the API (because they didn't have the API  Tooling enabled), this commit would be part of master and would look like the correct API version.  We need some of us to really compare master with the API of the last release.

So, I wouldn't recommend following master.


> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Nathan Ridge
> Sent: Thursday, November 27, 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]
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit

Back to the top