Hi Akira, Thanks for verification, have a check on my local, the artifacts were signed by the wrong key.
I'm going to cancel this VOTE and create a new one. Thanks to everyone who helped with this VOTE. Thanks, Cheng Pan On Mon, Aug 30, 2021 at 7:16 AM Akira Ajisaka <[email protected]> wrote: > Hi Cheng Pan, > > I couldn't verify the signatures of the release artifacts. > Would you add the key to > https://dist.apache.org/repos/dist/dev/incubator/kyuubi/KEYS or create > another RC with an existing key in the KEYS file? > > % gpg --import KEYS > gpg: key F07E6C29ED4E2E5B: public key "Cheng Pan <[email protected]>" > imported > gpg: key F7051850A0AF904D: public key "Kent Yao (github) > <[email protected]>" imported > gpg: key 04DB933085E7DF72: public key "Fei Wang <[email protected]>" > imported > gpg: Total number processed: 3 > gpg: imported: 3 > % gpg --verify kyuubi-1.3.0-incubating-bin.tgz.asc > gpg: assuming signed data in 'kyuubi-1.3.0-incubating-bin.tgz' > gpg: Signature made Fri Aug 27 15:57:57 2021 JST > gpg: using RSA key F3B17DF6E8929A3871BD5B3F0F420CC405E019E9 > gpg: Can't check signature: No public key > % gpg --verify kyuubi-1.3.0-incubating-source.tgz.asc > gpg: assuming signed data in 'kyuubi-1.3.0-incubating-source.tgz' > gpg: Signature made Fri Aug 27 15:55:09 2021 JST > gpg: using RSA key F3B17DF6E8929A3871BD5B3F0F420CC405E019E9 > gpg: Can't check signature: No public key > > Thanks and regards, > Akira > > On Fri, Aug 27, 2021 at 4:31 PM Cheng Pan <[email protected]> wrote: > > > > Hello Apache Kyuubi PPMC and Community, > > > > Please vote on releasing the following candidate as > > Apache Kyuubi (Incubating) version v1.3.0-incubating. > > > > The VOTE will remain open for at least 72 hours. > > > > [ ] +1 Release this package as Apache Kyuubi v1.3.0-incubating > > [ ] +0 > > [ ] -1 Do not release this package because ... > > > > To learn more about Apache Kyuubi (Incubating), please see > > https://kyuubi.apache.org/ > > > > The tag to be voted on is v1.3.0-incubating-rc5 (commit 1ec75b3): > > https://github.com/apache/incubator-kyuubi/tree/v1.3.0-incubating-rc5 > > > > The release files, including signatures, digests, etc. can be found at: > > > https://dist.apache.org/repos/dist/dev/incubator/kyuubi/v1.3.0-incubating-rc5/ > > > > Signatures used for Kyuubi RCs can be found in this file: > > https://dist.apache.org/repos/dist/dev/incubator/kyuubi/KEYS > > > > The staging repository for this release can be found at: > > https://repository.apache.org/content/repositories/orgapachekyuubi-1005/ > > > > The commit list since the last RC: > > > https://github.com/apache/incubator-kyuubi/compare/v1.3.0-incubating-rc4...v1.3.0-incubating-rc5 > > > > FAQ > > > > ================================= > > How can I help test this release? > > ================================= > > > > If you are a Kyuubi user, you can help us test this release by taking > > an existing Kyuubi workload and running on this release candidate, then > > reporting any regressions. > > > > In the Java/Scala, you can add the staging repository to your projects > > resolvers > > and test with the RC (make sure to clean up the artifact cache > before/after > > so > > you don't end up building with a out of date RC going forward). > > > > ============================================================== > > What should happen to GitHub issues still targeting v1.3.0-incubating? > > ============================================================== > > > > Committers should look at those and triage. Extremely important bug > fixes, > > documentation, and API tweaks that impact compatibility should be worked > on > > immediately. Everything else please retarget to an appropriate release. > > > > ======================= > > But my bug isn't fixed? > > ======================= > > > > In order to make timely releases, we will typically not hold the release > > unless > > the bug in question is a regression from the previous release. That being > > said, > > if there is something which is a regression that has not been correctly > > targeted > > please ping me or a committer to help target the issue. >
