milenkovicm commented on issue #974: URL: https://github.com/apache/datafusion-ballista/issues/974#issuecomment-2490463250
As balista has tight coupling with datafusion, and we cant really mix and match different versions, would it make sense to have same version as datafusion, like datafusion-python does? it would help users to pick right datafusion version (probably we should re-export datafusion in `ballista::datafusion`) main reason we can't have same version as datafusion is that ballista is still not as mature as df is, so we should not use major version > 0. Nothing stopping us to use keep minor version in sync with df major version. This would users with decision which versions to choose in short, proposal is: - use `0.43.0` for next release and keep minor version in sync with datafusion major - use same version as datafusion once ballista get promoted to version 1 wdyt @andygrove ? -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
