Hi
Cancel this vote, details are here
https://github.com/apache/pulsar/issues/18598
Regards
Jiwei Guo (Tboy)
On Thu, Nov 24, 2022 at 5:54 PM guo jiwei wrote:
> Hi
> We found a case that may break the old users. could we discuss if we
> need to resolve that and then continue to validate t
Hi
We found a case that may break the old users. could we discuss if we need
to resolve that and then continue to validate this release?
https://github.com/apache/pulsar/issues/18598
Regards
Tboy
On Thu, Nov 24, 2022 at 3:56 PM Haiting Jiang
wrote:
> +1 binding
>
> - Checksum and signatu
+1 binding
- Checksum and signatures
- Built from sources using `mvn clean install -DskipTests` using JDK
17 and maven 3.6.1
- Run Pulsar standalone and produce/consume case
- Validate Pub/Sub and Java Functions
- Validate Connectors
- Validate Stateful Functions
- Run a simple performance check
Hi Dave
All of the artifacts are signed by me.
Regards
Tboy
On Thu, Nov 24, 2022 at 11:10 AM Dave Fisher wrote:
> I haven’t checked and it’s ok to have more than one release manager for a
> release. But are all of the artifacts signed by one individual or both TBoy
> and Nicolo?
>
> The
I haven’t checked and it’s ok to have more than one release manager for a
release. But are all of the artifacts signed by one individual or both TBoy and
Nicolo?
The rule is who builds it signs it.
Best,
Dave
Sent from my iPhone
> On Nov 23, 2022, at 6:41 PM, guo jiwei wrote:
>
> Hi Nicolo
Hi Nicolo
Added to the repo.
Regards
Jiwei Guo (Tboy)
On Thu, Nov 24, 2022 at 1:03 AM Nicolò Boschi wrote:
> Hi, thanks for driving the release
>
> I found out that I forgot to add Pulsar Shell (PIP-181) artifacts to the
> staging script, so I created these two pull requests:
> - https://
Hi, thanks for driving the release
I found out that I forgot to add Pulsar Shell (PIP-181) artifacts to the
staging script, so I created these two pull requests:
- https://github.com/apache/pulsar/pull/18583
- https://github.com/apache/pulsar-site/pull/302
Since you built all the repo locally, I
Hi Haiting
> Is this expected or a bug?
Yes, it's expected. we can ignore this step. I will correct the doc later.
> I think you mean RocksDB, it's the default for standalone.
Thanks for correcting it.
Regards
Jiwei Guo (Tboy)
On Wed, Nov 23, 2022 at 3:29 PM Enrico Olivelli wrote:
Il giorno mer 23 nov 2022 alle ore 05:43 Haiting Jiang
ha scritto:
>
> Hi Jiwei,
>
> Thank you for cutting this RC.
>
> When following the processes in "Validate Release Candidate",
> command `nc -vz4 localhost 4181` fails. which means table service is
> not started in standalone mode.
> Is this e
Hi Jiwei,
Thank you for cutting this RC.
When following the processes in "Validate Release Candidate",
command `nc -vz4 localhost 4181` fails. which means table service is
not started in standalone mode.
Is this expected or a bug?
> Since the metadata store is changed from ZK to etcd,
I think y
10 matches
Mail list logo
