kszucs commented on pull request #11263: URL: https://github.com/apache/arrow/pull/11263#issuecomment-933396901
> After: > > For RC: > 1. Download the built .deb/.rpm for RC > 2. Sign the built .deb/.rpm > 3. Generate metadata for APT/Yum repositories for the built and signed .deb/.rpm > 4. Download metadata for APT/Yum repositories from [https://apache.jfrog.io/ui/native/arrow/{debian,centos,...}](https://apache.jfrog.io/ui/native/arrow/%7Bdebian,centos,...%7D) > 5. Merge metadata of 3. and 4. > 6. Upload the built and signed .deb/.rpm and the merged metadata for APT/Yum repositories to [https://apache.jfrog.io/ui/native/arrow/{debian,centos,...}-rc](https://apache.jfrog.io/ui/native/arrow/%7Bdebian,centos,...%7D-rc) > Aren't the RC and non-RC repositories have the own metadata? Previously we had different versions uploaded to them. > Some problems may exist because I can't test with Artifactory. Because I don't have staging environment. I'll fix remained problems in the release process for 6.0.0. Is `packages.groonga.org` hosted on artifactory? Couldn't we use a new postfix, like `{debian,centor,...}-staging` to test the new upload script on the apache artifactory account? -- 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]
