Re: Coordinating Arrow 0.8.0 end-game

2017-12-10 Thread Wes McKinney
I put up the last patches -- once these are merged I can start the RC1 vote tomorrow if no huge issues arise. On Sat, Dec 9, 2017 at 9:18 AM, Uwe L. Korn wrote: > From my side, it also look like everything is ready for a release. > > Cheers > Uwe > > On Fri, Dec 8, 2017, at 08:38 PM, Wes McKinney

Re: Coordinating Arrow 0.8.0 end-game

2017-12-09 Thread Uwe L. Korn
>From my side, it also look like everything is ready for a release. Cheers Uwe On Fri, Dec 8, 2017, at 08:38 PM, Wes McKinney wrote: > It looks like we are in pretty good shape to release next week. We > have a handful of Python / C++ patches in flight, but I'm hopefully > we'll be in position to

Re: Coordinating Arrow 0.8.0 end-game

2017-12-08 Thread Wes McKinney
It looks like we are in pretty good shape to release next week. We have a handful of Python / C++ patches in flight, but I'm hopefully we'll be in position to cut the RC1 on Monday or Tuesday. On Thu, Dec 7, 2017 at 11:47 AM, Uwe L. Korn wrote: > The turbodbc side is fixed, we sadly did some brea

Re: Coordinating Arrow 0.8.0 end-game

2017-12-07 Thread Uwe L. Korn
The turbodbc side is fixed, we sadly did some breaking changes: https://github.com/blue-yonder/turbodbc/pull/138 It would be nice if we could keep these APIs stable in the next releases as we get more and more users of them. Uwe On Thu, Dec 7, 2017, at 01:09 AM, Bryan Cutler wrote: > Thanks, Wes

Re: Coordinating Arrow 0.8.0 end-game

2017-12-06 Thread Bryan Cutler
Thanks, Wes. The only outstanding issue on the Java side is ARROW-1864 Upgrading Netty to 4.1.x https://github.com/apache/arrow/pull/1376. The other issues have been resolved or pushed back. On Wed, Dec 6, 2017 at 5:08 AM, Tom Augspurger wrote: > I've reproduced the dask failures and am looking

Re: Coordinating Arrow 0.8.0 end-game

2017-12-06 Thread Tom Augspurger
I've reproduced the dask failures and am looking into them now (it's around index metadata). On Wed, Dec 6, 2017 at 3:52 AM, Uwe L. Korn wrote: > Hello all, > > I'm just executing the current master locally against turbodbc and dask. > Sadly it seems that the unit tests in both projects are brea

Re: Coordinating Arrow 0.8.0 end-game

2017-12-06 Thread Uwe L. Korn
Hello all, I'm just executing the current master locally against turbodbc and dask. Sadly it seems that the unit tests in both projects are breaking. I'm going to have a look at what happens in both. We should sort out these problems before the release. Uwe On Mon, Dec 4, 2017, at 08:06 PM, Wes

Coordinating Arrow 0.8.0 end-game

2017-12-04 Thread Wes McKinney
hi folks, I wanted to start a coordination thread to stay on top of the remaining items to be able to get to a release-able state for 0.8.0, by end of this week or beginning of next week with any luck. There are a number of housekeeping items we are working on the C++/Python side, but some of thes