Hi folks,
It's time to get oriented for our 3.0.0 Arrow release. We had previously
said that we wanted to be release-ready by the end of this week, but that
seems unlikely. There are a number of challenges in front of us, and we
need to step up and address them. Updating on the points I sent out 3 weeks
ago (see below):

* Release blockers: per
https://cwiki.apache.org/confluence/display/ARROW/Arrow+3.0.0+Release we
are up to 6 blockers, and that's not a complete list. We have failing
nightly builds, and we don't have any macOS crossbow builds due to
Travis-CI limits, so that means no mac wheels at the moment. So we are not
releasable today.
* Backlog: I did some pushing of issues to 4.0 today, so we're down to
180ish open issues tagged for 3.0. Please review your own backlogs and bump
anything you aren't going to get done for this release out.
* Pull requests: https://github.com/apache/arrow/pulls shows 118 open PRs
right now. Some of that is probably a holiday backup, but please do spend
some time reviewing and merging (or closing, if appropriate) so we have
fewer things hanging on past this release.
* Release process: despite the burst of interest a while back, there
doesn't seem to have been any movement on the proposed improvements that
would make it less expensive for us to release, and thus be able to release
more frequently. Nevertheless, we still need to release now, and we will
need someone (I believe from the PMC) to volunteer to be release manager
for 3.0.

If you think you can help on any of these issues, please do! This release
won't happen without some collective effort.

Thanks, and happy 2021 to you all.

Neal


On Mon, Dec 14, 2020 at 11:36 AM Neal Richardson <
neal.p.richard...@gmail.com> wrote:

> Hi all,
> I've created
> https://cwiki.apache.org/confluence/display/ARROW/Arrow+3.0.0+Release,
> cloned from our previous release dashboards, for our upcoming release. A
> few things I'd like to draw your attention to:
>
> * Blockers: there are 5 currently. I'm not certain that they all are
> blockers, nor am I sure that there aren't other blockers. I know we've had
> some issues lately with python wheel builds, and I've added a couple of
> known issues, but there may be others. If you know of other release
> blockers, please note them.
> * There are over 300 unstarted issues tagged for 3.0.0. Given holiday
> schedules and the release target in the first week of January, that's at
> least 200 too many. Please review your backlogs and start bumping things
> out of scope. I've added a 4.0.0 version that you can move things to, if
> you want.
> * Release process improvements: there was some discussion a few weeks ago
> about what could be done to make it easier to cut releases (
> https://lists.apache.org/thread.html/r2257603c91336c042633f2bc480f34f58c02d9c67ff1ee1a212933b5%40%3Cdev.arrow.apache.org%3E).
> A few tasks were mentioned in that thread. If anyone is going to take
> action, now would be a good time.
>
> Thanks,
> Neal
>
>

Reply via email to