kou opened a new pull request, #45903: URL: https://github.com/apache/arrow/pull/45903
### Rationale for this change We're using apache.jfrog.io for binary artifacts mainly for APT/Yum repositories. But apache.jfrog.io isn't stable as we expected. For example, it was down annually. See also: #40744 FYI: Based on https://issues.apache.org/jira/browse/INFRA-26324 , it will not be down this year. ### What changes are included in this PR? Use repository.apache.org instead of apache.jfrog.io. Existing binary artifacts are already copied to repository.apache.org from apache.jfrog.io. For example: https://repo1.maven.org/maven2/org/apache/arrow/debian/ Migration plan: 1. We use repo1.maven.org (it's a CDN of repository.apache.org) in apache-arrow-apt-source (for APT repositories) and apache-arrow-release (for Yum repositories) 2. We keep uploading only apache-arrow-apt-source (for APT repositories) and apache-arrow-release (for Yum repositories) to apache.jfrog.io * Existing users can migrate to repository.apache.org automatically by this 3. We'll stop uploading apache-arrow-apt-source (for APT repositories) and apache-arrow-release (for Yum repositories) to apache.jfrog.io after we use reproducible builds based auto signing * We'll not change signing key after this ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. -- 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]
