andygrove commented on issue #2511: URL: https://github.com/apache/datafusion-ballista/issues/2511#issuecomment-5940676536
> do we move python to datafusion-ballista-python at the end? it would make sense if we have different release process. I don't see much value in moving it out, personally. A separate release process doesn't need a separate repo: https://github.com/apache/datafusion-ballista/pull/2512 tags the Python releases on the same release branch and builds the source tarball from just python/. Keeping it in this repo also makes it easy to run the client's tests against a cluster built from main, which is how https://github.com/apache/datafusion-ballista/pull/2374 caught the wire break in https://github.com/apache/datafusion-ballista/issues/2376. And the last time we moved it out (https://github.com/apache/datafusion-ballista/issues/635), it went unmaintained for about a year before https://github.com/apache/datafusion-ballista/pull/970 brought it back. -- 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]
