kou commented on PR #13622: URL: https://github.com/apache/arrow/pull/13622#issuecomment-1191006292
Objectives of them are different: Tests in the `r-binary-packages` task is for CI. `dev/release/verify-release-candidate*` is for voting by PMC members. See also: https://www.apache.org/legal/release-policy.html#release-approval > Before casting +1 binding votes, individuals are REQUIRED to download all signed source code packages onto their own hardware, verify that they meet all requirements of ASF policy on releases as described below, validate all cryptographic signatures, compile as provided, and test the result on their own platform. For `dev/release/verify-release-candidate*`, it's better that R tests are run on a PMC member's environment. It may not be covered by the `r-binary-packages` task. For example, I'm using Debian GNU/Linux sid but the environment doesn't exist in the `r-binary-packages` task. Anyway, this can be a follow up task as you said. @nealrichardson Do you want to take a look at this again before we merge this? -- 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]
