3.3.x +1
The branch-3.2 is the latest branch, and the latest version is 3.2.2, it
contains functionality improvements, bug fixes, and CVE fixes, if we happen to
release a new version based on branch-3.3, why not add this change to it?
Best
- Ran Gao
On 2024/04/17 17:30:27 Lari Hotari wrote:
>
The Apache Pulsar team is proud to announce Apache Pulsar Node.js
client version 1.11.0.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor mana
I'd not like to do this change for 3.3.x, but the fact is that there's no
support for Jetty 9.4.x .
A new CVE in Jetty 9.4.x could cause a problem to us if the support policy is
actually followed in Jetty and users are forced to upgrade to get the fix. We
just have to tolerate this risk, I gues
I personally agree with NOT including it in 3.3.x
Following the release policy, it should be time to start preparing the
3.3.x branch soon.
Also I wonder if the release line after 3.3.x will be 4.0, given that
3.0 has been released almost 1y ago and the LTS should be cut every 18
months.
Having th
> do we first release 3.3.x asap and then tackle this upgrade for Pulsar
3.4.x
+1
Lari Hotari 于2024年4月17日周三 21:57写道：
> Hi,
>
> Pulsar Broker and Pulsar Proxy use Jetty 9.4.x. Jetty 9.4.x has reached
> end-of-line already in June 2022. Jetty 9.4.x has been receiving security
> updates until now a
Close this vote with 3 binding +1s
- zike
- baodi
- Masahiro Sakamoto
And 1 non-binding +1:
- Shusuke Tsuda
Thanks,
Baodi Shi
On Apr 17, 2024 at 11:52:47, Zike Yang wrote:
> +1 (binding)
>
> - Verified checksum and signature
> - Built from source on macOS arm64 and run the example
> - Instal
