Hello Apache Pulsar Community,
This is a call for the vote to release the Apache Pulsar Helm Chart version
3.2.0.
Release notes for 3.2.0-candidate-3:
https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.2.0-candidate-3
The release candidate is available at:
https://dist.apache.org
This release vote is cancelled since there's a new vote out for Apache Pulsar
Helm Chart 3.2.0-candidate-3:
https://lists.apache.org/thread/6wst9jqg0w9otyn4ltwoq574029czoqy
-Lari
On 2024/01/18 06:06:45 Lari Hotari wrote:
> Hello Apache Pulsar Community,
>
> This is a call for the vote to releas
Thank you for reviewing and merging the PR #21937 (restoring the broker id
format). I have cherry-picked that to branch-3.2 together with it's dependency
PR #21894 (fixes leader broker election when advertised listeners is
configured) and in addition #21871 (pulsar-bom).
>From my side we are re
Since there's going to be one more release candidate for 3.2.0 , I have
cherry-picked PIP-326 (pulsar-bom) to branch-3.2. pulsar-bom is a low risk
addition to the release.
-Lari
On 2024/01/18 17:54:22 Chris Bono wrote:
> The Pulsar BOM (PIP-326) implementation missed the initial timeline to
> b
Hi yunze,
Thanks for reporting this. Actually, the `VERSION` file is not used in
the code even before that PR. We currently have two hardcoded version
files in place: `VERSION` which represents the current version and
`stable.txt` which represents the current stable version. However, I'm
curious
I agree with retaining this file in this 0.12.0 release to avoid some
unexpected changes. We can estimate whether it's safe to remove the
VERSION file later.
Thanks,
Yunze
On Mon, Jan 22, 2024 at 10:18 AM Zike Yang wrote:
>
> Hi yunze,
>
> Thanks for reporting this. Actually, the `VERSION` file
