andygrove commented on issue #2370: URL: https://github.com/apache/datafusion-ballista/issues/2370#issuecomment-5427818369
I'm going around in circles thinking about this. We currently have one vote for both Ballista and PyBallista for the same version, and consequences are: - We have to wait for datafusion-python release before we can release ballista - Python users can help test the release and vote on it If we split into separate release cycles for ballista vs PyBallista: - We will need separate create-tarball/release-tarball scripts for each and separate votes for each - It will be more difficult for Python users to vote on ballista releases - When we start the vote on PyBallista, there could be issues with the already released Ballista crates. This would generate additional work for patch releases and more release votes -- 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]
