You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2021/02/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=17285913#comment-17285913 ] 

Antoine Pitrou commented on ARROW-1975:
---------------------------------------

[~uwe] Should we keep this open? Note we don't promise ABI (or even API) stability accross major versions.

> [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 Korn
>            Assignee: Uwe Korn
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)