You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/17 16:00:00 UTC

[jira] [Commented] (ARROW-1975) [C++] Add abi-compliance-checker to build process

    [ https://issues.apache.org/jira/browse/ARROW-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441078#comment-16441078 ] 

ASF GitHub Bot commented on ARROW-1975:
---------------------------------------

xhochy opened a new pull request #1905: ARROW-1975: [C++] Generate ABI reports
URL: https://github.com/apache/arrow/pull/1905
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> [C++] Add abi-compliance-checker to build process
> -------------------------------------------------
>
>                 Key: ARROW-1975
>                 URL: https://issues.apache.org/jira/browse/ARROW-1975
>             Project: Apache Arrow
>          Issue Type: New Feature
>          Components: C++
>            Reporter: Uwe L. Korn
>            Assignee: Uwe L. Korn
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.9.1
>
>
> I would like to check our baseline modules with https://lvc.github.io/abi-compliance-checker/ to ensure that version upgrades are much smoother and that we don‘t break the ABI in patch releases. 
> As we‘re pre-1.0 yet, I accept that there will be breakage but I would like to keep them to a minimum. Currently the biggest pain with Arrow is you need to pin it in Python always with {{==0.x.y}}, otherwise segfaults are inevitable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)