[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: ABI changes analysis

From: Ponomarenko Andrey <andrewponomarenko_at_yandex.ru>
Date: Tue, 05 Jul 2016 14:36:49 +0300
28.06.2016, 03:04, "Greg Stein":
On Sat, Jun 25, 2016 at 11:28 AM, Daniel Shahaf wrote:
Greg Stein wrote on Sat, Jun 25, 2016 at 07:29:11 -0500:
> I've reviewed the reports, and it looks like we've maintained all our ABI
> guarantees. The changes are what I would expect.
>
> Thank you for this!

+1 on both counts.

Perhaps we could run this on candidate tarballs as part of the release
process?
At least at major releases, if not every candidate. I haven't explored the toolset to see how packaged/automatable it is.
 
Conceivably, we could have a buildbot run this nightly-ish (weekly?), and have it flag issues relative to the prior release.
 
Cheers,
-g
 
See http://lvc.github.io/abi-compliance-checker/#ABI_Dumper for instructions on how to run the basic analysis tool on the library objects.
 
 
Received on 2016-07-05 13:37:04 CEST

This is an archived mail posted to the Subversion Dev mailing list.