adnanhemani commented on code in PR #4114: URL: https://github.com/apache/polaris/pull/4114#discussion_r3034326258
########## site/content/community/release-guides/release-verification-guide.md: ########## @@ -181,50 +173,13 @@ After that, release candidate verification starts immediately, performing the fo 5. Helm chart GPG signature and checksum checks 6. Source tarball and binary artifacts GPG signature and checksum checks 7. Build Polaris from the Git commit/tag -8. Compares that the list of Maven artifacts produced by the build matches those in the Nexus staging repository. -9. Compares the individual Maven artifacts of the local build with the ones in the Nexus staging repository. -10. Compares the main binary distribution artifacts for Polaris server and Polaris admin tool. -11. Compares the locally built Helm chart with the one in the staging repository. +8. Checks mandatory LICENSE/NOTICE content in Maven JARs (excluding Spark JARs) and distribution archives. +9. Checks mandatory LICENSE/NOTICE content in the Helm chart. Found issues are reported on the console in _red_. -Details for each reported issue will be reported in the log file, depending on the issue and file type. -The intent is to provide as much information as possible to eventually fix a reproducible build issue. -* Text files: Output of `diff` of the local and staged files. -* Zip/Jar files: output of `zipcmp`. - If `zipcmp` reports no difference, the output of `zipinfo` for both files is logged. -* Tarballs: output of `diff --recursive` the extracted local and staged tarballs. - If `diff` reports no difference, the output of `tar tvf` for both files is logged. -* Other files: Output of `diff` of the local and staged files. - Note: GPG signatures are verified **only** against the project's `KEYS` file. If the script finds no issues, the temporary verification directory is deleted by default. You can keep it around by using the `--keep-temp-dir` (`-k`) option. Remember to delete it manually when you're done. - -# Reproducible builds Review Comment: While it is something that we definitely would like to strive for in the future, we cannot do it today. I don't see a point in listing things on the website that do not work today nor have a known, tangible timeline for happening. -- 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]
