[DISCUSS] Need for 0.17.2 patch release?

[Wes McKinney <we...@gmail.com>]

In light of ARROW-8860 and perhaps some other critical bugs that have
been reported, and since our releases have been going more smoothly,
what do people think about doing another patch release in a week or
two?

Re: [DISCUSS] Need for 0.17.2 patch release?

[Joris Van den Bossche <jo...@gmail.com>]

Just from judging by the actual bug (nested data support in Feather is
indeed a new feature, but it's also one of the key highlights of that new
feature), I personally think it would be worth doing another bugfix release
(at least for C++ and dependent packages).
Of course, our release process is quite complicated .. So taking that into
account as well, I have a less strong opinion.

Joris

On Sun, 24 May 2020 at 18:57, Antoine Pitrou <an...@python.org> wrote:

>
> I'm fine with going for a 1.0 in the July timeframe.
>
> Regards
>
> Antoine.
>
>
> Le 23/05/2020 à 00:18, Wes McKinney a écrit :
> > That sounds fine to me, mostly was curious about what others thought.
> >
> > On Fri, May 22, 2020 at 5:01 PM Neal Richardson
> > <ne...@gmail.com> wrote:
> >>
> >> I'm not convinced (but open to persuasion) that ARROW-8860 alone merits
> the
> >> effort of a patch release. It's unfortunate but has a number of
> >> workarounds/alternatives, and it's arguably not a regression but rather
> a
> >> bug in a new feature. Plus, there are (unofficial) nightly Python and R
> >> packages available for anyone who must have a fix right away.
> >>
> >> Personally, I'd rather see us focus our efforts on getting a rock-solid
> 1.0
> >> out the door in 5-6 weeks time.
> >>
> >> Neal
> >>
> >> On Fri, May 22, 2020 at 1:50 PM Wes McKinney <we...@gmail.com>
> wrote:
> >>
> >>> Given some of the biggish projects (eg C++ kernels ARROW-8792) ongoing
> I'd
> >>> be slightly concerned about cutting a release out of master right away
> >>> until a little more time has passed, but I can see arguments both ways
> >>>
> >>> On Fri, May 22, 2020, 3:40 PM Krisztián Szűcs <
> szucs.krisztian@gmail.com>
> >>> wrote:
> >>>
> >>>> The amount of effort required to create a patch release is comparable
> >>>> to a minor release. How about we should create a 0.18 minor release
> >>>> instead?
> >>>>
> >>>> On Fri, May 22, 2020 at 3:54 PM Wes McKinney <we...@gmail.com>
> >>> wrote:
> >>>>>
> >>>>> In light of ARROW-8860 and perhaps some other critical bugs that have
> >>>>> been reported, and since our releases have been going more smoothly,
> >>>>> what do people think about doing another patch release in a week or
> >>>>> two?
> >>>>
> >>>
>

Re: [DISCUSS] Need for 0.17.2 patch release?

[Antoine Pitrou <an...@python.org>]

I'm fine with going for a 1.0 in the July timeframe.

Regards

Antoine.


Le 23/05/2020 à 00:18, Wes McKinney a écrit :
> That sounds fine to me, mostly was curious about what others thought.
> 
> On Fri, May 22, 2020 at 5:01 PM Neal Richardson
> <ne...@gmail.com> wrote:
>>
>> I'm not convinced (but open to persuasion) that ARROW-8860 alone merits the
>> effort of a patch release. It's unfortunate but has a number of
>> workarounds/alternatives, and it's arguably not a regression but rather a
>> bug in a new feature. Plus, there are (unofficial) nightly Python and R
>> packages available for anyone who must have a fix right away.
>>
>> Personally, I'd rather see us focus our efforts on getting a rock-solid 1.0
>> out the door in 5-6 weeks time.
>>
>> Neal
>>
>> On Fri, May 22, 2020 at 1:50 PM Wes McKinney <we...@gmail.com> wrote:
>>
>>> Given some of the biggish projects (eg C++ kernels ARROW-8792) ongoing I'd
>>> be slightly concerned about cutting a release out of master right away
>>> until a little more time has passed, but I can see arguments both ways
>>>
>>> On Fri, May 22, 2020, 3:40 PM Krisztián Szűcs <sz...@gmail.com>
>>> wrote:
>>>
>>>> The amount of effort required to create a patch release is comparable
>>>> to a minor release. How about we should create a 0.18 minor release
>>>> instead?
>>>>
>>>> On Fri, May 22, 2020 at 3:54 PM Wes McKinney <we...@gmail.com>
>>> wrote:
>>>>>
>>>>> In light of ARROW-8860 and perhaps some other critical bugs that have
>>>>> been reported, and since our releases have been going more smoothly,
>>>>> what do people think about doing another patch release in a week or
>>>>> two?
>>>>
>>>

