Thanks for the update and effort Wes! On Wed, Mar 28, 2018 at 4:40 PM, Julian Hyde <[email protected]> wrote:
> +1 > > Great move. > > Your presence looms large over this project, so stepping back will give > others the chance to take the lead. > > I know (from other projects) how oppressive it is to be the main “go to” > person in a project. It irks me, for instance, when people address comments > in PRs directly to me when they could be addressed by several other people > in the community. > > Enjoy your time off. You’ve earned it. > > Julian > > > > On Mar 28, 2018, at 4:19 PM, Wes McKinney <[email protected]> wrote: > > > > hi folks, > > > > It's been quite a lot of work the last few years building the Apache > > Arrow project and community until this point. I began working on some > > flavor of an Arrow-like project in early 2015, later merging with the > > efforts of folks from Apache {Drill, Calcite, Kudu, Impala, Spark, > > ...} and other OSS projects and the rest is now history. > > > > I am definitely in need of an extended vacation from day-to-day > > maintenance and development; truthfully I have not been writing as > > many patches as usual this year so far due to how overwhelming the > > activity level and deluge of user feedback (bug reports, StackOverflow > > questions, etc.) has been. > > > > I'm going to try to review the most important pending PRs (out of the > > 40 open right now) over the next few days, but I plan to be mostly > > absent from day-to-day maintainer work until May. > > > > If you need my attention on something time sensitive related to > > development, I'm happy to be available -- please reach out to me > > directly. I will still be available for time-sensitive PMC-related > > activities also. I'm giving some talks about Arrow over the next 6 > > weeks, so I'll be working for the interests of the project in other > > ways, just less active on GitHub and JIRA. > > > > I want to reiterate how important packaging / release automation and > > nightly integration testing (being discussed in a separate thread > > right now) are to the current and future health of the project. I hope > > we can develop a scalable solution to this problem within the next > > couple of months. > > > > Thanks, > > Wes > >
