houqp commented on pull request #68: URL: https://github.com/apache/arrow-datafusion/pull/68#issuecomment-929750339
> arrow 6.0 is likely to be released a few weeks from now in mid october, so if we targeted arrow 7.0 (Jan / Feb 2022) as the timeline to converge that would let us get DataFusion over to arrow2 in a few weeks, and then have several months to work out the kinks prior to a real arrow 7.0 release. Obviously Jorge is the best person to answer this question, so please take my words with a grain of salt :) I am not actively working on arrow2 at the moment other than filing annoying issues ;) But from the activities I have observed in the arrow2 repo so far, it probably won't be ready for 1.x release after the arrow 6 release. Jorge is still releasing multiple versions of arrow2 a week, so I am concerned that moving to ASF at its current stage would slow him down unless we start to get significant more contributions to the arrow2 repo. Assuming we won't be able to get arrow2 into ASF in time, I propose we maintain an arrow2 branch in datafusion to buy us more time and reduce downstream impact. I can help maintain that branch and merge with master one or twice a month until arrow2 is ready. If we don't want to pay the cost of maintaining a separate arrow2 datafusion branch, we could also temporarily have datafusion depend the current arrow2 repo with the goal of eventually merging arrow2 with arrow as it matures. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
