Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.3 Candidate 1

+1 (binding) Validated source artifacts - checked sha512 checksum - checked signature Validated binaries - ran sample app -Lari On Fri, 16 Feb 2024 at 17:42, Chris Bono wrote: > > Following PIP-205: Reactive Java client for Apache Pulsar ( > https://github.com/apache/pulsar/issues/17335), this

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.3 Candidate 1

+1 (non-binding) Validated source artifacts - checked sha512 checksum - checked signature Validated binaries - ran sample app On 2024/02/16 15:42:35 Chris Bono wrote: > Following PIP-205: Reactive Java client for Apache Pulsar ( > https://github.com/apache/pulsar/issues/17335), this is release

[VOTE] Reactive Java client for Apache Pulsar 0.5.3 Candidate 1

Following PIP-205: Reactive Java client for Apache Pulsar ( https://github.com/apache/pulsar/issues/17335), this is release candidate 1 for the Reactive Java client for Apache Pulsar, version 0.5.3. *** Please download, test and vote on this release. This vote will stay open for at least 72 hours

Pulsar Version upgrade guidelines

There have been a few discussions in the past on the slack channel and I recently also started a similar thread [0] regarding if we can skip certain releases while upgrading towards pulsar 3.0 and beyond. Starting this dev mailing list discussion to get some more input. As per official release pol