amoeba commented on issue #47081: URL: https://github.com/apache/arrow/issues/47081#issuecomment-3062916702
I understand the goal of doing reproducible builds was primarily so we could do [Automated Release Signing](https://infra.apache.org/release-signing.html#automated-release-signing) (i.e., sign release on GHA). Therefore I think (at at minimum) we only really need to do one test (Proposed approach 2) since presumably everyone verifying the release will be doing a reproducibility check (stipulation 3 on https://infra.apache.org/release-signing.html#automated-release-signing). However, testing reproducibility in more environments on CI before putting out a release for a vote would help us avoid failing release votes. Can you clarify what "Check reproducible source archive on PMC members' machine" is here? Is that a manually step the release manager takes or were you referring to verifying releases during a vote? -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
