francis-du commented on issue #7: URL: https://github.com/apache/arrow-datafusion-python/issues/7#issuecomment-1308161472
> I am quite unfamiliar with the release procedure of this repo, but here are my observations on how the basic flow of a release might look like: > > * It seems like the last release was at July with 0.6.0, so we probably need to bump the version tag for this one? > * There is already some automation in place for [building the wheels](https://github.com/apache/arrow-datafusion-python/blob/72f06006ca78ab4bcfcfc10ea3d3f2c2e9e515e9/.github/workflows/build.yml#L18-L22) when an rc version tag is pushed. So we can trigger it and use the artifacts for the release candidate process. > * Once the vote passes, we probably need to repeat these two steps but with the final version (that'd be `0.7.0`). For building wheels for all platforms, I think it makes sense to change the build action to actually be ran on every tag push. > * Downloading the artifacts from the build of 0.7.0, and uploading them to [PyPI using twine](https://github.com/pypa/twine). We don't seem to need to publish to PyPI with `twine`, we can publish directly with [`maturin publish`](https://www.maturin.rs/tutorial.html). -- 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]