Re: [DISCUSS] Need for 0.17.2 patch release?

[Wes McKinney <we...@gmail.com>]

That sounds fine to me, mostly was curious about what others thought.

On Fri, May 22, 2020 at 5:01 PM Neal Richardson
<ne...@gmail.com> wrote:
>
> I'm not convinced (but open to persuasion) that ARROW-8860 alone merits the
> effort of a patch release. It's unfortunate but has a number of
> workarounds/alternatives, and it's arguably not a regression but rather a
> bug in a new feature. Plus, there are (unofficial) nightly Python and R
> packages available for anyone who must have a fix right away.
>
> Personally, I'd rather see us focus our efforts on getting a rock-solid 1.0
> out the door in 5-6 weeks time.
>
> Neal
>
> On Fri, May 22, 2020 at 1:50 PM Wes McKinney <we...@gmail.com> wrote:
>
> > Given some of the biggish projects (eg C++ kernels ARROW-8792) ongoing I'd
> > be slightly concerned about cutting a release out of master right away
> > until a little more time has passed, but I can see arguments both ways
> >
> > On Fri, May 22, 2020, 3:40 PM Krisztián Szűcs <sz...@gmail.com>
> > wrote:
> >
> > > The amount of effort required to create a patch release is comparable
> > > to a minor release. How about we should create a 0.18 minor release
> > > instead?
> > >
> > > On Fri, May 22, 2020 at 3:54 PM Wes McKinney <we...@gmail.com>
> > wrote:
> > > >
> > > > In light of ARROW-8860 and perhaps some other critical bugs that have
> > > > been reported, and since our releases have been going more smoothly,
> > > > what do people think about doing another patch release in a week or
> > > > two?
> > >
> >

Re: [DISCUSS] Need for 0.17.2 patch release?

[Neal Richardson <ne...@gmail.com>]

I'm not convinced (but open to persuasion) that ARROW-8860 alone merits the
effort of a patch release. It's unfortunate but has a number of
workarounds/alternatives, and it's arguably not a regression but rather a
bug in a new feature. Plus, there are (unofficial) nightly Python and R
packages available for anyone who must have a fix right away.

Personally, I'd rather see us focus our efforts on getting a rock-solid 1.0
out the door in 5-6 weeks time.

Neal

On Fri, May 22, 2020 at 1:50 PM Wes McKinney <we...@gmail.com> wrote:

> Given some of the biggish projects (eg C++ kernels ARROW-8792) ongoing I'd
> be slightly concerned about cutting a release out of master right away
> until a little more time has passed, but I can see arguments both ways
>
> On Fri, May 22, 2020, 3:40 PM Krisztián Szűcs <sz...@gmail.com>
> wrote:
>
> > The amount of effort required to create a patch release is comparable
> > to a minor release. How about we should create a 0.18 minor release
> > instead?
> >
> > On Fri, May 22, 2020 at 3:54 PM Wes McKinney <we...@gmail.com>
> wrote:
> > >
> > > In light of ARROW-8860 and perhaps some other critical bugs that have
> > > been reported, and since our releases have been going more smoothly,
> > > what do people think about doing another patch release in a week or
> > > two?
> >
>

Re: [DISCUSS] Need for 0.17.2 patch release?

[Wes McKinney <we...@gmail.com>]

Given some of the biggish projects (eg C++ kernels ARROW-8792) ongoing I'd
be slightly concerned about cutting a release out of master right away
until a little more time has passed, but I can see arguments both ways

On Fri, May 22, 2020, 3:40 PM Krisztián Szűcs <sz...@gmail.com>
wrote:

> The amount of effort required to create a patch release is comparable
> to a minor release. How about we should create a 0.18 minor release
> instead?
>
> On Fri, May 22, 2020 at 3:54 PM Wes McKinney <we...@gmail.com> wrote:
> >
> > In light of ARROW-8860 and perhaps some other critical bugs that have
> > been reported, and since our releases have been going more smoothly,
> > what do people think about doing another patch release in a week or
> > two?
>

Re: [DISCUSS] Need for 0.17.2 patch release?

[Krisztián Szűcs <sz...@gmail.com>]

The amount of effort required to create a patch release is comparable
to a minor release. How about we should create a 0.18 minor release
instead?

On Fri, May 22, 2020 at 3:54 PM Wes McKinney <we...@gmail.com> wrote:
>
> In light of ARROW-8860 and perhaps some other critical bugs that have
> been reported, and since our releases have been going more smoothly,
> what do people think about doing another patch release in a week or
> two?