alamb commented on issue #292: URL: https://github.com/apache/arrow-rs/issues/292#issuecomment-841652592
Here is what I am thinking for the release workflow (based on the main apache release flow. The major difference is that there is no Release Candidate) Proposal: 1. Update version on active_release branch with proposed release number 2. create tag from active_release branch with proposed release number 1. Make a candidate release .tar.gz file with signatures + Upload to apache distro dev dev, e.g. https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-rs-4.1.0/ 3. Propose release of that rc on the mailing list 4. if approved: move tarball to release, e.g. https://dist.apache.org/repos/dist/release/arrow/apache-arrow-rs-4.1.0/ 5. If not approved, fix whatever the problem is and make a new tag, with a new minor release (aka don't make "RC / release candidates, just skip minor versions) We will then treat uploading to crates.io as a post official release task done from the official source I hope to have a script for most of this process (other than the email / approval). -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
