+1

Just a reminder, this one [0] might be a blocker for the subsequent patch
releases since it has introduced a new rule of the rule_name.
Here [1] is the discussion under the private mailing thread.
IMO, we should revert this change first before starting the release.

And I also hope more PMCs can follow this topic [1], providing your
thoughts.

Thanks,
Penghui

[0]
https://github.com/apache/pulsar/commit/c7eabc9391361508fc222469479bfea83d5d0c64
[1] https://lists.apache.org/thread/q1k1krfjr8njdf8t3sy1ht4vg67s4x71

On Wed, Mar 15, 2023 at 12:25 PM Haiting Jiang <jianghait...@gmail.com>
wrote:

> +1
>
> Thanks,
> Haiting
>
> On Wed, Mar 15, 2023 at 11:46 AM Yubiao Feng
> <yubiao.f...@streamnative.io.invalid> wrote:
> >
> > +1
> >
> > Thanks
> > Yubiao Feng
> >
> > On Wed, Mar 15, 2023 at 11:43 AM guo jiwei <techno...@apache.org> wrote:
> >
> > > Hello, Pulsar community:
> > >
> > > I'd like to propose releasing Apache Pulsar 2.11.1. It's been about
> > > two months since 2.11.0 was released.
> > >
> > > There are about over 200 PRS [0] cherry-picked to branch-2.11 since
> > > the last release.
> > >
> > > If you have any important fixes or any questions, please reply to this
> > > email and we will evaluate whether to include them in 2.11.1
> > >
> > >
> > > [0]
> > >
> https://github.com/apache/pulsar/pulls?page=9&q=is%3Apr+label%3Arelease%2F2.11.1+-label%3Acherry-picked%2Fbranch-2.11.1+is%3Amerged
> > >
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
>

Reply via email to