Repository navigation
Release DataFusion-Python 53.0.0 #1442
Description
Activity
#1443 for fixing CI
Reacted by Nuno FariaOk, question for both of you: I ran this skill and found a bunch of valid areas where we have APIs upstream that were never exposed in Python. Now have a handful of PRs to resolve all of them. They're all originally AI generated but I've been personally reviewing each one (and making changes) before marking it ready for review.
Question is: should we wait to get all these in and then start the DF53 release or start the release now and get those all in for 54?
Question is: should we wait to get all these in and then start the DF53 release or start the release now and get those all in for 54?
I think we can try to merge them first. With that said, could there also be a
53.1.0feature release to handle those new APIs, or does the versioning need to be in sync with DataFusion?I think we're in a good spot. I'd like to purge those deprecated APIs and then start release. What do you think?
I'll start the release :)
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Publish the next version of
datafusion-pythonnow thatdatafusion-53is out.I noticed that the CI is failing (OOM?), so that has to be fixed first.
@timsaucer are there any TODOs that need to be done before the next version can be published?
PRs to merge
Issues to close