sgilmore10 opened a new issue, #41102: URL: https://github.com/apache/arrow/issues/41102
### Describe the enhancement requested As per @kou's [suggestion](https://github.com/apache/arrow/pull/40956#discussion_r1556447060) in #40956, we should modify the release preparation script (`dev/release/01-prepare.sh`) to create release candidate-specific git tags (i.e. `apache-arrow-{MAJOR}-{MINOR}-{PATCH}-rc{RC_NUM}`) instead of generic release git tags (i.e. `apache-arrow-{MAJOR}-{MINOR}-{PATCH}`). Once a release candidate is approved, the generic release git tag can be created from the approved release candidate's git tag. The new release workflow would be the following: > 1. Create a apache-arrow-X.Y.Z-rc0 tag for X.Y.Z RC0 > 2. (Found a problem for X.Y.Z RC0) > 3. Create a apache-arrow-X.Y.Z-rc1 tag for X.Y.Z RC1 > 4. Vote > 5. Passed > 6. Create a apache-arrow-X.Y.Z tag from apache-arrow-X.Y.Z-rc1 ike apache/arrow-adbc and apache/arrow-flight-sql-postgresql do See @kou's [comment](https://github.com/apache/arrow/pull/40956#discussion_r1556447060) for more details. ### Component(s) Packaging, Release -- 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]
