You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ok, 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.0 feature release to handle those new APIs, or does the versioning need to be in sync with DataFusion?
Activity
kevinjqliu commentedon Mar 25, 2026
#1443 for fixing CI
timsaucer commentedon Apr 1, 2026
Ok, 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?
nuno-faria commentedon Apr 1, 2026
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?timsaucer commentedon Apr 8, 2026
I think we're in a good spot. I'd like to purge those deprecated APIs and then start release. What do you think?
timsaucer commentedon Apr 9, 2026
I'll start the release :)