Unfortunately, I have to vote -1 on this. Release candidates, if they are to become actual releases, must be binary identical once voted upon and released. This archive contains numerous references to “RC1” including the top-level directory within the archive itself. All of these will at a minimum change the sha512sum of the archive, and logically result in different contents.
However, I don’t see an issue with the source code, so simply re-releasing the tarball without ‘-RC1’ in the version will probably work. Craig > On Aug 31, 2022, at 5:03 AM, Peter Bacsko <[email protected]> wrote: > > Hello everyone, > > I’d like to call a vote for releasing Apache YuniKorn 1.1.0 RC1. > > The release artifacts have been uploaded here: > https://dist.apache.org/repos/dist/dev/yunikorn/1.1.0-RC1/ > > My public key is located here: > https://downloads.apache.org/yunikorn/KEYS > > JIRA issues that have been resolved in this release: > https://issues.apache.org/jira/issues/?filter=12352202 > > Git tags for each component are as follows: > > incubator-yunikorn-scheduler-interface: v1.1.0-1 > incubator-yunikorn-core: v1.1.0-1 > incubator-yunikorn-k8shim: v1.1.0-1 > incubator-yunikorn-web: v1.1.0-1 > incubator-yunikorn-release: v1.1.0-1 > > One the release is voted on and approved, all repos will be tagged 1.1.0 > for consistency. > > Please review and vote. The vote will be open for at least 72 hours and > closes on Saturday, September 3 2022, 12pm CEST. > > [ ] +1 Approve > [ ] +0 No opinion > [ ] -1 Disapprove (and the reason why) > > > Thank you, > Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
