Hello Pulsar community,

Here's the updated Pulsar 4.0 timeline:
2024-10-11: [Completed] Code freeze for 4.0 by branching branch-4.0 from the 
master branch
2024-10-14: 4.0 release candidate 1 - Release candidate voting starts
2024-10-17: Reserved for 4.0 release candidate 2 if needed
2024-10-24: 4.0.0 announcement

Known important issues for the release are tracked with the "release/blocker" 
label at
https://github.com/apache/pulsar/labels/release%2Fblocker
These aren't true blockers. We might choose to have a release candidate 2 if 
there's a true release blocker.

All current open PRs targeting the 4.0.0 milestone have been moved to 4.1.0 
milestone.
Already approved PRs targeting 4.0.0 have been labeled with "release/4.0.1".

>From now on, new PRs targeting 4.0.0 should be labeled with "release/4.0.0" to 
>be considered for the 4.0.0 release. Or with "release/4.0.1" to be considered 
>for 4.0.1 release.

Please reply to this thread or contact me directly if there are PRs that should 
be cherry-picked to the 4.0.0 release.

Don't cherry-pick anything on your own, I'll coordinate the cherry-picks since 
I'm responsive in delivering 4.0.0 on schedule. When necessary, I'll revert 
cherry-picks from branch-4.0 in order to meet the deadline.

Please let me know if you have any questions or feedback.
I'll start release candidate 1 on Monday. It's possible it won't be until 
Tuesday that I have the release candidate ready and voting begins.

-Lari

Reply via email to