[
https://issues.apache.org/jira/browse/ARROW-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607673#comment-17607673
]
Jacob Wujciak-Jens commented on ARROW-17353:
--------------------------------------------
Yes all of the files should be named with only the release version and not with
the added date component as you said. While it might be possible to change the
r-binary-packages job to use a different version (it is possible via param but
this was intended for R only patch releases and such) I think it is safer to
integrate the checking/renaming into the actual ruby release script.
> [Release] R libarrow binaries have the wrong version number
> -----------------------------------------------------------
>
> Key: ARROW-17353
> URL: https://issues.apache.org/jira/browse/ARROW-17353
> Project: Apache Arrow
> Issue Type: Bug
> Components: Developer Tools
> Affects Versions: 9.0.0
> Reporter: Jacob Wujciak-Jens
> Priority: Blocker
> Fix For: 10.0.0
>
>
> The libarrow binaries that are uploaded during the release process have the
> wrong version number. This is an issue with the submit binaries
> script/r-binary-packages job. The arrow version should be picked up by the
> job even if not passed explicitly as a custom param.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
