I think ARROW-13086 (JIRA
<https://issues.apache.org/jira/browse/ARROW-13086?jql=project%20%3D%20ARROW%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%205.0.0>
/ PR <https://github.com/apache/arrow/pull/10575>) is ready to merge (only
the Travis CI build is failing). If it isn't and I've missed something let
me know I will be able to work on it this evening.

Thanks,
Karik

On Fri, 16 Jul 2021 at 02:41, Neal Richardson <[email protected]>
wrote:

> Hi folks,
> We're down to 32 (non-Rust) JIRA issues [1] left in the 5.0.0 scope, so
> we're close to being release-ready. If you have things you're working on
> for the release, please get them merged in the next day or so or else bump
> them out of scope. I think we can plan on cutting rc0 at the beginning of
> next week. Thanks all for your hard work to get us here.
>
> Neal
>
>
> [1]:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%205.0.0
>
> On Thu, Jul 8, 2021 at 7:10 AM Andrew Lamb <[email protected]> wrote:
>
> > I volunteer / plan to prepare the 5.0 releases for the Arrow Rust
> > implementation (arrow-rs),  which is a separate release artifact, but I
> do
> > not have time to make releases for other languages.
> >
> > On Thu, Jul 8, 2021 at 6:17 AM Alessandro Molina <
> > [email protected]> wrote:
> >
> > > As mentioned in the biweekly sync call, we are approaching the wished
> > date
> > > for the 5.0.0 release, which should happen at the end of next week, or
> > > worst case the week after.
> > >
> > > Apart from my usual recommendation to take a look at the TODO Backlog
> at
> > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+5.0.0+Release
> > and
> > > defer to 6.0.0 any ticket you don't think you will be able to tackle in
> > the
> > > next week or two, I think that we also need to start raising the topic
> of
> > > who is willing to be the release manager for this round.
> > >
> > > At the biweekly call Jorge already mentioned that he might not be able
> to
> > > take care of this release like he did for 4.0.1, so if anyone one else
> is
> > > willing to take over the process I think it would be great to start
> > > assessing who might be able to do so.
> > >
> > > Thanks!
> > > Alessandro
> > >
> >
>

Reply via email to