Hi all,

I have cherry-picked the fixes to branch-2.10 and will roll out the new RC
tomorrow.
If you find any potential breaking changes, please share the information
there.

Best,
Penghui

On Wed, Feb 23, 2022 at 1:56 PM PengHui Li <peng...@apache.org> wrote:

> Thanks Dave,
>
> Yes, this is also what I want to ask, I have checked all the current
> opened PRs and the current merged PRs
> Looks no other related breaking change fixes. I think we'd better keep the
> VOTE open for 2 days?
>
> Thanks,
> Penghui
>
> On Wed, Feb 23, 2022 at 1:03 PM Dave Fisher <wave4d...@comcast.net> wrote:
>
>> Hi -
>>
>> Has anyone else found another breaking issue?
>>
>> Just asking to save Peng Hui time if there is another fix for RC2,
>>
>> All the best,
>> Dave
>>
>> Sent from my iPhone
>>
>> > On Feb 22, 2022, at 8:31 PM, PengHui Li <peng...@apache.org> wrote:
>> >
>> > Hi all,
>> >
>> > This PR https://github.com/apache/pulsar/pull/14410 fixes a breaking
>> change
>> > in 2.10.0,
>> > without this fix, if users enabled the debug level log and only upgrade
>> the
>> > broker but not the clients,
>> > we will get exception.
>> >
>> > I will cherry-pick this one to branch-2.10 and rollout a new RC for
>> 2.10.0.
>> >
>> > And https://github.com/apache/pulsar/pull/14409 also fixes a breaking
>> > change which discussed
>> > under the 2.9.3 release thread, it also affects the 2.10.0.
>> >
>> > Thanks,
>> > Penghui
>> >
>> >> On Tue, Feb 22, 2022 at 5:14 PM Andras Beni
>> >> <andras.b...@streamnative.io.invalid> wrote:
>> >>
>> >> +1 (non binding)
>> >>
>> >> Checks done:
>> >>
>> >> - Validated checksums and signatures
>> >>
>> >> - Compiled from source w/ JDK11
>> >>
>> >> - Ran Pulsar standalone and produced-consumed from CLI and validated
>> Java
>> >> functions
>> >>
>> >> Andras
>> >>
>> >>> On Fri, Feb 18, 2022 at 4:08 PM PengHui Li <peng...@apache.org>
>> wrote:
>> >>>
>> >>> This is the first release candidate for Apache Pulsar, version 2.10.0.
>> >>>
>> >>> It fixes the following issues:
>> >>>
>> >>>
>> >>
>> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A2.10.0+is%3Amerged+-label%3Arelease%2F2.9.1+-label%3Arelease%2F2.9.2
>> >>>
>> >>> *** Please download, test and vote on this release. This vote will
>> stay
>> >>> open
>> >>> for at least 72 hours ***
>> >>>
>> >>> Note that we are voting upon the source (tag), binaries are provided
>> for
>> >>> convenience.
>> >>>
>> >>> Source and binary files:
>> >>>
>> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.0-candidate-1/
>> >>>
>> >>> SHA-512 checksums:
>> >>>
>> >>>
>> >>>
>> >>
>> 3bd99e0d48c0e7df247b558aa0e0761f4652264948944b4cacbbacf6ee4052a58a73c0869b660359972f91979fd1bef46b0a980f02a8b8cfb193feb076217606
>> >>> apache-pulsar-2.10.0-bin.tar.gz
>> >>>
>> >>>
>> >>
>> cf3a1c5aa25bc0c8264e8dc4ef53106503c7448aafa9a779e143b07a9426cf58579289930f750748f85910312194b6dc5bd65cded5b0df7b40ae0aca174023ef
>> >>> apache-pulsar-2.10.0-src.tar.gz
>> >>>
>> >>> Maven staging repo:
>> >>>
>> https://repository.apache.org/content/repositories/orgapachepulsar-1142/
>> >>>
>> >>> The tag to be voted upon:
>> >>> v2.10.0-candidate-1 (c58e6e8b33a487b6d9dd10410b7620d33ecb994f)
>> >>> https://github.com/apache/pulsar/releases/tag/v2.10.0-candidate-1
>> >>>
>> >>> Pulsar's KEYS file containing PGP keys we use to sign the release:
>> >>> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>> >>>
>> >>> Docker images:
>> >>>
>> >>> pulsar:2.10.0 [1]
>> >>> pulsar-all:2.10.0 [2]
>> >>>
>> >>> Please download the source package, and follow the Release Candidate
>> >>> Validation[3]
>> >>> to validate the release
>> >>>
>> >>> [1]
>> >>>
>> >>>
>> >>
>> https://hub.docker.com/layers/193225180/lph890127/pulsar/2.10.0/images/sha256-c264084cd34e3952ec4c1f4177c5122251ef39a3af60b7a229851972675706d8?context=repo
>> >>> [2]
>> >>>
>> >>>
>> >>
>> https://hub.docker.com/layers/193227776/lph890127/pulsar-all/2.10.0/images/sha256-7e2297dfabbd1d433198c3bc906c09802394da0d41393f2069e515d7131e4be2?context=repo
>> >>> [3]
>> https://github.com/apache/pulsar/wiki/Release-Candidate-Validation
>> >>>
>> >>
>>
>>

Reply via email to