kou commented on PR #14396: URL: https://github.com/apache/arrow/pull/14396#issuecomment-1279845567
> Do I understand correctly you added the `arrow.repo` option so binary verification from the staging area of the artifactory is possible? No. I added it for using the artifacts (built in the current `r-binary-packages` task) at local. But we can use it to verify the artifacts at https://apache.jfrog.io/ui/native/arrow/r-rc/ in `dev/release/verify-release-candidate.sh`. (It's out of scope of this pull request.) > The only issue I see is that for R packages the usual convention for dev versions is `last.released.version.large_numeric_component` compared with the use of `future.release.version.dev_int` in the other components. Changing that might cause confusion in the R nightly users (not sure how big that group is?). OK. I've changed to use `9.0.0.${1_0000_00_00 + dev_int}` (without `--arrow-version` / see https://github.com/apache/arrow/pull/14396#issuecomment-1279843385 / `1_0000_00_00 + ` is just for generating a greater number than `YYYYMMDD`. We can just use `9000` instead if we don't need to care existing developers who use our nightly packages) and `10.0.0` (with `--arrow-version 10.0.0-rc1` / see https://github.com/apache/arrow/pull/14396#issuecomment-1279843418 ). -- 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]
