+1 (binding)
- verified source release file hash and signature
- ran build
- validated the Nuget package using a simple Pulsar app
Using dotnet sdk 9.0.203 (dotnet --version) on MacOS arm64.
Used the documented validation process on MacOS:
https://github.com/apache/pulsar-dotpulsar/blob/master/do
Hi everyone,
Please review and vote on the release candidate for the version 4.2.3, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
DotPulsar's KEYS file contains the PGP keys we used to sign this release:
https://downloads.apache.or
Hi community,
There have been some bug fixes recently, as well as the fix [1] that
bumps versions of some dependencies to address CVEs. It's time to
release a patched release 3.7.1.
I will start the 3.7.1 release once the existing PRs with
`release/3.7.1` labels are merged.
[1] https://github.co
+1 (binding)
- Verified checksum and signatures
- Built from source with Go 1.23.4 on macOS
- Run perf tools
I also agree that we should not block this release so long for a PR
that does not fix a regression. We don't need to rush into including
that fix in 0.15.0.
Thanks,
Yunze
On Fri, Apr 18,
There is a thread about cherry-picking the changes:
https://lists.apache.org/thread/g1jq0vkq0wt28mdnbg63bpw8fpx9ml42
Similar changes have also been made in the past to maintenance branches, so
this is not anything exceptional to bring up for discussion and then
cherry-pick to maintenance branch
Hi all,
https://github.com/apache/pulsar/pull/24118 introduces breaking
changes on the downstream applications without a PIP.
For example, our internal Kafka protocol implementations heavily rely
on the behavior that partitions can be produced or consumed even if
the partition metadata is deleted
I see the discussion now. So there is nothing wrong with the process.
Adding an option to configure this behavior is acceptable as a quick
solution to me as well.
Thanks,
Yunze
On Tue, Apr 22, 2025 at 9:15 PM Lari Hotari wrote:
>
> There is a thread about cherry-picking the changes:
> https://l
Hi all,
I prepared a quick fix: https://github.com/apache/pulsar/pull/24195 so
that we can fix the regression quickly in 3.0, 3.3 and 4.0 releases. I
devoted my time addressing this breaking change because it's my
responsibility that I missed the previous open discussion in the ML
list. But I didn
I noticed that the following KoP tests need to be updated:
OffsetResetTest.java, GroupCoordinatorTest.java, and
TransactionStateManagerTest.java. The breakage is limited to test scenarios
only.
> It has been valid and allowed to create producers or readers
directly on partitions if the partition co
I'm aware that #24118 breaks some test cases, but I believe those test
cases were incorrect. I also flagged this PR as introducing breaking
changes in the mailing list, please see
https://lists.apache.org/thread/g1jq0vkq0wt28mdnbg63bpw8fpx9ml42
I'd like to better understand the scope of the breaka
Hi Zixuan,
If you're maintaining your own private KoP fork and upgrading the
Pulsar dependency to include this PR, all tests in
`GroupCoordinatorTest` fail without changes. I didn't have a chance to
look into all the failed tests for now. But at least, there are 37
tests failing due to the same re
+1 (binding)
/db
David Jensen skrev den 2025-04-22 11:46:
Hi everyone,
Please review and vote on the release candidate for the version 4.2.3,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
DotPulsar's KEYS file contains the PGP k
12 matches
Mail list logo
