> I think we need to state the release deadline before each feature
release. What’s the deadline of 3.2.0? @Jiwei Maybe we could start the vote
now?
Yes, I will raise the `VOTE` thread soon.
Regards
Jiwei Guo (Tboy)
On Tue, Jan 30, 2024 at 9:55 AM Zike Yang wrote:
> Based on the release
> po
Based on the release
policy(https://pulsar.apache.org/contribute/release-policy/), for each
feature release, there would be three weeks to verify the release
candidate before the release deadline. And the first two weeks are
only for verification.
I think we need to state the release deadline befo
Is this a release VOTE thread? I think that the subject of the thread should
state that explicitly.
What does a VERIFY thread mean? We don't have that in our release process
documented at https://pulsar.apache.org/contribute/release-process/ .
Thanks,
-Lari
On 2024/01/27 15:14:27 guo jiwei w
+1 (binding)
- Built from source
- Checked the signatures
- Run standalone
- Checked producer and consumer
- Verified the Cassandra connector
- Verified the Stateful function
Regards,
Penghui
On Sat, Jan 27, 2024 at 11:15 PM guo jiwei wrote:
> This is the fifth release candidate for Apache Pul
This is the fifth release candidate for Apache Pulsar version 3.2.0.
It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1
*** Please download, test and verify on this release. This release
candidate verification will stay open until Feb 2 ***
Note that we are ver
