Release version 0.7.0

[andygrove]

I would like to propose releasing version 0.7.0.

Checklist:

• Run Apache RAT (Release Audit Tool) in CI #31
• Add instructions and scripts for publishing the Python documentation #33
• Publish release candidate
• Start vote
• Vote passes
• Publish Python artifacts to PyPi
• Publish documentation for Python bindings #39

[francis-du]

I would like to participate in the release process to familiarize myself with the ASF specification.

[andygrove]

I would like to see us start releasing this project again, but I don't have sufficient knowledge about Python. I would love to pair with someone to get a release out.

@isidentical I was curious - do you have any interest in the DataFusion Python bindings?

[jimexist]

I used to do release while it is hosted in datafusion-contrib org, if help is needed I can share more.

[andygrove]

I used to do release while it is hosted in datafusion-contrib org, if help is needed I can share more.

Thanks @jimexist. Is there any documentation on how to do the release? I guess the first step is getting this kind of documentation into the repo.

[isidentical]

@andygrove @jimexist also let me know if there is anything I can help with.

[isidentical]

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 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.

[francis-du]

I'm interested in doing some work on this, anyone who needs my help please assign me.

[francis-du]

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 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.

• We don't seem to need to publish to PyPI with twine, we can publish directly with maturin publish.

• For building wheels, here is a GiHub Action example, I don't know if it can be used directly.

[andygrove]

maturin publish sounds good. Is publishing to PyPi enough for this release? How important is it to publish wheels?

[andygrove]

If we are ok with just running maturin publish for now, I think we could go ahead and create a release candidate, vote on it, then run that command to publish?

[francis-du]

If we are ok with just running maturin publish for now, I think we could go ahead and create a release candidate, vote on it, then run that command to publish?

I think these are enough, does @isidentical has anything else to add?