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 this upgrade in 4.0 seems like a good move to me.
Nicolò Il giorno mer 17 apr 2024 alle ore 17:32 Zixuan Liu <zix...@apache.org> ha scritto: > > > do we first release 3.3.x asap and then tackle this upgrade for Pulsar > 3.4.x > +1 > > Lari Hotari <lhot...@apache.org> 于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 although it is not officially supported anymore. This > > might change soon. That's why we need to start preparing to upgrade to > > Jetty 12. > > > > It is recommended to skip Jetty 10 and Jetty 11 since they are also end of > > support. > > More details about this recommendation is in this Jetty GitHub issue > > message by the Jetty maintainer: > > https://github.com/jetty/jetty.project/issues/11644#issuecomment-2048516903 > > . > > > > Could we target Jetty 12 upgrade for the master branch so that it gets > > included in Pulsar 3.3.x ? > > Or, do we first release 3.3.x asap and then tackle this upgrade for Pulsar > > 3.4.x? > > > > -Lari > >
