Hi, Enrico,
> On the other side we should not encourage people to use 'latest' in
production as because it is by design unpredictable.
Agree. Fortunately, for the current document, we don't encourage
people to use 'latest', We specify the specific version when starting
the Pulsar docker in the do
+1 (binding)
Built from sources
Run some smoke tests with Pulsar standalone
Verified checksums and signatures (I had to import KEYS, there was a new key)
Enrico
Il giorno mer 13 dic 2023 alle ore 09:42 guo jiwei
ha scritto:
>
> +1 (binding)
>
> - Checked the signatures
> - Built from source
> -
+1 (binding)
Thanks
Yubiao Feng
On Wed, Dec 13, 2023 at 4:23 PM Asaf Mesika wrote:
> Hi,
>
> I'm starting the vote for PIP-323, since it has been reviewed by several
> people and all comments have been resolved.
>
> Reminder:
>
> PIP-323 is introduced to fill the gap of backlog quota telemetry.
+1(binding)
Best,
Mattison
> On Dec 13, 2023, at 16:22, Asaf Mesika wrote:
>
> Hi,
>
> I'm starting the vote for PIP-323, since it has been reviewed by several
> people and all comments have been resolved.
>
> Reminder:
>
> PIP-323 is introduced to fill the gap of backlog quota telemetry. It
https://github.com/apache/pulsar/pull/21747
Hi Pulsar Community,
Do we consider the 2.10 release line EOL? If not, is there a committer
that would like to volunteer to release 2.10.6?
We briefly discussed keeping 2.10 alive in June [0], and that was
followed by a 2.10.5 release in July. Given that we already have 2.11,
3.0, 3.1, and now a
+1
Thanks
Yubiao Feng
On Tue, Nov 28, 2023 at 4:04 PM Yuri Mizushima wrote:
> Hi, Pulsar Community
>
> This thread is starting a vote for PIP-282.
>
> PIP design PR:
> https://github.com/apache/pulsar/pull/20776
>
> discussion thread:
> https://lists.apache.org/thread/69fpb0d30y7pc02k3zvg2lpb2l
