I agree to add an admin API to the go client, this would be very helpful.
Il giorno ven 17 feb 2023 alle ore 08:44 Zixuan Liu
ha scritto:
>
> Hi Zhangjian,
>
> This is a good idea to write the admin client by golang, but I don't
> suggest add the admin features to pulsar-go-client, it's better to
Oh that's right. Then we have to update one of them.
Thanks,
Yunze
On Fri, Feb 17, 2023 at 3:02 PM Zike Yang wrote:
>
> Hi, Yunze
>
> I think the KEYS file in the release repo is necessary. They are both
> used to verify the release file. Otherwise, the user will fail when
> checking the GPG sig
I checked with Sijie today.
StreamNative can contribute the pulsarctl project to Apache Foundation.
Regards,
Penghui
On Fri, Feb 17, 2023 at 4:02 PM Enrico Olivelli wrote:
> I agree to add an admin API to the go client, this would be very helpful.
>
> Il giorno ven 17 feb 2023 alle ore 08:44 Zi
Actually we shouldn't have a "dev" KEYS file. It is confusing.
I suggest dropping it.
When a new committer wants to cut a release they can ask for help to
the PMC to add their KEY to the "release" KEYS
Enrico
Il giorno ven 17 feb 2023 alle ore 09:21 Yunze Xu
ha scritto:
>
> Oh that's right. Th
Hi, Yunze
Seems that you didn't add your public key here [0]. There is an issue
when verifying the Pulsar C++ Client 3.1.2 released files:
```
➜ pulsar-archive gpg --verify apache-pulsar-client-cpp-3.1.2.tar.gz.asc
gpg: assuming signed data in 'apache-pulsar-client-cpp-3.1.2.tar.gz'
gpg: Signatur
> When a new committer wants to cut a release they can ask for help to
the PMC to add their KEY to the "release" KEYS
I agree. We should only allow a PMC member to update the key.
> Seems that you didn't add your public key here [0].
Yes, I found this issue as well, my key is only added to the d
I've synchronized the missed keys from dev to release, including the
following committers:
- Yunze Xu
- Yuto Furuta
- xiangying
- Baodi Shi
See https://dist.apache.org/repos/dist/release/pulsar/KEYS
Regarding whether to drop the KEYS in the dev repo, let's wait more opinions.
Thanks,
Yunze
On F
Hi PengHui,
Now I changed my mind a bit. Even if the pulsarctl was contributed to
the Apache Foundation, I think we should also avoid adding it as the
dependency. What we need is an API layer but not the CLI, while
pulsarctl couples the API and CLI.
At the moment, my expectation is:
1. Use a sepa
The Apache Pulsar team is proud to announce Apache Pulsar Client C++
version 3.1.2.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor managemen
> Actually we shouldn't have a "dev" KEYS file. It is confusing.
Make sense to me.
Thanks,
Zike Yang
Zike Yang
On Fri, Feb 17, 2023 at 5:37 PM Yunze Xu wrote:
>
> I've synchronized the missed keys from dev to release, including the
> following committers:
> - Yunze Xu
> - Yuto Furuta
> - xian
Hi everyone,
This is the first release candidate for Apache Pulsar Node.js client,
version 1.8.1.
It fixes the following
issues:https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.1+is%3Aclosed
Please download the source files and review this release candidate:
-
This is the 3rd release candidate for Apache Pulsar Client Python,
version 3.1.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-python/milestone/2?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Python wheel
Hi Yunze,
Yes, we can split it.
Both one repo with two modules or two repos works for me.
The pulsarctl already have the admin API and CLI.
So I think we don’t need to develop another one.
Best,
Penghui
> On Feb 17, 2023, at 17:44, Yunze Xu wrote:
>
> Hi PengHui,
>
> Now I changed my mind a
Hello,
I see that some "Pulsar Community Bot" appeared in Slack
it is connected to this email address "pulsar.community@gmail.com"
While I find this thing "amazing"I wonder if I missed something,
who is the owner of this "bot" ?
Enrico
Il giorno gio 16 feb 2023 alle ore 16:03 Kiryl Val
Thank for StreamNative for willing to donate this project. This means we
don't have to develop and maintain a set of HTTP code from scratch. My idea
aligns with Yunze's, and separating it into a standalone pulsar-admin-go
project would be better. The **pulsarctl** repo contains bookkeeper http
call
I’m the owner of this account.
The goal is to test drive duplicating Slack questions to the GitHub discussions.
With the current level of activity in Slack it’s not so hard to do it manually.
I’m in CET now. I can share the account credentials with people who can post
questions to GitHub Discussi
My concern is that users should have a choice on where to post their questions.
They might have concerns about GitHub’s terms and conditions. We can pin a
message to slack pointing to GitHub discussions and stackoverflow.
Best,
Dave
Sent from my iPhone
> On Feb 17, 2023, at 9:22 AM, Kiryl Valk
What about such wording?
---
Your question was moved here: https://github.com/apache/pulsar/discussions/123
Please consider asking new questions here:
* At StackOverflow using apache-pulsar tag.
* In the Q&A category at GitHub Discussions.
* Apache Pulsar User Mailing List.
It will
Thanks everyone for voting.
I'm closing the vote with 8 binding +1s and 2 non-binding +1s
Binding:
* Matteo
* Nozomi
* PengHui
* Nicolò
* Yunze
* Hang
* Michael
* Enrico
Non-Binding:
* Zike
* Mattison
--
Matteo Merli
On Mon, Feb 13, 2023 at 11:06 PM Enrico Olivelli
wrote:
> +1 (bi
Hi Haiting,
We'll publish the LTS and end-of-life policy on the website, with the
support dates for each release.
--
Matteo Merli
On Mon, Feb 13, 2023 at 6:27 PM Haiting Jiang
wrote:
> Hi Matteo,
>
> I noticed that 2.10 is not mentioned to be the first LTS version as
> discussed previously.
Async-http-client has always been super-stable in the past and is being
used by many other Java projects. I don't see any risk of being abandoned.
The fact that activity was quiet is mostly related to this project being
"complete" from a feature standpoint (which is good).
The alternatives are rea
Since the LTS release model has been formally approved, I'm proposing
the following schedule for the release:
* Tue - 2023-05-11
- RC-1
- Code Freeze -- Only critical fixes will be merged in the 3.0
release branch. Contributors should plan to have all the changes merged in
before th
Hi all,
Thank your for your point!
Closed now.
Thanks,
Zixuan
Matteo Merli 于2023年2月18日周六 06:36写道：
> Async-http-client has always been super-stable in the past and is being
> used by many other Java projects. I don't see any risk of being abandoned.
> The fact that activity was quiet is most
I support breaking this into two PIPs. It was my fault the two PIPs
were merged in the first place. I am sorry if I created any confusion.
My intention was only to point out that names are a meaningful way to
simplify logic, and we should reserve certain names for Pulsar's own
usage with a well def
+1 I support this timeline.
> I also wanted to propose trying out a model where we have 3 release
> managers for all major releases.
Great idea, this will be a valuable improvement to our release
process. It also creates an opportunity for new committers to ease
into the release management role.
+1 awesome plan.
Thanks,
Zixuan
Michael Marshall 于2023年2月18日周六 14:33写道：
> +1 I support this timeline.
>
> > I also wanted to propose trying out a model where we have 3 release
> > managers for all major releases.
>
> Great idea, this will be a valuable improvement to our release
> process. It a
+1.
I think that there is a typo. See below.
Sent from my iPhone
> On Feb 17, 2023, at 2:44 PM, Matteo Merli wrote:
>
> Since the LTS release model has been formally approved, I'm proposing
> the following schedule for the release:
>
> * Tue - 2023-05-11
> - RC-1
> - Code Freeze
Ups,
I started from the release date I was meaning April for the RCs:
* Tue - 2023-04-11
* Tue - 2023-04-18 - RC-2
* Tue - 2023-04-25 - RC-3
* Tue - 2023-05-02 - Announce 3.0 Release
Sorry for the mixup!
--
Matteo Merli
On Fri, Feb 17, 2023 at 10:39 PM Dave Fisher wrote:
> +1.
>
> I th
+1 - this timeline sounds even better :)
On Sat, Feb 18, 2023 at 12:41 AM Matteo Merli wrote:
>
> Ups,
>
> I started from the release date I was meaning April for the RCs:
>
> * Tue - 2023-04-11
> * Tue - 2023-04-18 - RC-2
> * Tue - 2023-04-25 - RC-3
> * Tue - 2023-05-02 - Announce 3.0 Releas
29 matches
Mail list logo
