171 commits? Why?
This is too much in my opinion for a point release. I am pretty sure that we don't need all that changes. Every change we cherry pick has a good chance to break the stability Enrico Il Mer 5 Gen 2022, 16:30 mattison chao <mattisonc...@gmail.com> ha scritto: > +1 > > regards, > Mattisonchao > > On Wed, 5 Jan 2022 at 23:04, Lan Liang <liangyuanpen...@163.com> wrote: > > > +1,Thanks for your work. > > > > > > > > > > > > > > Best Regards, > > Lan Liang > > On 1/5/2022 23:01，Hang Chen<chenh...@apache.org> wrote： > > +1 > > > > Best, > > Hang > > > > 陳智弘 <thomasec...@gmail.com> 于2022年1月5日周三 21:30写道： > > > > +1 > > > > Lari Hotari <l...@hotari.net> 於 2022年1月5日 週三 20:56 寫道： > > > > +1 > > > > On Wed, Jan 5, 2022 at 11:23 AM Ran Gao <r...@apache.org> wrote: > > > > Hello, Pulsar community: > > > > I'd like to propose that we release Apache Pulsar 2.9.2. > > > > Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer > > to [0]), they contain the log4j security patch and many important fixes. > > > > I am happy to volunteer to be the release manager. > > > > I see 4 merged PRs are labeled release/2.9.2 but not cherry-pick to > > branch-2.9, I'll cherry-pick them, and there are also 20 open PRs are > > labeled release/2.9.2, I'll follow them to make sure important fix could > > be > > merged in 2.9.2. > > > > > > Best, > > Ran Gao > > > > > > [0] https://github.com/apache/pulsar/compare/v2.9.1...branch-2.9 > > > > > > >
