Description
Is your feature request related to a problem or challenge?
Up to now, when we have made DataFusion releases, we have mostly focused on validated that DataFusion's own unit tests have passed, (see dev/release/README.md) but haven't tested the upgrade with other downstream projects (like ballista, ray, InfluxDB IOx, etc) until after we have release the code
This results sometimes in downstream users finding issues after release. Some recent examples
- delta-rs upgrade: chore: upgrade to datafusion 43 delta-io/delta-rs#2886
- Simplify expressions swallows a cast expression #13481
- Regression in 43.0.0: coalesce no longer works between Utf8 and Utf8View columns #13568
- Regression:
Invalid comparison operation: Utf8 == Utf8View
error during LEFT ANTI JOIN #13510
Describe the solution you'd like
I would like to improve the testing / release process for DataFusion releases to reduce the number of regressions found after release.
This would likely take the form of updating the dev/release/README.md
Describe alternatives you've considered
One idea mentioned by @Omega359 and @andygrove on #13525 (comment)
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.
Additional context
No response