Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-22 Thread Michael Marshall
ms > - Check the license headers > - build sources > - Validate Pub/Sub and Java Functions > - Validate Stateful Functions > > Regards, > Hiroyuki > > From: Michael Marshall > Sent: Wednesday, February 16, 2022 13:34 > To: Dev

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-17 Thread Hiroyuki Sakai
: [VOTE] Pulsar Release 2.8.3 Candidate 2 This is the second release candidate for Apache Pulsar, version 2.8.3. It fixes the following issues: https://github.com/apache/pulsar/compare/v2.8.2...v2.8.3-candidate-2 *** Please download, test and vote on this release. This vote will stay open for at least

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-17 Thread Nicolò Boschi
+1 (non binding) Checks: - Checksum and signatures - Apache Rat check passes - Compile from source w JDK11 - Build docker image from source - Run Pulsar standalone and produce-consume from CLI - Deployed a cluster to a k8s env and tested simple functions (k8s mode) and the elastic sink usin

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-17 Thread Ran Gao
+1 - Check src build - Check run standalone mode by binary package - Check Basic publish and consume partitioned topic - Check Pulsar SQL query bytes data On 2022/02/16 04:34:55 Michael Marshall wrote: > This is the second release candidate for Apache Pulsar, version 2.8.3. > > It fixes the foll

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-16 Thread Michael Marshall
Thanks for pointing that out, Penghui. I can confirm that my KEY is not signed. While it's not the same as in person verification, I'll note that since becoming a committer I have signed all of my git commits with the same gpg key used to sign these release artifacts. At the very least, we can be

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-16 Thread PengHui Li
Thanks for the explanation Dave. Best, Penghui On Thu, Feb 17, 2022 at 10:37 AM Dave Fisher wrote: > While it’s preferred that KEYS are signed it’s not required. The last > Apache key signing party was at Apachecon Las Vegas in 2019. Here’s looking > forward to the next one. Bring your governme

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-16 Thread Dave Fisher
While it’s preferred that KEYS are signed it’s not required. The last Apache key signing party was at Apachecon Las Vegas in 2019. Here’s looking forward to the next one. Bring your government ids. Regards, Dave Sent from my iPhone > On Feb 16, 2022, at 6:11 PM, PengHui Li wrote: > > Hi Mi

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-16 Thread PengHui Li
Hi Michael, Please check your key ``` gpg: assuming signed data in 'apache-pulsar-2.8.3-bin.tar.gz' gpg: Signature made Wed Feb 16 04:49:42 2022 CST gpg:using RSA key BD4291E509D771B79E7BD1F5C5724B3F5588C4EB gpg: Good signature from "Michael Marshall " [unknown] gpg: WARNING: This

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-16 Thread PengHui Li
+1 (binding) - Checked the signature - Start the standalone - Publish and consume messages - Check the Cassandra connector - Check the stateful function Thanks for the great work, Penghui On Wed, Feb 16, 2022 at 12:35 PM Michael Marshall wrote: > This is the second release candidate for Apache

[VOTE] Pulsar Release 2.8.3 Candidate 2

2022-02-15 Thread Michael Marshall
This is the second release candidate for Apache Pulsar, version 2.8.3. It fixes the following issues: https://github.com/apache/pulsar/compare/v2.8.2...v2.8.3-candidate-2 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are votin