timsaucer opened a new issue, #1025: URL: https://github.com/apache/datafusion-python/issues/1025
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** 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. The reason we have these differences is because we have identified a few discrepancies during the release candidate testing and made corrections. Since test-pypi doesn't allow duplicate files we have taken the approach of updating the candidate version number. This works, but it is sub-optimal. **Describe the solution you'd like** I think we want to update the CI pipeline. When we have a release candidate tag, we do something like ```shell sed -i -e 's/\[project\]/\[project\]\nversion=\"45.0.0rc2\"/' pyproject.toml ``` We'd replace the version with the tag. Then we have the pipeline also run for tagged versions, so `45.0.0` would run and build without this sed command. If we did this, we could still upload our rc candidates just like normal to apache svn and we could upload these rc versions to test-pypi. Then we would only need to push a second tag of the approved release candidate. It would be the same exact code, but rebuilt without the `rc` suffix. **Describe alternatives you've considered** Continue as we are. -- 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.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
