hi folks, We've had a rough couple of weeks in our PR queue due to various CI issues causing a high incidence of build failures:
* Package dependency upgrades (Thrift -- this has been fixed) * Failures due possibly to VM setting changes in Travis CI (memory thrashing / VM timeouts, see ARROW-2062, ARROW-2071) * apt flakiness (this is still ongoing, see ARROW-2021) Meanwhile, at the moment, we have 37 open PRs (https://github.com/apache/arrow/pulls). Some of these are stale and need to either be reviewed, updated, or closed. We have many other PRs that need to be rebased (builds should mostly pass now if rebased on master) and/or reviewed. I've been doing the best I can do keep up with the PR queue (and others have been reviewing and merging PRs, too), but it's currently not enough to keep up, and there's a lot of development work for the 0.9.0 milestone that I'd like to also be doing. The project is growing fast -- both in users and new developers. Just on a single install path for the Python libraries, Arrow is being installed _over 1000 times per day_ (https://anaconda.org/conda-forge/pyarrow) -- when you add up all the install paths it is likely to be much more than that. Reviews and help maintaining PRs from the community, but especially from other committers and PMC members, would be especially useful right now to get the project operating smoothly with a steady stream of high quality patches making their way into master. If there's anything else we can do to improve developer and community productivity in Arrow right now, I'm open to ideas. Thanks, Wes
