houqp commented on issue #771: URL: https://github.com/apache/arrow-datafusion/issues/771#issuecomment-888017641
I also prefer we go with our own versioning scheme to better adhere to semantic versioning at the very least for ballista and datafusion python binding. For datafusion the ship has already sailed unfortunately. If we are to release datafusion and ballista together, how do we manage the version differences? Do we just name the same tarball with different names? Or do we actually produce two different release tarballs with project specific sources? Regardless what versioning scheme we use, the datafusion python documentation would still be needed. @Jimexist perhaps you could hep start building the automation for that? -- 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...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
