andygrove commented on issue #13525: URL: https://github.com/apache/datafusion/issues/13525#issuecomment-2496487538
> I have felt the pain points of the version upgrades. I mentioned this in the discord server, but one thing I think we can do that will lessen this is to push hard to get the `datafusion-python` upgrade PR through as fast as we can once a release candidate is ready for `datafusion`. Then we can document all the changes we had to make for it and add them to the release notes. It would be good to have a page similar to what pyo3 does with their [migration guide](https://pyo3.rs/v0.23.1/migration.html). I know this might slow down the release process but I think it would be a good thing to do since part of our goal is to have `datafusion-python` expose most of `datafusion`. It won't catch everything, so we might also want to ask any PRs with breaking API changes to document what users need to do for migration. Spark provides an upgrade guide for major new versions. Perhaps we could do the same? Any PR that is a breaking change should also include updates to the upgrade guide for the next release. Upgrading our own subprojects (Ballista, Comet, DF Python, DF Ray) as part of the DataFusion release process makes a lot of sense to validate that the upgrade guide is complete. -- 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]
