Hi all,

I'd like to discuss initiating the next set of Pulsar maintenance
releases: 3.0.14, 3.3.9, 4.0.7, and 4.1.1.

The previous releases were initiated on July 17 and completed on July 31.

Changes in branch-3.0 since 3.0.13:
https://github.com/apache/pulsar/compare/v3.0.13...branch-3.0

Changes in branch-3.3 since 3.3.8:
https://github.com/apache/pulsar/compare/v3.3.8...branch-3.3

Changes in branch-4.0 since 4.0.6:
https://github.com/apache/pulsar/compare/v4.0.6...branch-4.0

Changes in branch-4.1 since 4.1.0:
https://github.com/apache/pulsar/compare/v4.1.0...branch-4.1

Some notes about the upcoming releases:

For Pulsar 3.3.9: Although branch-3.3 is generally unmaintained, we're
making an exception for this release. Spring Pulsar 1.2.x uses Pulsar
Client 3.3.x and there's a reported Spring Boot dependency issue that
requires a fix in Pulsar.
- Fix: https://github.com/apache/pulsar/pull/24742
- Pulsar issue: https://github.com/apache/pulsar/issues/24740
- Spring Boot issue: https://github.com/spring-projects/spring-boot/issues/42522

For Pulsar 4.0.7 and 4.1.1: Both releases will include an important
fix for Key_Shared subscriptions PIP-379 implementation where
consuming could get stuck in certain situations.
- Fix: https://github.com/apache/pulsar/pull/24736

Please review the full change log links above for complete details on
all fixes and improvements included in these releases.

Unless there are any objections, I'll create release candidates for
3.0.14, 3.3.9, 4.0.7, and 4.1.1 as soon as possible.

-Lari

Reply via email to