alamb opened a new issue, #775: URL: https://github.com/apache/arrow-rs-object-store/issues/775
**Is your feature request related to a problem or challenge?** When we push a `<version>` tag (e.g. `0.14.0`) to GitHub, it automatically creates a GitHub "Release". In our current process this tag is pushed while preparing the release *candidate*, before the ASF vote has passed and before publishing to crates.io. This causes confusion: people watching the repo see what looks like an official `0.14.0` release before it is officially approved and available on crates.io. See the confusion this caused on the 0.14.0 release thread: - https://github.com/apache/arrow-rs-object-store/issues/657#issuecomment-4768526354 - (and my response: https://github.com/apache/arrow-rs-object-store/issues/657#issuecomment-4768622326) Per ASF guidelines, nothing should be presented as a release until the release vote has passed. **Prior art** `arrow-rs` hit and fixed the exact same problem: - Issue: https://github.com/apache/arrow-rs/issues/7753 - Fix: https://github.com/apache/arrow-rs/pull/7754 Their fix was to only tag `X.Y.Z-rcN` before the vote, and push the bare `X.Y.Z` tag (which creates the GitHub release) only as part of the *post-approval* steps. This matches the DataFusion release process. **Describe the solution you'd like** Update `dev/release/README.md` and the release scripts so that: 1. During RC preparation we only create/push `X.Y.Z-rcN` tags (not the bare `X.Y.Z` tag). - Currently `dev/release/README.md` (the "Create git tag for the release" step) pushes the plain `<version>` tag *before* the vote. 2. The bare `X.Y.Z` tag is only created and pushed in the post-vote / post-approval steps, so the GitHub Release only appears after the release is officially approved. 3. Update `dev/release/create-tarball.sh` (and any other scripts that reference the tag) to match the new scheme, as needed. **Additional context** Follow-on from the 0.14.0 release: https://github.com/apache/arrow-rs-object-store/issues/657 -- 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]
