[VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK

https://github.com/apache/pulsar/pull/24364 --- # PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK # Context Currently, Pulsar requires Java 17 for the server side components and Java 8 for the client SDK and the client admin SDK. For the server side components the change was

Re: [DISCUSS] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK

Thanks for the comments. I'll start a vote thread. -- Matteo Merli On Thu, Jun 5, 2025 at 1:06 AM xiangying meng wrote: > +1 > > Xiangying Meng > > On Thu, Jun 5, 2025 at 4:04 PM Nicolò Boschi wrote: > > > > +1 > > > > Nicolò Boschi > > > > Il giorno gio 5 giu 2025 alle ore 09:02 Haiting Jian

Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK

+1 (binding) -Lari On 2025/06/19 19:35:53 Matteo Merli wrote: > https://github.com/apache/pulsar/pull/24364 > > --- > > # PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK > > # Context > > Currently, Pulsar requires Java 17 for the server side components and Java > 8 for the

ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3.

Hi all, ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3. Example build failures: pulsar-ci.yaml for branch-3.0 (ExtensibleLoadManagerImplTest is in broker group 1 in branch-3.0): https://github.com/apache/pulsar/actions/workflows/pulsar-ci.yaml?query=branch%3Abranch-3.0 In ma