houqp commented on issue #771: URL: https://github.com/apache/arrow-datafusion/issues/771#issuecomment-890411309
I have prepared a preview in https://github.com/apache/arrow-datafusion/pull/801. After the PR gets merged, the next step is to create a signed tarball for voting. Here are the generated changelog for each subproject: * https://github.com/houqp/arrow-datafusion/blob/qp_release/datafusion/CHANGELOG.md * https://github.com/houqp/arrow-datafusion/blob/qp_release/python/CHANGELOG.md * https://github.com/houqp/arrow-datafusion/blob/qp_release/ballista/CHANGELOG.md My proposed release process requires adding two new sets of tags: `ballista-x.y.z` and `python-x.y.z`. The `x.y.z` tag will be used to tag release versions for datafusion itself and is required for every voted datafusion release. `ballista-x.y.z` and `python-x.y.z` tags are optional and only needed if we want to release a new version of ballista or python binding together with the same datafusion release. In other words, releasing a new version of python binding or ballista requires a new release of datafusion as well, but not the other way around. I am going to send the proposed release setup to the dev list to gather more feedbacks today. -- 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
