Hi all, Put an update here, we have created branch-2.11[1].
[1] https://github.com/apache/pulsar/tree/branch-2.11 Regards Jiwei Guo (Tboy) On Wed, Jul 27, 2022 at 10:59 AM Zixuan Liu <node...@gmail.com> wrote: > +1 > > Thanks, > Zixuan > > Yunze Xu <y...@streamnative.io.invalid> 于2022年7月26日周二 23:34写道： > > > I opened a PR https://github.com/apache/pulsar/pull/16803 that might be > > the blocker > > of the release of 2.11.0, PTAL. > > > > Thanks, > > Yunze > > > > > > > > > > > 2022年7月22日 18:21，Zixuan Liu <node...@gmail.com> 写道： > > > > > > +1 > > > > > > Thanks, > > > Zixuan > > > > > > Enrico Olivelli <eolive...@gmail.com> 于2022年7月22日周五 18:06写道： > > > > > >> Il giorno ven 22 lug 2022 alle ore 12:05 guo jiwei > > >> <techno...@apache.org> ha scritto: > > >>> > > >>> I will take the release > > >> > > >> Thanks ! > > >> > > >> Enrico > > >> > > >>> > > >>> Regards > > >>> Jiwei Guo (Tboy) > > >>> > > >>> > > >>> On Fri, Jul 22, 2022 at 12:37 AM Nicolò Boschi <boschi1...@gmail.com > > > > >> wrote: > > >>> > > >>>> I understand the need for the Pulsar Summit. > > >>>> > > >>>> In that case I have to step back because I will be offline for the > > >> next few > > >>>> weeks > > >>>> Sorry > > >>>> > > >>>> Nicolò Boschi > > >>>> > > >>>> Il Gio 21 Lug 2022, 06:32 PengHui Li <peng...@apache.org> ha > scritto: > > >>>> > > >>>>> Thanks for volunteering Nicolò. > > >>>>> > > >>>>>> So a plan could be to try to merge the work in progress targeted > > >> for > > >>>> 2.11 > > >>>>> by the mid of August and then start the code freezing as described > > >> in the > > >>>>> PIP. > > >>>>> > > >>>>> So the target release date will be early September. One point is > > >> Pulsar > > >>>>> Summit > > >>>>> San Francisco will start on August 18, 2022. I think maybe we can > > >> start > > >>>> to > > >>>>> test > > >>>>> the master branch for now and continue the in-progress tasks. If we > > >> can > > >>>>> have a > > >>>>> major release before Pulsar Summit, it should be good news to the > > >>>>> Community. > > >>>>> > > >>>>> Thanks. > > >>>>> Penghui > > >>>>> > > >>>>> On Mon, Jul 18, 2022 at 4:06 PM Enrico Olivelli < > eolive...@gmail.com > > >>> > > >>>>> wrote: > > >>>>> > > >>>>>> Nicolò, > > >>>>>> > > >>>>>> Il Lun 18 Lug 2022, 10:00 Nicolò Boschi <boschi1...@gmail.com> ha > > >>>>> scritto: > > >>>>>> > > >>>>>>> Thanks Penghui for the reminder. > > >>>>>>> I'd like to also include PIP: 181 Pulsar shell if the time > > >> permits. > > >>>>>>> > > >>>>>>> I believe that is a good idea to start testing the code freeze > > >>>> proposed > > >>>>>> by > > >>>>>>> PIP-175 (https://github.com/apache/pulsar/issues/15966). Even > > >> if not > > >>>>>>> officially approved, we discussed it many times and agreed to the > > >>>>>>> usefulness of the code freezing. > > >>>>>>> > > >>>>>> > > >>>>>> Great idea! > > >>>>>> > > >>>>>> We should really try it > > >>>>>> > > >>>>>> So a plan could be to try to merge the work in progress targeted > > >> for > > >>>> 2.11 > > >>>>>>> by the mid of August and then start the code freezing as > > >> described in > > >>>>> the > > >>>>>>> PIP. > > >>>>>>> > > >>>>>>> Also, I volunteer for driving the release if nobody else is > > >>>> interested > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> Thanks for volunteering > > >>>>>> > > >>>>>> Enrico > > >>>>>> > > >>>>>> > > >>>>>>> Thanks, > > >>>>>>> Nicolò Boschi > > >>>>>>> > > >>>>>>> > > >>>>>>> Il giorno lun 18 lug 2022 alle ore 06:59 Yunze Xu > > >>>>>>> <y...@streamnative.io.invalid> ha scritto: > > >>>>>>> > > >>>>>>>> In addition to #16202, there is a following PR to support the > > >>>> correct > > >>>>>>>> ACK implementation for chunked messages. It should depend on > > >> #16202 > > >>>>>>>> But I think I can submit an initial PR this week and change the > > >>>> tests > > >>>>>>>> after #16202 is merged. > > >>>>>>>> > > >>>>>>>> Thanks, > > >>>>>>>> Yunze > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>>> 2022年7月18日 11:22，PengHui Li <peng...@apache.org> 写道： > > >>>>>>>>> > > >>>>>>>>> Hi all, > > >>>>>>>>> > > >>>>>>>>> We released 2.10.0 three months ago. And there are many great > > >>>>> changes > > >>>>>>> in > > >>>>>>>>> the master branch, > > >>>>>>>>> including new features and performance improvements. > > >>>>>>>>> > > >>>>>>>>> - PIP 74: apply client memory to consumer > > >>>>>>>>> https://github.com/apache/pulsar/pull/15216 > > >>>>>>>>> - PIP 143: Support split bundles by specified boundaries > > >>>>>>>>> https://github.com/apache/pulsar/pull/13796 > > >>>>>>>>> - PIP 145: regex subscription improvements > > >>>>>>>>> https://github.com/apache/pulsar/pull/16062 > > >>>>>>>>> - PIP 160: transaction performance improvements (still in > > >>>> progress > > >>>>>> and > > >>>>>>>>> merged some PRs) > > >>>>>>>>> - PIP 161: new exclusive producer mode support > > >>>>>>>>> https://github.com/apache/pulsar/pull/15488 > > >>>>>>>>> - PIP 182: Provide new load balance placement strategy > > >>>>> implementation > > >>>>>>> for > > >>>>>>>>> ModularLoadManagerStrategy > > >>>>>> https://github.com/apache/pulsar/pull/16281 > > >>>>>>>>> Add Pulsar Auth support for the Pulsar SQL > > >>>>>>>>> https://github.com/apache/pulsar/pull/15571 > > >>>>>>>>> > > >>>>>>>>> And some features are blocked in the review stage, but they > > >> are > > >>>>>>> powerful > > >>>>>>>>> improvements for Pulsar > > >>>>>>>>> > > >>>>>>>>> PIP 37: Support chunking with Shared subscription > > >>>>>>>>> https://github.com/apache/pulsar/pull/16202 > > >>>>>>>>> PIP-166: Function add MANUAL delivery semantics > > >>>>>>>>> https://github.com/apache/pulsar/pull/16279 > > >>>>>>>>> > > >>>>>>>>> You can find the complete change list in 2.11.0 at > > >>>>>>>>> > > >>>>>>>> > > >>>>>>> > > >>>>>> > > >>>>> > > >>>> > > >> > > > https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A2.11.0+-label%3Arelease%2F2.10.1+-label%3Arelease%2F2.10.2 > > >>>>>>>>> > > >>>>>>>>> And maybe I missed some important in-progress PRs, please > > >> let me > > >>>>> know > > >>>>>>> if > > >>>>>>>> it > > >>>>>>>>> should be a blocker of the 2.11.0 release. > > >>>>>>>>> > > >>>>>>>>> It's a good time to discuss the target time of the 2.11.0 > > >>>> release. > > >>>>>>>>> I think we can leave 2 weeks to complete the in-progress PRs > > >> and > > >>>> 2 > > >>>>>>> weeks > > >>>>>>>> to > > >>>>>>>>> accept bug fixes. > > >>>>>>>>> And target the 2.11.0 release in mid-August. > > >>>>>>>>> > > >>>>>>>>> Please let me know what you think. > > >>>>>>>>> > > >>>>>>>>> Thanks, > > >>>>>>>>> Penghui > > >>>>>>>> > > >>>>>>>> > > >>>>>>> > > >>>>>> > > >>>>> > > >>>> > > >> > > > > >
