kou commented on code in PR #7754: URL: https://github.com/apache/arrow-rs/pull/7754#discussion_r2165440511
########## dev/release/README.md: ########## @@ -191,9 +191,16 @@ If the release is not approved, fix whatever the problem is and try again with t ### If the release is approved, -Move tarball to the release location in SVN, e.g. https://dist.apache.org/repos/dist/release/arrow/arrow-4.1.0/, using the `release-tarball.sh` script: +Then, create a new release on GitHub using the tag `<version>` (e.g. `4.1.0`). -Rust Arrow Crates: +Push the release tag to github + +```shell +git tag <version> <version>-<rc> +git push apache <version> +``` + +Move tarball to the release location in SVN, e.g. https://dist.apache.org/repos/dist/release/arrow/arrow-4.1.0/, using the `release-tarball.sh` script: Review Comment: ```suggestion Move tarball to the release location in SVN, e.g. https://dist.apache.org/repos/dist/release/arrow/arrow-rs-4.1.0/, using the `release-tarball.sh` script: ``` ########## dev/release/README.md: ########## @@ -109,21 +109,21 @@ distribution servers. While the official release artifact is a signed tarball, we also tag the commit it was created for convenience and code archaeology. +### Pick a Release Candidate (RC) number Review Comment: "Pick a Release Candidate (RC) number" -> "Create git tag for the release" order may be better: ```diff diff --git a/dev/release/README.md b/dev/release/README.md index 7b2d4f175..e2257b69c 100644 --- a/dev/release/README.md +++ b/dev/release/README.md @@ -105,14 +105,14 @@ create a release candidate using the following steps. Note you need to be a committer to run these scripts as they upload to the apache `svn` distribution servers. -### Create git tag for the release: - -While the official release artifact is a signed tarball, we also tag the commit it was created for convenience and code archaeology. - ### Pick a Release Candidate (RC) number Pick numbers in sequential order, with `1` for `rc1`, `2` for `rc2`, etc. +### Create git tag for the release: + +While the official release artifact is a signed tarball, we also tag the commit it was created for convenience and code archaeology. + Use a string such as `43.0.0` as the `<version>`. Create and push the tag thusly (for example, for version `4.1.0` and `rc2` would be `4.1.0-rc2`): ``` -- 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]
