The issue blocking the release has been resolved and I will start the 3.0.13, 3.3.8 and 4.0.6 release candidates after validating that Pulsar CI status for the maintenance branches looks ok.
-Lari On 2025/07/26 13:51:02 Lari Hotari wrote: > Heesung helped resolve the remaining issues with ExtensibleLoadManager tests > in branch-3.3, thank you. > > There's a remaining issue blocking the release that was most likely triggered > by PR "[fix][broker] Fix Broker OOM due to too many waiting cursors and reuse > a recycled OpReadEntry incorrectly #24551" > (https://github.com/apache/pulsar/pull/24551). > This reveals a broader issue in ManagedCursor state and lifecycle management > that has been present for a long time and has become worse with some changes > in the past. > > I have created PR #24569 (https://github.com/apache/pulsar/pull/24569) to > address these issues. The change is still in progress and needs some more > work. I'd appreciate initial feedback on the approach. > > -Lari > > On 2025/07/24 21:23:53 Lari Hotari wrote: > > It seems that branch-3.3 continues to have some issues with > > ExtensibleLoadManager. > > ExtensibleLoadManagerImplTest.testHandleNoChannelOwner and > > ExtensibleLoadManagerImplTest.testRoleChange fail (examples in > > https://github.com/apache/pulsar/actions/runs/16504885952/job/46672818468 . > > In branch-3.0 these are fine. > > The integration tests running in containers also fail for branch-3.3 for > > ExtensibleLoadManagerTest.testIsolationPolicy , examples in > > https://github.com/apache/pulsar/actions/runs/16504885626/job/46673949729 . > > > > I'd appreciate assistance in resolving these issues so that the releases > > don't get delayed. > > > > -Lari > > > > On 2025/07/24 18:30:40 Lari Hotari wrote: > > > To address the ExtensibleLoadManager issues, Zixuan provided a fix for > > > branch-3.0 in https://github.com/apache/pulsar/pull/24451 which has been > > > backported to branch-3.3. > > > Thank you, Zixuan for unblocking the releases! > > > I'll start the CI runs for maintenance branches to find out the current > > > state. > > > We also have PR 24522 merged and cherry-picked, so we should be soon > > > ready to start the release. > > > > > > -Lari > > > > > > On 2025/07/23 17:19:54 Lari Hotari wrote: > > > > 3.0.13 and 3.3.8 releases are currently blocked due to multiple failing > > > > ExtensibleLoadManager related tests in Pulsar CI. I asked for help from > > > > Zixuan in investigating these issues. > > > > > > > > latest CI runs for branch-3.0: > > > > https://github.com/apache/pulsar/actions/runs/16471469993 Pulsar CI > > > > https://github.com/apache/pulsar/actions/runs/16471470166 Pulsar CI > > > > Flaky > > > > > > > > latest CI runs for branch-3.3: > > > > https://github.com/apache/pulsar/actions/runs/16471494841 Pulsar CI > > > > https://github.com/apache/pulsar/actions/runs/16471495023 Pulsar CI > > > > Flaky > > > > > > > > All Pulsar CI runs can be found at > > > > https://github.com/apache/pulsar/actions/workflows/pulsar-ci.yaml > > > > https://github.com/apache/pulsar/actions/workflows/pulsar-ci-flaky.yaml > > > > > > > > It's possible to add a branch filter such as "branch:branch-3.0" to get > > > > the latest runs for a specific maintenance branch: > > > > https://github.com/apache/pulsar/actions/workflows/pulsar-ci.yaml?query=branch%3Abranch-3.0 > > > > https://github.com/apache/pulsar/actions/workflows/pulsar-ci-flaky.yaml?query=branch%3Abranch-3.0 > > > > > > > > In addition to resolving the failing ExtensibleLoadManager related > > > > tests for branch-3.0 and branch-3.3, we are waiting for the resolution > > > > of https://github.com/apache/pulsar/pull/24522 before proceeding with > > > > the releases. > > > > > > > > -Lari > > > > > > > > On 2025/07/17 16:33:36 Lari Hotari wrote: > > > > > Hi all, > > > > > > > > > > I'd like to discuss initiating the next set of Pulsar maintenance > > > > > releases 3.0.13, 3.3.8 and 4.0.6. > > > > > The previous releases were initiated on May-20 and completed on > > > > > May-23. > > > > > > > > > > Changes in branch-3.0 since 3.0.12: > > > > > https://github.com/apache/pulsar/compare/v3.0.12...branch-3.0 > > > > > > > > > > Changes in branch-3.3 since 3.3.7: > > > > > https://github.com/apache/pulsar/compare/v3.3.7...branch-3.3 > > > > > > > > > > Changes in branch-4.0 since 4.0.5: > > > > > https://github.com/apache/pulsar/compare/v4.0.5...branch-4.0 > > > > > > > > > > The main reason for these releases is to get the BookKeeper 4.17.2 > > > > > upgrade into Pulsar 3.3.x and 4.0.x and BookKeeper 4.16.7 upgrade > > > > > into Pulsar 3.0.x. > > > > > The latest BookKeeper releases contain important fixes for issues > > > > > which could lead to data loss. Please check the BookKeeper release > > > > > notes for more details: > > > > > https://bookkeeper.apache.org/release-notes/ > > > > > > > > > > Unless there are any objections, I'll create release candidates for > > > > > 3.0.13, 3.3.8 and 4.0.6 asap. > > > > > > > > > > -Lari > > > > > > > > > > > > > > >
