You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Antoine Pitrou (JIRA)" <ji...@apache.org> on 2019/07/04 11:52:00 UTC
[jira] [Commented] (ARROW-5848) [C++] SO versioning schema after
release 1.0.0
[ https://issues.apache.org/jira/browse/ARROW-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878580#comment-16878580 ]
Antoine Pitrou commented on ARROW-5848:
---------------------------------------
I added a workaround in https://github.com/apache/arrow/pull/4791
> [C++] SO versioning schema after release 1.0.0
> ----------------------------------------------
>
> Key: ARROW-5848
> URL: https://issues.apache.org/jira/browse/ARROW-5848
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Affects Versions: 1.0.0
> Reporter: Krisztian Szucs
> Assignee: Krisztian Szucs
> Priority: Major
>
> Described by [~kou] on the mailing list:
> If we may break ABI compatibility each minor version up
> release ("Y" is increased in "X.Y.Z"), we should include
> minor version into SO major version (100, 101 and 102 in the
> following examples):
> * 1.0.0 -> libarrow.100.0.0
> * 1.1.0 -> libarrow.101.0.0
> * 1.2.0 -> libarrow.102.0.0
> If we don't break ABI compatibility each minor version up
> release, we just use the same SO major version (100 in the
> following examples) in 1.0.0:
> * 1.0.0 -> libarrow.100.0.0
> * 1.1.0 -> libarrow.100.1.0
> * 1.2.0 -> libarrow.100.2.0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)