+1 Thanks, Zike Yang
On Mon, Nov 28, 2022 at 6:46 PM Xiangying Meng <xiangy...@apache.org> wrote: > > Hi, Enrico > Thanks for your suggestion. > I will only cherry-pick patches that have been on the master branch for a > while. > Thanks, > Xiangying > > > On Mon, Nov 28, 2022 at 6:20 PM Enrico Olivelli <eolive...@gmail.com> wrote: > > > Il Lun 28 Nov 2022, 10:50 PengHui Li <codelipeng...@gmail.com> ha scritto: > > > > > +1 > > > > > > Thanks, > > > Penghui > > > > > > > On Nov 28, 2022, at 17:48, Xiangying Meng <xiangy...@apache.org> > > wrote: > > > > > > > > Hello, Pulsar community: > > > > > > > > I'd like to propose releasing Apache Pulsar 2.10.3. It's been about one > > > > month since 2.10.2 was released. > > > > > > > > There are 93 PRs [0] needed to cherry-pick in branch-2.10. I will > > > > cherry-pick these PRs for branch-2.10. Exclude some PRs that merge > > > directly > > > > into branch-2.10. > > > > > > > > There are 32 PRs [1] opened. I'll follow up on each of those PRs to see > > > if > > > > they will be completed soon or will need to be pushed to 2.10.3 > > > > > > > > > 2.10.x is a really stable and mature branch. > > If you want to cut a release soon I think that it is better to not include > > new last minute things. > > Let's cherry pick only patches that have been on the master branch for a > > while. > > > > Introducing instability is a risk that I don't think we want to take. > > > > > > By the way I am +1 for cutting a release > > > > Thanks > > Enrico > > > > > > > > > > > If you have any important fixes or any questions, please reply to this > > > > email, and we will evaluate whether to include them in 2.10.3 > > > > > > > > Thanks, > > > > Xiangying > > > > [0] - > > > > > > > > > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.10.3+-label%3Acherry-picked%2Fbranch-2.10+is%3Amerged+ > > > > [1] - > > > > > > > > > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.10.3+-label%3Acherry-picked%2Fbranch-2.10+is%3Aopen+ > > > > > > > >
