Can we propose getting changes other than Python or Parquet related into this 
release?

For example, I found a critical issue in the C# implementation that, if 
possible, I'd like to get included in a patch release.  
https://github.com/apache/arrow/pull/4836

Eric

-----Original Message-----
From: Wes McKinney <wesmck...@gmail.com> 
Sent: Tuesday, July 9, 2019 7:59 AM
To: dev@arrow.apache.org
Subject: Re: [DISCUSS] Need for 0.14.1 release due to Python package problems, 
Parquet forward compatibility problems

On Tue, Jul 9, 2019 at 12:02 AM Sutou Kouhei <k...@clear-code.com> wrote:
>
> Hi,
>
> > If the problems can be resolved quickly, I should think we could cut 
> > an RC for 0.14.1 by the end of this week. The RC could either be cut 
> > from a maintenance branch or out of master -- any thoughts about 
> > this (cutting from master is definitely easier)?
>
> How about just releasing 0.15.0 from master?
> It'll be simpler than creating a patch release.
>

I'd be fine with that, too.

>
> Thanks,
> --
> kou
>
> In <CAJPUwMBPaz7zLBkBcVo-r=nmvwuy8wxxddcctobuuamy4ee...@mail.gmail.com>
>   "[DISCUSS] Need for 0.14.1 release due to Python package problems, Parquet 
> forward compatibility problems" on Mon, 8 Jul 2019 11:32:07 -0500,
>   Wes McKinney <wesmck...@gmail.com> wrote:
>
> > hi folks,
> >
> > Perhaps unsurprisingly due to the expansion of our Python packages, 
> > a number of things are broken in 0.14.0 that we should fix sooner 
> > than the next major release. I'll try to send a complete list to 
> > this thread to give a status within a day or two. Other problems may 
> > arise in the next 48 hours as more people install the package.
> >
> > If the problems can be resolved quickly, I should think we could cut 
> > an RC for 0.14.1 by the end of this week. The RC could either be cut 
> > from a maintenance branch or out of master -- any thoughts about 
> > this (cutting from master is definitely easier)?
> >
> > Would someone (who is not Kou) be able to assist with creating the RC?
> >
> > Thanks,
> > Wes

Reply via email to