Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-29 Thread Francois Saint-Jacques
current versioning schema is the following: > > * 1.0.0 -> libarrow.100.0.0 > * 1.1.0 -> libarrow.101.0.0 > * 1.2.0 -> libarrow.102.0.0 > > I'll update .deb package names when we decide this. > > > Thanks, > -- > kou > > In > "Re

Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-20 Thread Sutou Kouhei
-> libarrow.102.0.0 I'll update .deb package names when we decide this. Thanks, -- kou In "Re: [DISCUSS] C++ SO versioning with 1.0.0" on Thu, 4 Jul 2019 13:55:03 +0200, Krisztián Szűcs wrote: > Created a PR with the versioning scheme described by @Kou. > https:

Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-04 Thread Krisztián Szűcs
Created a PR with the versioning scheme described by @Kou. https://github.com/apache/arrow/pull/4801 We can change later (but before the next release) to unblock the failing CI builds. On Thu, Jul 4, 2019 at 12:51 PM Antoine Pitrou wrote: > On Thu, 4 Jul 2019 09:50:10 +0200 > Krisztián Szűcs w

Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-04 Thread Antoine Pitrou
On Thu, 4 Jul 2019 09:50:10 +0200 Krisztián Szűcs wrote: > Could We add a temporary solution and perhaps change the versioning schema > later? > I'm asking because all of our c++ based CI builds are failing now. Wow, thanks for pointing out. Indeed: https://travis-ci.org/apache/arrow/builds/55411

Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-04 Thread Krisztián Szűcs
gt;> > >> There is the official Debian package for it: > >> > >> https://packages.debian.org/search?keywords=abi-compliance-checker > >> > >> In <20c3b917-6f80-ca14-669d-f89e7ec7f...@python.org> > >> "Re: [DISCUSS] C++ SO ver

Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-03 Thread Antoine Pitrou
cial Debian package for it: >> >> https://packages.debian.org/search?keywords=abi-compliance-checker >> >> In <20c3b917-6f80-ca14-669d-f89e7ec7f...@python.org> >> "Re: [DISCUSS] C++ SO versioning with 1.0.0" on Wed, 3 Jul 2019 >> 09:59:15 +020

Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-03 Thread Uwe L. Korn
s=abi-compliance-checker > > In <20c3b917-6f80-ca14-669d-f89e7ec7f...@python.org> > "Re: [DISCUSS] C++ SO versioning with 1.0.0" on Wed, 3 Jul 2019 > 09:59:15 +0200, > Antoine Pitrou wrote: > > > > > Do we have any reliable tool to check for ABI

Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-03 Thread Sutou Kouhei
f80-ca14-669d-f89e7ec7f...@python.org> "Re: [DISCUSS] C++ SO versioning with 1.0.0" on Wed, 3 Jul 2019 09:59:15 +0200, Antoine Pitrou wrote: > > Do we have any reliable tool to check for ABI breakage? > > > Le 03/07/2019 à 02:57, Sutou Kouhei a écrit : >>

Re: [DISCUSS] C++ SO versioning with 1.0.0

2019-07-03 Thread Antoine Pitrou
Do we have any reliable tool to check for ABI breakage? Le 03/07/2019 à 02:57, Sutou Kouhei a écrit : > Hi, > > We'll release 0.14.0 soon. Then we use "1.0.0-SNAPSHOT" at > master. If we use "1.0.0-SNAPSHOT", C++ build is failed: > > https://github.com/apache/arrow/blob/master/cpp/CMakeLists.

[DISCUSS] C++ SO versioning with 1.0.0

2019-07-02 Thread Sutou Kouhei
Hi, We'll release 0.14.0 soon. Then we use "1.0.0-SNAPSHOT" at master. If we use "1.0.0-SNAPSHOT", C++ build is failed: https://github.com/apache/arrow/blob/master/cpp/CMakeLists.txt#L47 message(FATAL_ERROR "Need to implement SO version generation for Arrow 1.0+") So we need to consider how t