-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARROW-5848: [C++] SO versioning schema after release 1.0.0 #4801
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, quite happy with this. I don't expect us to have a longterm stable ABI yet. Once we have reached this, we should slow down on SO version bumps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, please merge quickly :-)
@kszucs Need to re-run cmake-format, see https://travis-ci.org/kszucs/arrow/jobs/554237034 |
Ahh, thanks for notifying me. |
Can you cancel the old builds on your Travis and AppVeyor account? |
Done. |
I merged to unstuck other PRs. Thank you! |
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 > > I choose 1XX as SO major version because we already use > 10-14 for SO major version. We should not use them in the > future to avoid confusion. So I choose 1XX in the above > examples. We can change this schema later, but to resolve the CI failures we need a solution for now. Author: Krisztián Szűcs <szucs.krisztian@gmail.com> Closes #4801 from kszucs/so-versioning and squashes the following commits: 81519fe <Krisztián Szűcs> cmake-format 74a8cbf <Krisztián Szűcs> fix full so-version in comment 431ef56 <Krisztián Szűcs> update SO versioning
Described by @kou on the mailing list:
We can change this schema later, but to resolve the CI failures we need a solution for now.