Unfortunately, I think we've passed the window for doing a 5.0.1. Since
it's not trivial to make a release, and we're doing 6.0.0 in a couple of
weeks (mid-October), in my opinion it makes most sense to focus our efforts
on making the next release excellent.

Neal


On Mon, Sep 20, 2021 at 4:25 PM Dominik Moritz <domor...@apache.org> wrote:

>  Neal, could you make a release?
>
> On Aug 27, 2021 at 14:43:10, Dominik Moritz <domor...@apache.org> wrote:
>
> > Are there any other changes for 5.0.1? It would be great to release a
> > version with the fixes to the JS bundles since it prevents people from
> > upgrading from Arrow 3.
> >
> > On Jul 30, 2021 at 14:31:59, Neal Richardson <
> neal.p.richard...@gmail.com>
> > wrote:
> >
> >> Let's give it a few more days to see what other issues come up as more
> >> people install 5.0.0, then we can evaluate whether to do a general 5.0.1
> >> patch release for all projects or if we should do something more
> targeted.
> >> A vote on source will be required either way, but we've taken steps to
> >> reduce the burden of making patch releases.
> >>
> >> Neal
> >>
> >> On Fri, Jul 30, 2021 at 1:15 PM Dominik Moritz <domor...@apache.org>
> >> wrote:
> >>
> >> Hi all,
> >>
> >>
> >> We introduced a regression in Arrow that sometimes leads JS code
> bundlers
> >>
> >> to emitting code that is missing some functionality. We have a patch for
> >>
> >> this problem in https://github.com/apache/arrow/pull/10826 that is now
> in
> >>
> >> master. I would like to propose to release Arrow JS 5.0.1 with this
> change
> >>
> >> in it.
> >>
> >>
> >> What’s the process for releasing a patch version? I marked
> >>
> >> https://issues.apache.org/jira/browse/ARROW-12636 as being fixed in
> >> 5.0.1.
> >>
> >> Will this patch be in a 5.0.1 release automatically when we get to a
> >>
> >> general 5.0.1 release (not just JS). The issue isn’t super urgent since
> >> the
> >>
> >> issue exists in Arrow 4 as well but it would be good not to wait until
> >>
> >> Arrow 6.
> >>
> >>
> >> Best wishes,
> >>
> >> Dom
> >>
> >>
> >>
>

Reply via email to