You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Haiting Jiang <ji...@apache.org> on 2022/07/26 11:19:49 UTC
[DISCUSS] Restart Release Pulsar 2.7.5
Hello Pulsar Community,
Previously in early February, we had a discussion about 2.7.5 release in [1].
But unfortunately, there seems to be a test regression in Candidate 1 and the
release process is blocked since [2]. I would like to pick up the work and
volunteer to be the release manager.
Here [3] you can find the list of 52 commits to branch-2.7 since the 2.7.4
release. The commits number is 41 more than RC1. Since 2.7.5 should be the
last release of branch 2.7, I plan to include all existing commit this time.
After that branch 2.7 should not accept any more commits.
There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked
[4]. I'll follow up on these PRs and solve the test regression issue and start
preparing branch-2.7 RC2 for the release.
BR,
Haiting Jiang
[1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
[2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
[3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
[4] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by PengHui Li <co...@gmail.com>.
+1
Penghui
On Jul 27, 2022, 11:00 +0800, Zixuan Liu <no...@gmail.com>, wrote:
> +1
>
> Thanks,
> Zixuan
>
> Zike Yang <zi...@apache.org> 于2022年7月26日周二 22:24写道：
>
> > +1
> >
> > Thanks
> > Zike Yang
> >
> > On Tue, Jul 26, 2022 at 7:46 PM Hang Chen <ch...@apache.org> wrote:
> > >
> > > +1
> > >
> > > Thanks,
> > > Hang
> > >
> > > Enrico Olivelli <eo...@gmail.com> 于2022年7月26日周二 19:21写道：
> > > >
> > > > +1
> > > >
> > > > thank you
> > > >
> > > > Enrico
> > > >
> > > > Il giorno mar 26 lug 2022 alle ore 13:19 Haiting Jiang
> > > > <ji...@apache.org> ha scritto:
> > > > >
> > > > > Hello Pulsar Community,
> > > > >
> > > > > Previously in early February, we had a discussion about 2.7.5
> > release in [1].
> > > > > But unfortunately, there seems to be a test regression in Candidate
> > 1 and the
> > > > > release process is blocked since [2]. I would like to pick up the
> > work and
> > > > > volunteer to be the release manager.
> > > > >
> > > > > Here [3] you can find the list of 52 commits to branch-2.7 since the
> > 2.7.4
> > > > > release. The commits number is 41 more than RC1. Since 2.7.5 should
> > be the
> > > > > last release of branch 2.7, I plan to include all existing commit
> > this time.
> > > > > After that branch 2.7 should not accept any more commits.
> > > > >
> > > > > There are 4 closed PRs targeting 2.7.5 that have not yet been
> > cherry-picked
> > > > > [4]. I'll follow up on these PRs and solve the test regression issue
> > and start
> > > > > preparing branch-2.7 RC2 for the release.
> > > > >
> > > > > BR,
> > > > > Haiting Jiang
> > > > >
> > > > > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
> > > > > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
> > > > > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
> > > > > [4]
> > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
> >
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by Zixuan Liu <no...@gmail.com>.
+1
Thanks,
Zixuan
Zike Yang <zi...@apache.org> 于2022年7月26日周二 22:24写道：
> +1
>
> Thanks
> Zike Yang
>
> On Tue, Jul 26, 2022 at 7:46 PM Hang Chen <ch...@apache.org> wrote:
> >
> > +1
> >
> > Thanks,
> > Hang
> >
> > Enrico Olivelli <eo...@gmail.com> 于2022年7月26日周二 19:21写道：
> > >
> > > +1
> > >
> > > thank you
> > >
> > > Enrico
> > >
> > > Il giorno mar 26 lug 2022 alle ore 13:19 Haiting Jiang
> > > <ji...@apache.org> ha scritto:
> > > >
> > > > Hello Pulsar Community,
> > > >
> > > > Previously in early February, we had a discussion about 2.7.5
> release in [1].
> > > > But unfortunately, there seems to be a test regression in Candidate
> 1 and the
> > > > release process is blocked since [2]. I would like to pick up the
> work and
> > > > volunteer to be the release manager.
> > > >
> > > > Here [3] you can find the list of 52 commits to branch-2.7 since the
> 2.7.4
> > > > release. The commits number is 41 more than RC1. Since 2.7.5 should
> be the
> > > > last release of branch 2.7, I plan to include all existing commit
> this time.
> > > > After that branch 2.7 should not accept any more commits.
> > > >
> > > > There are 4 closed PRs targeting 2.7.5 that have not yet been
> cherry-picked
> > > > [4]. I'll follow up on these PRs and solve the test regression issue
> and start
> > > > preparing branch-2.7 RC2 for the release.
> > > >
> > > > BR,
> > > > Haiting Jiang
> > > >
> > > > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
> > > > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
> > > > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
> > > > [4]
> https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
>
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by Zike Yang <zi...@apache.org>.
+1
Thanks
Zike Yang
On Tue, Jul 26, 2022 at 7:46 PM Hang Chen <ch...@apache.org> wrote:
>
> +1
>
> Thanks,
> Hang
>
> Enrico Olivelli <eo...@gmail.com> 于2022年7月26日周二 19:21写道：
> >
> > +1
> >
> > thank you
> >
> > Enrico
> >
> > Il giorno mar 26 lug 2022 alle ore 13:19 Haiting Jiang
> > <ji...@apache.org> ha scritto:
> > >
> > > Hello Pulsar Community,
> > >
> > > Previously in early February, we had a discussion about 2.7.5 release in [1].
> > > But unfortunately, there seems to be a test regression in Candidate 1 and the
> > > release process is blocked since [2]. I would like to pick up the work and
> > > volunteer to be the release manager.
> > >
> > > Here [3] you can find the list of 52 commits to branch-2.7 since the 2.7.4
> > > release. The commits number is 41 more than RC1. Since 2.7.5 should be the
> > > last release of branch 2.7, I plan to include all existing commit this time.
> > > After that branch 2.7 should not accept any more commits.
> > >
> > > There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked
> > > [4]. I'll follow up on these PRs and solve the test regression issue and start
> > > preparing branch-2.7 RC2 for the release.
> > >
> > > BR,
> > > Haiting Jiang
> > >
> > > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
> > > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
> > > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
> > > [4] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by Hang Chen <ch...@apache.org>.
+1
Thanks,
Hang
Enrico Olivelli <eo...@gmail.com> 于2022年7月26日周二 19:21写道：
>
> +1
>
> thank you
>
> Enrico
>
> Il giorno mar 26 lug 2022 alle ore 13:19 Haiting Jiang
> <ji...@apache.org> ha scritto:
> >
> > Hello Pulsar Community,
> >
> > Previously in early February, we had a discussion about 2.7.5 release in [1].
> > But unfortunately, there seems to be a test regression in Candidate 1 and the
> > release process is blocked since [2]. I would like to pick up the work and
> > volunteer to be the release manager.
> >
> > Here [3] you can find the list of 52 commits to branch-2.7 since the 2.7.4
> > release. The commits number is 41 more than RC1. Since 2.7.5 should be the
> > last release of branch 2.7, I plan to include all existing commit this time.
> > After that branch 2.7 should not accept any more commits.
> >
> > There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked
> > [4]. I'll follow up on these PRs and solve the test regression issue and start
> > preparing branch-2.7 RC2 for the release.
> >
> > BR,
> > Haiting Jiang
> >
> > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
> > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
> > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
> > [4] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by Enrico Olivelli <eo...@gmail.com>.
+1
thank you
Enrico
Il giorno mar 26 lug 2022 alle ore 13:19 Haiting Jiang
<ji...@apache.org> ha scritto:
>
> Hello Pulsar Community,
>
> Previously in early February, we had a discussion about 2.7.5 release in [1].
> But unfortunately, there seems to be a test regression in Candidate 1 and the
> release process is blocked since [2]. I would like to pick up the work and
> volunteer to be the release manager.
>
> Here [3] you can find the list of 52 commits to branch-2.7 since the 2.7.4
> release. The commits number is 41 more than RC1. Since 2.7.5 should be the
> last release of branch 2.7, I plan to include all existing commit this time.
> After that branch 2.7 should not accept any more commits.
>
> There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked
> [4]. I'll follow up on these PRs and solve the test regression issue and start
> preparing branch-2.7 RC2 for the release.
>
> BR,
> Haiting Jiang
>
> [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
> [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
> [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
> [4] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by Haiting Jiang <ji...@gmail.com>.
Hi all,
I have cherry-picked all necessary commits to branch-2.7, see [1]
Notice, there are some PRs dropped from 2.7.x for some reason.
- Upgrade Netty to 4.1.76.Final, Netty Tcnative, grpc and protobuf #15212,
Conflict with Bookkeeper 4.12.x
- Upgrade Netty to 4.1.77.Final and netty-tcnative to 2.0.52.Final #15646.
Same as above
- [Build] Use grpc-bom to align grpc library versions #15234. This depends
on #15212
- [improve][broker]Expose Netty threads num config to bookkeeper.conf
#15000. Not strictly bug fix, and not able to catch the release time.
- Prometheus metric support label #14564. Stale for months.
- Expose BookKeeper client thread pool metrics #14348. Stale for months.
And I have deleted the label `release/2.7.6`.
If any of you want some PRs to be included in 2.7.5, please reply in the
email.
I will begin the release next Wednesday (UTC+8 Time Zone).
[1]
https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7+-base%3Abranch-2.7
Thanks,
Haiting
On Fri, Jul 29, 2022 at 3:10 PM Haiting Jiang <ji...@gmail.com>
wrote:
> Hi Penghui,
>
> > I see #11992 was closed, and we’d better onboard #16326 in 2.7.5
>
> Sure, I will help Zixuan on this.
>
> > For the merged PRs with label "release/2.7.6"
> > We should change them to "release/2.7.5"
>
> I am updating the label after it's cherry-picked to branch 2.7
> There won't be any PR labeled "release/2.7.6" after this release.
>
> Thanks,
> Haiting
>
> On Fri, Jul 29, 2022 at 1:12 PM PengHui Li <co...@gmail.com>
> wrote:
>
>> Hi haiting,
>>
>> I see #11992 was closed, and we’d better onboard #16326 in 2.7.5
>>
>> For the merged PRs with label "release/2.7.6"
>> We should change them to "release/2.7.5"
>>
>> Penghui
>> Thanks,
>> Penghui
>>
>> On Jul 27, 2022, 19:13 +0800, Haiting Jiang <ji...@apache.org>,
>> wrote:
>> > Hi all,
>> >
>> > > There are 4 closed PRs targeting 2.7.5 that have not yet been
>> cherry-picked
>> > > [4]. I'll follow up on these PRs and solve the test regression issue
>> and start
>> > > preparing branch-2.7 RC2 for the release.
>> >
>> > After dealing with these 4 closed PRs, I find that
>> > - There are 2 open PRs (#11992 and #16326) targeting branch-2.7 but not
>> > labeled with "release/2.7.5".
>> > - There are 4 open PRs and 17 merged PRs labeled "release/2.7.6" but
>> > have not yet been cherry-picked. See [1].
>> >
>> > As we plan to set 2.7.5 as the final release of branch 2.7, all these
>> PRs
>> > will be included in this release, and labeled "release/2.7.5".
>> >
>> > Please let me know if I miss other PRs.
>> >
>> > BR,
>> > Haiting
>> >
>> > [1]
>> https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.6+-label%3Acherry-picked%2Fbranch-2.7+
>> >
>> > On 2022/07/26 11:19:49 Haiting Jiang wrote:
>> > > Hello Pulsar Community,
>> > >
>> > > Previously in early February, we had a discussion about 2.7.5 release
>> in [1].
>> > > But unfortunately, there seems to be a test regression in Candidate 1
>> and the
>> > > release process is blocked since [2]. I would like to pick up the
>> work and
>> > > volunteer to be the release manager.
>> > >
>> > > Here [3] you can find the list of 52 commits to branch-2.7 since the
>> 2.7.4
>> > > release. The commits number is 41 more than RC1. Since 2.7.5 should
>> be the
>> > > last release of branch 2.7, I plan to include all existing commit
>> this time.
>> > > After that branch 2.7 should not accept any more commits.
>> > >
>> > > There are 4 closed PRs targeting 2.7.5 that have not yet been
>> cherry-picked
>> > > [4]. I'll follow up on these PRs and solve the test regression issue
>> and start
>> > > preparing branch-2.7 RC2 for the release.
>> > >
>> > > BR,
>> > > Haiting Jiang
>> > >
>> > > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
>> > > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
>> > > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
>> > > [4]
>> https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
>> > >
>>
>
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by Haiting Jiang <ji...@gmail.com>.
Hi Penghui,
> I see #11992 was closed, and we’d better onboard #16326 in 2.7.5
Sure, I will help Zixuan on this.
> For the merged PRs with label "release/2.7.6"
> We should change them to "release/2.7.5"
I am updating the label after it's cherry-picked to branch 2.7
There won't be any PR labeled "release/2.7.6" after this release.
Thanks,
Haiting
On Fri, Jul 29, 2022 at 1:12 PM PengHui Li <co...@gmail.com> wrote:
> Hi haiting,
>
> I see #11992 was closed, and we’d better onboard #16326 in 2.7.5
>
> For the merged PRs with label "release/2.7.6"
> We should change them to "release/2.7.5"
>
> Penghui
> Thanks,
> Penghui
>
> On Jul 27, 2022, 19:13 +0800, Haiting Jiang <ji...@apache.org>,
> wrote:
> > Hi all,
> >
> > > There are 4 closed PRs targeting 2.7.5 that have not yet been
> cherry-picked
> > > [4]. I'll follow up on these PRs and solve the test regression issue
> and start
> > > preparing branch-2.7 RC2 for the release.
> >
> > After dealing with these 4 closed PRs, I find that
> > - There are 2 open PRs (#11992 and #16326) targeting branch-2.7 but not
> > labeled with "release/2.7.5".
> > - There are 4 open PRs and 17 merged PRs labeled "release/2.7.6" but
> > have not yet been cherry-picked. See [1].
> >
> > As we plan to set 2.7.5 as the final release of branch 2.7, all these PRs
> > will be included in this release, and labeled "release/2.7.5".
> >
> > Please let me know if I miss other PRs.
> >
> > BR,
> > Haiting
> >
> > [1]
> https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.6+-label%3Acherry-picked%2Fbranch-2.7+
> >
> > On 2022/07/26 11:19:49 Haiting Jiang wrote:
> > > Hello Pulsar Community,
> > >
> > > Previously in early February, we had a discussion about 2.7.5 release
> in [1].
> > > But unfortunately, there seems to be a test regression in Candidate 1
> and the
> > > release process is blocked since [2]. I would like to pick up the work
> and
> > > volunteer to be the release manager.
> > >
> > > Here [3] you can find the list of 52 commits to branch-2.7 since the
> 2.7.4
> > > release. The commits number is 41 more than RC1. Since 2.7.5 should be
> the
> > > last release of branch 2.7, I plan to include all existing commit this
> time.
> > > After that branch 2.7 should not accept any more commits.
> > >
> > > There are 4 closed PRs targeting 2.7.5 that have not yet been
> cherry-picked
> > > [4]. I'll follow up on these PRs and solve the test regression issue
> and start
> > > preparing branch-2.7 RC2 for the release.
> > >
> > > BR,
> > > Haiting Jiang
> > >
> > > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
> > > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
> > > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
> > > [4]
> https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
> > >
>
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by PengHui Li <co...@gmail.com>.
Hi haiting,
I see #11992 was closed, and we’d better onboard #16326 in 2.7.5
For the merged PRs with label "release/2.7.6"
We should change them to "release/2.7.5"
Penghui
Thanks,
Penghui
On Jul 27, 2022, 19:13 +0800, Haiting Jiang <ji...@apache.org>, wrote:
> Hi all,
>
> > There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked
> > [4]. I'll follow up on these PRs and solve the test regression issue and start
> > preparing branch-2.7 RC2 for the release.
>
> After dealing with these 4 closed PRs, I find that
> - There are 2 open PRs (#11992 and #16326) targeting branch-2.7 but not
> labeled with "release/2.7.5".
> - There are 4 open PRs and 17 merged PRs labeled "release/2.7.6" but
> have not yet been cherry-picked. See [1].
>
> As we plan to set 2.7.5 as the final release of branch 2.7, all these PRs
> will be included in this release, and labeled "release/2.7.5".
>
> Please let me know if I miss other PRs.
>
> BR,
> Haiting
>
> [1] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.6+-label%3Acherry-picked%2Fbranch-2.7+
>
> On 2022/07/26 11:19:49 Haiting Jiang wrote:
> > Hello Pulsar Community,
> >
> > Previously in early February, we had a discussion about 2.7.5 release in [1].
> > But unfortunately, there seems to be a test regression in Candidate 1 and the
> > release process is blocked since [2]. I would like to pick up the work and
> > volunteer to be the release manager.
> >
> > Here [3] you can find the list of 52 commits to branch-2.7 since the 2.7.4
> > release. The commits number is 41 more than RC1. Since 2.7.5 should be the
> > last release of branch 2.7, I plan to include all existing commit this time.
> > After that branch 2.7 should not accept any more commits.
> >
> > There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked
> > [4]. I'll follow up on these PRs and solve the test regression issue and start
> > preparing branch-2.7 RC2 for the release.
> >
> > BR,
> > Haiting Jiang
> >
> > [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
> > [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
> > [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
> > [4] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
> >
Re: [DISCUSS] Restart Release Pulsar 2.7.5
Posted by Haiting Jiang <ji...@apache.org>.
Hi all,
> There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked
> [4]. I'll follow up on these PRs and solve the test regression issue and start
> preparing branch-2.7 RC2 for the release.
After dealing with these 4 closed PRs, I find that
- There are 2 open PRs (#11992 and #16326) targeting branch-2.7 but not
labeled with "release/2.7.5".
- There are 4 open PRs and 17 merged PRs labeled "release/2.7.6" but
have not yet been cherry-picked. See [1].
As we plan to set 2.7.5 as the final release of branch 2.7, all these PRs
will be included in this release, and labeled "release/2.7.5".
Please let me know if I miss other PRs.
BR,
Haiting
[1] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.6+-label%3Acherry-picked%2Fbranch-2.7+
On 2022/07/26 11:19:49 Haiting Jiang wrote:
> Hello Pulsar Community,
>
> Previously in early February, we had a discussion about 2.7.5 release in [1].
> But unfortunately, there seems to be a test regression in Candidate 1 and the
> release process is blocked since [2]. I would like to pick up the work and
> volunteer to be the release manager.
>
> Here [3] you can find the list of 52 commits to branch-2.7 since the 2.7.4
> release. The commits number is 41 more than RC1. Since 2.7.5 should be the
> last release of branch 2.7, I plan to include all existing commit this time.
> After that branch 2.7 should not accept any more commits.
>
> There are 4 closed PRs targeting 2.7.5 that have not yet been cherry-picked
> [4]. I'll follow up on these PRs and solve the test regression issue and start
> preparing branch-2.7 RC2 for the release.
>
> BR,
> Haiting Jiang
>
> [1] https://lists.apache.org/thread/wxl5z67nnzv05r5vldjq3c6sm7fxnrcc
> [2] https://lists.apache.org/thread/yvrmwldtzbo9lbs0jqjfj31lxtd792jq
> [3] https://github.com/apache/pulsar/compare/v2.7.4...branch-2.7
> [4] https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.7.5+-label%3Acherry-picked%2Fbranch-2.7
>