In addition to #16202, there is a following PR to support the correct
ACK implementation for chunked messages. It should depend on #16202
But I think I can submit an initial PR this week and change the tests
after #16202 is merged.
 
Thanks,
Yunze




> 2022年7月18日 11:22,PengHui Li <peng...@apache.org> 写道:
> 
> Hi all,
> 
> We released 2.10.0 three months ago. And there are many great changes in
> the master branch,
> including new features and performance improvements.
> 
> - PIP 74: apply client memory to consumer
> https://github.com/apache/pulsar/pull/15216
> - PIP 143: Support split bundles by specified boundaries
> https://github.com/apache/pulsar/pull/13796
> - PIP 145: regex subscription improvements
> https://github.com/apache/pulsar/pull/16062
> - PIP 160: transaction performance improvements (still in progress and
> merged some PRs)
> - PIP 161: new exclusive producer mode support
> https://github.com/apache/pulsar/pull/15488
> - PIP 182: Provide new load balance placement strategy implementation for
> ModularLoadManagerStrategy https://github.com/apache/pulsar/pull/16281
> Add Pulsar Auth support for the Pulsar SQL
> https://github.com/apache/pulsar/pull/15571
> 
> And some features are blocked in the review stage, but they are powerful
> improvements for Pulsar
> 
> PIP 37: Support chunking with Shared subscription
> https://github.com/apache/pulsar/pull/16202
> PIP-166: Function add MANUAL delivery semantics
> https://github.com/apache/pulsar/pull/16279
> 
> You can find the complete change list in 2.11.0 at
> https://github.com/apache/pulsar/pulls?q=is%3Apr+milestone%3A2.11.0+-label%3Arelease%2F2.10.1+-label%3Arelease%2F2.10.2
> 
> And maybe I missed some important in-progress PRs, please let me know if it
> should be a blocker of the 2.11.0 release.
> 
> It's a good time to discuss the target time of the 2.11.0 release.
> I think we can leave 2 weeks to complete the in-progress PRs and 2 weeks to
> accept bug fixes.
> And target the 2.11.0 release in mid-August.
> 
> Please let me know what you think.
> 
> Thanks,
> Penghui

Reply via email to