kevinjqliu commented on issue #1025: URL: https://github.com/apache/datafusion-python/issues/1025#issuecomment-2664276975
> Currently we have a divergence in a few releases in the datafusion-python version number and their upstream datafusion they rely on. This isn't a big problem but it does bring questions from time to time about why we have DataFusion 43.0.0 but datafusion-python 43.1.0. I just assumed that the major version is what people are expecting to align. For example, `datafusion` 43 is used for `datafusion-python` 43. > Since test-pypi doesn't allow duplicate files we have taken the approach of updating the candidate version number. Here's the process we use for pyiceberg; i just updated the entire release process. https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/how-to-release.md#publishing-a-release-candidate-rc We create both SVN and PYPI artifacts by using Github Action ([python-release.yml](https://github.com/apache/iceberg-python/blob/main/.github/workflows/python-release.yml)) which can be downloaded and re-uploaded to their respective locations. In the PYPI build, the `pyproject.toml` version number is overwritten to one with RC suffix, i.e. `0.8.0rc1` ([1](https://github.com/apache/iceberg-python/blob/e927aee874cdd3c60fc11425770767cececa4606/.github/workflows/python-release.yml#L133), [2](https://github.com/apache/iceberg-python/blob/e927aee874cdd3c60fc11425770767cececa4606/.github/workflows/pypi-build-artifacts.yml#L53-L56)) But in SVN build, the current version number is used, i.e. `0.8.0`. ([1](https://github.com/apache/iceberg-python/blob/main/.github/workflows/svn-build-artifacts.yml)) When the vote passes, we just move the SVN artifact from the apache `dev/` folder to the `release/` folder https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/how-to-release.md#upload-the-accepted-rc-to-apache-release-svn Otherwise, we generate another candidate. Happy to help out here. -- 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
