You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Xiangying Meng <xi...@apache.org> on 2022/11/28 09:48:31 UTC
[DISCUSS] Release Pulsar 2.10.3
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
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+
Re: [DISCUSS] Release Pulsar 2.10.3
Posted by Xiangying Meng <xi...@apache.org>.
Hi Lari,
I open a PR <https://github.com/apache/pulsar/pull/18980> to cherry-pick
this PR. Could you please take a look when you have time?
Sincerely,
Xiangying
On Fri, Dec 16, 2022 at 4:21 PM Lari Hotari <lh...@apache.org> wrote:
> There's at least one very important PR that wasn't marked for 2.10.3 .
> For performance, addressing https://github.com/apache/pulsar/pull/17273
> is crucial. The broker cache is currently partially broken in all released
> versions of Pulsar until that fix is out.
>
> I tagged it as 2.10.3 now. I tried to cherry-pick it, but it has a lot of
> merge conflicts. The main reason for the merge conflict seems to be that
> fixes to ManagedLedgerImpl file didn't get cherry-picked in the same order
> as the fixes were made. Are there any volunteers to do the cherry-picking
> for 17273?
>
> -Lari
>
>
> On 2022/11/28 09:48:31 Xiangying Meng 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
> >
> > 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+
> >
>
Re: [DISCUSS] Release Pulsar 2.10.3
Posted by Lari Hotari <lh...@apache.org>.
There's at least one very important PR that wasn't marked for 2.10.3 .
For performance, addressing https://github.com/apache/pulsar/pull/17273 is crucial. The broker cache is currently partially broken in all released versions of Pulsar until that fix is out.
I tagged it as 2.10.3 now. I tried to cherry-pick it, but it has a lot of merge conflicts. The main reason for the merge conflict seems to be that fixes to ManagedLedgerImpl file didn't get cherry-picked in the same order as the fixes were made. Are there any volunteers to do the cherry-picking for 17273?
-Lari
On 2022/11/28 09:48:31 Xiangying Meng 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
>
> 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+
>
Re: [DISCUSS] Release Pulsar 2.10.3
Posted by Haiting Jiang <ji...@gmail.com>.
+1
Thanks for being the RM.
Haigting
On Mon, Nov 28, 2022 at 7:13 PM Zike Yang <zi...@apache.org> wrote:
>
> +1
>
> Thanks,
> Zike Yang
>
> On Mon, Nov 28, 2022 at 6:46 PM Xiangying Meng <xi...@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 <eo...@gmail.com> wrote:
> >
> > > Il Lun 28 Nov 2022, 10:50 PengHui Li <co...@gmail.com> ha scritto:
> > >
> > > > +1
> > > >
> > > > Thanks,
> > > > Penghui
> > > >
> > > > > On Nov 28, 2022, at 17:48, Xiangying Meng <xi...@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+
> > > >
> > > >
> > >
Re: [DISCUSS] Release Pulsar 2.10.3
Posted by Zike Yang <zi...@apache.org>.
+1
Thanks,
Zike Yang
On Mon, Nov 28, 2022 at 6:46 PM Xiangying Meng <xi...@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 <eo...@gmail.com> wrote:
>
> > Il Lun 28 Nov 2022, 10:50 PengHui Li <co...@gmail.com> ha scritto:
> >
> > > +1
> > >
> > > Thanks,
> > > Penghui
> > >
> > > > On Nov 28, 2022, at 17:48, Xiangying Meng <xi...@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+
> > >
> > >
> >
Re: [DISCUSS] Release Pulsar 2.10.3
Posted by Xiangying Meng <xi...@apache.org>.
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 <eo...@gmail.com> wrote:
> Il Lun 28 Nov 2022, 10:50 PengHui Li <co...@gmail.com> ha scritto:
>
> > +1
> >
> > Thanks,
> > Penghui
> >
> > > On Nov 28, 2022, at 17:48, Xiangying Meng <xi...@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+
> >
> >
>
Re: [DISCUSS] Release Pulsar 2.10.3
Posted by Enrico Olivelli <eo...@gmail.com>.
Il Lun 28 Nov 2022, 10:50 PengHui Li <co...@gmail.com> ha scritto:
> +1
>
> Thanks,
> Penghui
>
> > On Nov 28, 2022, at 17:48, Xiangying Meng <xi...@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+
>
>
Re: [DISCUSS] Release Pulsar 2.10.3
Posted by PengHui Li <co...@gmail.com>.
+1
Thanks,
Penghui
> On Nov 28, 2022, at 17:48, Xiangying Meng <xi...@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
>
> 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+