Thanks, I will start the release process soon.
Regards
Jiwei Guo (Tboy)
On Thu, Mar 16, 2023 at 5:48 PM Zike Yang wrote:
>
> +1
>
> Thanks,
> Zike Yang
>
> On Wed, Mar 15, 2023 at 7:45 PM wrote:
> >
> > +1,
> > Thanks for your work!
> >
> > Best,
> > Mattison
> > On Mar 15, 2023, 15:24 +0800,
+1
Thanks,
Zike Yang
On Wed, Mar 15, 2023 at 7:45 PM wrote:
>
> +1,
> Thanks for your work!
>
> Best,
> Mattison
> On Mar 15, 2023, 15:24 +0800, PengHui Li , wrote:
> > +1
> >
> > Just a reminder, this one [0] might be a blocker for the subsequent patch
> > releases since it has introduced a new
+1,
Thanks for your work!
Best,
Mattison
On Mar 15, 2023, 15:24 +0800, PengHui Li , wrote:
> +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 threa
+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 ca
+1
Thanks,
Haiting
On Wed, Mar 15, 2023 at 11:46 AM Yubiao Feng
wrote:
>
> +1
>
> Thanks
> Yubiao Feng
>
> On Wed, Mar 15, 2023 at 11:43 AM guo jiwei 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
+1
Thanks
Yubiao Feng
On Wed, Mar 15, 2023 at 11:43 AM guo jiwei 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 r
