timsaucer commented on issue #1399: URL: https://github.com/apache/datafusion-python/issues/1399#issuecomment-3984356568
Case in point: @nuno-faria has this nice PR to prepare for the next release: https://github.com/apache/datafusion-python/pull/1402 That's a big change. It would be nice to merge it in early so that we can stabilize any new work that goes in between now and when 53 releases. One pressure I feel frequently is community members asking when df-python will be available once the upstream repo releases. Sometimes we get the question on the same day! I know of at least 3 repos that use both datafusion internally and datafusion-python as well. These repos get held up on the delay. We could go as @ion-elgreco suggests and move towards merging into the datafusion upstream repository. I suspect that would not be desired by many of the maintainers of the upstream repo to take on the additional responsibility, but I honestly don't know what the temperature of that room is. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
