jonkeane commented on PR #45173: URL: https://github.com/apache/arrow/pull/45173#issuecomment-2571367234
I'm trying to get a release ready to send to CRAN before our 14 January deadline. The only operative change that this branch has is https://github.com/apache/arrow/pull/45173/commits/cc4e0f31dc18c7b57846295936ee3172dd967674 (I also had to backport @amoeba 's CI fixes thanks for those!). The binary job runs, but I don't actually know the process to get the binaries that are created in the CI job to the jfrog repository. @amoeba @assignUser any thoughts about what to do here? Is this a manual step (with key signing and all of that)? I wanted to make the version 18.1.0.1 (that's why the branch is named such) since it's just this one patch to a dependency, but our version number + binary finder only looks at the first three version components https://github.com/apache/arrow/blob/3752109d64e3a02eaaa636a037141a51fae46819/r/tools/nixlibs.R#L967 Or maybe we could exploit this fact slightly and release 18.1.0.1, use the released 18.1.0 binaries everywhere, but include the patch in the source code (which is what CRAN will build + check with GCC15). That's a little bit funny because the binary folks are using is slightly different from the source version, but I'm pretty sure that would work. cc @nealrichardson and @thisisnic here too if there are 🚨 that that would be a bad plan. -- 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]
