raulcd commented on issue #48000: URL: https://github.com/apache/arrow/issues/48000#issuecomment-3467094524
We sign and upload source and binaries to the RC release on GitHub from our workflows instead of Artifactory which we did in the past. The rest of our workflows and release scripts expect the binaries there to download and verify them. Once the release is approved, our GitHub release is created and we just copy all the artifacts that were part of the release candidate, this has proven useful for example for the released source, i. e. when conda has issues with old releases being throttled from Apache and they just point to the GitHub release. As per wheels, we use those to just download locally and publish to PyPI, whether we should add them to the final GitHub release or not can be discussed. -- 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]
