Hi all, While I have successfully generated the release materials for the RC0 of Polaris v1.4.0, I am facing a few issues when running the `verify-release.sh` script.
1. A file descriptor resource leak causes the script to deadlock during the Signature and Checksum verification of the Maven repo. I've opened #4024 [1] to suggest a fix to this issue. 2. Getting errors on all artifacts: "Locally built and staged Maven repository artifact XXX differ". I've verified I'm using the same Java version to compile locally. So far, my hunch is that some asymmetric differences exist between how the code is assembled in the GitHub workflow and how we assemble it locally, perhaps relating to the "-PjarWithGitInfo" and "-Prelease" flags. I really have no clue why this may be happening... 3. The verify-release script is complaining that the LICENSE and NOTICE files are not found in "META-INF/" for the Spark connector jars. My understanding is that #3912 [2] may be causing this. I'm not sure if there was a decision that LICENSE/NOTICE files do not need to be placed there? But if not, is there a bug in #3912 that needs fixing? Here is a link to the GitHub Actions run that produces the materials I was attempting to verify: https://github.com/apache/polaris/actions/runs/23222125467 [1] https://github.com/apache/polaris/pull/4024 [2] https://github.com/apache/polaris/pull/3912 Best, Adnan Hemani
