errose28 commented on PR #109: URL: https://github.com/apache/ozone-site/pull/109#issuecomment-2542099414
Thanks for looking into this @adoroszlai. I'm also not sure why `ozone-dist` was skipped originally. Maybe this was an attempt to re-use those artifacts from the [original build](https://ozone-site-v2.staged.apache.org/docs/developer-guide/project/release-guide#create-the-release-artifacts)? Is there an extra verification step we can add to the release guide to make sure something like this gets caught during the release cycle? For example if some part of the original build is accidentally cleaned and the `mvn deploy:deploy` uploads partial artifacts. Maybe after [uploading to nexus](https://ozone-site-v2.staged.apache.org/docs/developer-guide/project/release-guide#upload-the-artifacts-to-apache-nexus) we can have the manager download the artifacts from both sources and check if they match. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
