Re: [ANNOUNCE] Zike Yang as a new PMC member in Apache Pulsar
Congratulations! Zike Best, Max Xu On Thu, Apr 11, 2024 at 9:26 PM PengHui Li wrote: > The Apache Pulsar Project Management Committee (PMC) has invited > Zike Yang https://github.com/RobertIndie to join the PMC, > and we are pleased to announce that he has accepted. > > Zike Yang is actively driving the Golang client release, contributing to > multiple > Pulsar repos, Golang client, CPP Client, Python Client, and Pulsar main > repo. > > On behalf of the Pulsar PMC, we extend a heartfelt welcome and > congratulations to Zike Yang. > > Regards, > Penghui >
Re: [ANNOUNCE] Baodi Shi as a new PMC member in Apache Pulsar
Congratulations! Baodi Best, Max Xu On Thu, Apr 11, 2024 at 9:23 PM PengHui Li wrote: > The Apache Pulsar Project Management Committee (PMC) has invited > Baodi Shi https://github.com/shibd to join the PMC, > and we are pleased to announce that he has accepted. > > Baodi Shi is actively driving the NodeJS client release, contributing to > multiple > Pulsar repos, Nodejs client, CPP Client, Python Client, and Pulsar main > repo. > > On behalf of the Pulsar PMC, we extend a heartfelt welcome and > congratulations to Baodi Shi. > > Regards, > Penghui >
Re: [ANNOUNCE] New Committer: Asaf Mesika
Congratulations, Asaf! Well deserved. Best, Max Xu On Wed, Feb 21, 2024 at 12:51 AM Lari Hotari wrote: > The Apache Pulsar Project Management Committee (PMC) has invited > Asaf Mesika https://github.com/asafm to become a committer and we > are pleased to announce that he has accepted. > > Welcome and Congratulations, Asaf Mesika! > > Please join us in congratulating and welcoming Asaf onboard! > > Best Regards, > > Lari Hotari > on behalf of the Pulsar PMC >
Re: [ANNOUNCE] Yubiao Feng as new PMC member in Apache Pulsar
Congratulations! Yubiao, well deserved Best, Max Xu On Mon, Nov 13, 2023 at 3:37 PM mattison chao wrote: > Dear Community, > > We are thrilled to announce that Yubiao Feng > https://github.com/poorbarcode has been invited and has accepted the role > of a member of the Apache Pulsar Project Management Committee (PMC). > > Yubiao Feng has proven to be an invaluable asset to our community, > consistently showcasing dedication and active engagement through > substantial contributions. Beyond his noteworthy technical input, Yubiao > plays a crucial role in meticulously reviewing pull requests, thereby > ensuring the overall excellence of our project. We eagerly anticipate and > appreciate his ongoing contributions. On behalf of the Pulsar PMC, we > extend a heartfelt welcome and congratulations to Yubiao Feng. > > Sincerely, > Mattison
Re: [VOTE] Pulsar Client Go Release 0.11.1 Candidate 1
The KEYS file link is dead, I think it should be https://downloads.apache.org/pulsar/KEYS On Mon, Oct 30, 2023 at 10:02 AM PengHui Li wrote: > +1 (binding) > > - Verified the signatures > - Build from the source > - Run the test on Pulsar 3.1.1 (make test PULSAR_VERSION=3.1.1) > - Run the test on Pulsar 3.0.1 (make test PULSAR_VERSION=3.0.1) > > Regards, > Penghui > > On Fri, Oct 20, 2023 at 4:46 PM Yunze Xu wrote: > > > +1 (binding) > > > > - Verified checksum and signatures > > - Build the perf tool from source > > - Run the perf to produce and consumer for some time > > > > Thanks, > > Yunze > > > > On Mon, Sep 11, 2023 at 6:08 PM Zike Yang wrote: > > > > > > Hi everyone, > > > Please review and vote on the release candidate #1 for the version > > > 0.11.1, as follows: > > > [ ] +1, Approve the release > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > This is the first release candidate for Apache Pulsar Go client, > version > > 0.11.1. > > > > > > It fixes the following issues: > > > > > > https://github.com/apache/pulsar-client-go/compare/v0.11.0...v0.11.1-candidate-1 > > > > > > Pulsar Client Go's KEYS file contains PGP keys we used to sign this > > release: > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > Please download these packages and review this release candidate: > > > - Review release notes: > > https://github.com/apache/pulsar-client-go/pull/1092 > > > - Download the source package (verify shasum, and asc) and follow the > > > README.md to build and run the pulsar-client-go. > > > > > > The vote will be open for at least 72 hours. It is adopted by majority > > > approval, with at least 3 PMC affirmative votes. > > > > > > Source file: > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.11.1-candidate-1/ > > > > > > The tag to be voted upon: > > > v0.11.1-candidate-1 > > > https://github.com/apache/pulsar-client-go/tree/v0.11.1-candidate-1 > > > > > > SHA-512 checksums: > > > > > > d2209c652918acee8d2c77d52a0a556af16ff7fc3e30ad96d05e01285b83a61d1a1f0d32bace184f830e2dd2e4dd20910e9ce5ae23aac4a40eb3d19885cb0182 > > > apache-pulsar-client-go-0.11.1-src.tar.gz > > >
Re: [VOTE] PIP-265: PR-based system for managing and reviewing PIPs
+1 (non-binding) Thanks for driving this helpful proposal! Best, Max Xu On Wed, May 10, 2023 at 6:52 PM Asaf Mesika wrote: > Hi, > > I'm starting the vote process for PIP-265. > > Link: https://github.com/apache/pulsar/issues/20207 > > Thanks! > > Asaf >
Re: [ANNOUNCE] Qiang Zhao as new PMC member in Apache Pulsar
Congratulations! Qiang Best, Max Xu On Wed, Mar 29, 2023 at 11:23 AM guo jiwei wrote: > Dear Community, > > We are thrilled to announce that Qiang Zhao > (https://github.com/mattisonchao) has been invited and has accepted the > role of member of the Apache Pulsar Project Management Committee (PMC). > > Qiang has been a vital asset to our community, consistently > demonstrating his dedication and active participation through > significant contributions. In addition to his technical contributions, > Qiang also plays an important role in reviewing pull requests and > ensuring the overall quality of our project. We look forward to his > continued contributions. > > On behalf of the Pulsar PMC, we extend a warm welcome and > congratulations to Qiang Zhao. > > Best regards > Jiwei >
Re: Re: Re: Introducer Pulsar admin api to pulsar-client-go
Hi, Enrico, Thanks for your concerns. I suppose we'll initiate the PIP discussion thread soon. Welcome to keep following the current repo https://github.com/streamnative/pulsar-admin-go. Best, Max Xu On Mon, Mar 27, 2023 at 3:09 PM Enrico Olivelli wrote: > Eric, > > Il Lun 27 Mar 2023, 07:44 Shen Eric ha > scritto: > > > Hi Community, > > > > We want to announce and introduce the [Pulsar Admin Go Library]( > > https://github.com/streamnative/pulsar-admin-go) which has been open > > sourced and cut the first release. > > > > The original Pulsar Admin Go Library is from [pulsarctl]( > > https://github.com/streamnative/pulsarctl)'s internal pkg which is not > > convenient for Pulsar Golang developers to use and manage. So, we > decoupled > > the Pulsar Admin related API from pulsarctl and created the > > [pulsar-admin-go](https://github.com/streamnative/pulsar-admin-go) > > library based on it, which also provides a clearer perspective and > > maintainability from an architectural perspective. > > > > In the future plan of this library: > > - Iterate the library and upgrade the related admin API based on the > > Pulsar progress. > > - More testing and dogfood from StreamNative’s golang projects: > > [pulsarctl](https://github.com/streamnative/pulsarctl), > > [terraform-provider-pulsar]( > > https://github.com/streamnative/terraform-provider-pulsar), > > [pulsar-resources-operator]( > > https://github.com/streamnative/pulsar-resources-operator). > > - When the library is stable, will donate it to Apache Foundation. > > > > Thanks for sharing the progress. > > I think that it is better to move the API to the Apache repository and then > we can improve it all together as a community. > It is fine if it is not 100% perfect yet, don't worry about that. > > > Cheers > Enrico > > > > > > -- > > > > Best regards, > > > > Eric Shen > > > > On 2023/03/17 09:09:38 Max Xu wrote: > > > Thanks Yu and Eric for your follow-up. > > > > > > Yes, we're working on that. I believe we will soon see pulsar-admin-go > :) > > > > > > > > > Best, > > > Max Xu > > > > > > > > > On Wed, Mar 15, 2023 at 2:36 PM Yu wrote: > > > > > > > Hi Eric, > > > > > > > > Thanks for sharing the updates! > > > > > > > > I discussed this project with Max previously. We would like to > > contribute > > > > docs for it, and I've already added "Go admin API (coming soon)" to > > the new > > > > Pulsar API docs already [1], which brings many benefits, such as: > > > > > > > > - Build excitement before launch. > > > > - Generate a targeted list of early adopters interested in this > > brand-new > > > > tool. > > > > - Improve SEO by adding relevant keywords. > > > > > > > > [1] > > https://github.com/apache/pulsar-site/pull/462#discussion_r1130770643 > > > > > > > > Yu > > > > > > > > > > > > On Wed, Mar 15, 2023 at 11:56 AM Shen Eric > > > > wrote: > > > > > > > > > Hi Zhangjian, > > > > > > > > > > We can share some progress on our side: > > > > > > > > > > we have completed: > > > > > > > > > > * Extracted the pulsar-admin-go library from the pulsarctl and > moved > > > > > it to a separate repo under StreamNative (now it is private) > > > > > * Updated the project layout and rename some pkg names like the cli > > > > pkg > > > > > > > > > > what we will do next: > > > > > > > > > > * Add some pulsar-admin-go library documentation > > > > > * Setup some CI/CD infra configurations for the repo > > > > > * Then we will release the 0.1.0 and open source this repo > > > > > > > > > > The release of the 0.1.0 and repo open-source we wanna make it in > > March > > > > > and will announce this to the community. > > > > > > > > > > The timeline to donate this project to Apache is undecided now but > we > > > > will > > > > > listen to the feedback from the community and donate it when most > of > > us > > > > > think it's qualified and stable. > > > > > > > > > > On 2023/03/03 04:14:33 ZhangJian He wrote: > > &g
Re: New Pulsar docs (API + CLI) are available!
Yu , Thanks for driving this. It looks great! Best, Max Xu On Thu, Mar 16, 2023 at 8:06 PM Yu wrote: > Hi community, > > To improve the developer experience and take Pulsar content to the next > level, recently we (+@hangc0276) have added some new docs as below. > > === > Fresh New Content > === > > - Pulsar API > (https://pulsar.apache.org/docs/next/pulsar-api-overview/) > > - Pulsar admin API > → Overview (https://pulsar.apache.org/docs/next/admin-api-overview/) > → Use cases (https://pulsar.apache.org/docs/next/admin-api-use-cases/） > → Features (https://pulsar.apache.org/docs/next/admin-api-features/) > → Tools (https://pulsar.apache.org/docs/next/admin-api-tools/) > → Get started (https://pulsar.apache.org/docs/next/admin-api-get-started/) > > - Pulsar client API > (https://pulsar.apache.org/docs/next/client-api-overview/) > > - Pulsar CLI > → pulsar-admin: Get started ( > https://pulsar.apache.org/docs/next/get-started-pulsar-admin/) > > Enjoy reading! > Here [1] are related doc PRs. > We'll add more docs on these topics in the near future. > Feel free to leave your suggestions, TIA! > > === > Acknowledgment > === > > @hangc0276 Huge shout out to you for providing technical input and > guidance! > > @BewareMyPower @horizonzy A big thank you for your technical support! > > === > > [1] > - https://github.com/apache/pulsar-site/pull/462 > - https://github.com/apache/pulsar-site/pull/403 > - https://github.com/apache/pulsar/pull/19002 > - https://github.com/apache/pulsar/pull/18680 > > Yu >
Re: Re: Introducer Pulsar admin api to pulsar-client-go
Thanks Yu and Eric for your follow-up.
Yes, we're working on that. I believe we will soon see pulsar-admin-go :)
Best,
Max Xu
On Wed, Mar 15, 2023 at 2:36 PM Yu wrote:
> Hi Eric,
>
> Thanks for sharing the updates!
>
> I discussed this project with Max previously. We would like to contribute
> docs for it, and I've already added "Go admin API (coming soon)" to the new
> Pulsar API docs already [1], which brings many benefits, such as:
>
> - Build excitement before launch.
> - Generate a targeted list of early adopters interested in this brand-new
> tool.
> - Improve SEO by adding relevant keywords.
>
> [1] https://github.com/apache/pulsar-site/pull/462#discussion_r1130770643
>
> Yu
>
>
> On Wed, Mar 15, 2023 at 11:56 AM Shen Eric
> wrote:
>
> > Hi Zhangjian,
> >
> > We can share some progress on our side:
> >
> > we have completed:
> >
> > * Extracted the pulsar-admin-go library from the pulsarctl and moved
> > it to a separate repo under StreamNative (now it is private)
> > * Updated the project layout and rename some pkg names like the cli
> pkg
> >
> > what we will do next:
> >
> > * Add some pulsar-admin-go library documentation
> > * Setup some CI/CD infra configurations for the repo
> > * Then we will release the 0.1.0 and open source this repo
> >
> > The release of the 0.1.0 and repo open-source we wanna make it in March
> > and will announce this to the community.
> >
> > The timeline to donate this project to Apache is undecided now but we
> will
> > listen to the feedback from the community and donate it when most of us
> > think it's qualified and stable.
> >
> > On 2023/03/03 04:14:33 ZhangJian He wrote:
> > > Hi, Eric. Thank you very much for the work you have done. I have no
> > > objections to the process, and it would be even better if there could
> be
> > a
> > > rough timeline.
> > >
> > > Thanks
> > > ZhangJian He
> > >
> > >
> > > On Fri, 3 Mar 2023 at 09:06, Shen Eric wrote:
> > >
> > > > Hi Zhangjian,
> > > >
> > > > I am a PM from StreamNative and we also had some internal discussions
> > > > related to this topic. Let me share our ongoing planning:
> > > >
> > > > * We will extract the pulsar admin pkg from the pulsarctl to a
> > > > separate open repo which will be called pulsar-admin-go under
> > StreamNative.
> > > > * Will iterate the pulsar-admin-go library by adding more tests,
> > > > documentation and may also update or fix the existing APIs.
> > > > * After the pulsar-admin-go library is stable, we will contribute
> this
> > > > project to Apache Foundation.
> > > >
> > > > Do you think this plan works for you?
> > > >
> > > > On 2023/02/17 01:47:26 ZhangJian He wrote:
> > > > > I would like to express that the current Pulsar client for Go
> > > > > (pulsar-client-go) is missing the pulsar Admin API. As such, I
> would
> > like
> > > > > to propose that we work towards adding this feature to
> > pulsar-client-go.
> > > > >
> > > > > I believe that this new feature would be a valuable addition to
> > > > > pulsar-client-go, and I am excited to work to make it happen.
> > > > >
> > > > > I have submitted a PR:
> > > > https://github.com/apache/pulsar-client-go/pull/959
> > > > > The full api is not currently available, but we are adding.
> > > > >
> > > > > Below is a simple example about how to use
> > > > >
> > > > > ## usage
> > > > >
> > > > > ```go
> > > > > package main
> > > > >
> > > > > import (
> > > > > "fmt"
> > > > > "github.com/apache/pulsar-client-go/padmin"
> > > > > )
> > > > >
> > > > > func main() {
> > > > > admin, err := padmin.NewDefaultPulsarAdmin()
> > > > > if err != nil {
> > > > > panic(err)
> > > > > }
> > > > > // get namespace topic list
> > > > > topics, err := admin.PersistentTopics.ListNamespaceTopics("tenant",
> > > > > "namespace")
> > > > > if err != nil {
> > > > > panic(err)
> > > > > }
> > > > > fmt.Println(topics)
> > > > > }
> > > > > ```
> > > > >
> > > > > Thanks
> > > > > ZhangJian He
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Best regards,
> > > >
> > > > Eric Shen 沈瑀昊
> > > >
> > >
> >
> >
> > --
> >
> > Best regards,
> >
> > Eric Shen 沈瑀昊
> >
>
Re: [ANNOUNCE] New committer: Yuri Mizushima
Congratulations! Yuri Best, Max Xu On Mon, Feb 27, 2023 at 6:55 PM Zike Yang wrote: > Congratulations! Yuri > > BR, > Zike Yang > > On Mon, Feb 27, 2023 at 5:15 PM ZhangJian He wrote: > > > > Congratulations! > > > > Thanks > > ZhangJian He > > > > > > On Mon, 27 Feb 2023 at 17:02, Zhengxin Cai > wrote: > > > > > Congrats! Yuri > > > > > > Zixuan Liu 于2023年2月27日周一 16:04写道： > > > > > > > Congrats! Yuri > > > > > > > > Best, > > > > Zixuan > > > > > > > > Horizon <1060026...@qq.com.invalid> 于2023年2月27日周一 15:57写道： > > > > > > > > > Congrats! > > > > > > > > > > > > > > > > > >
Re: [ANNOUNCE] New Committer: Baodi Shi
Congratulations! Baodi Best, Max Xu On Wed, Jan 18, 2023 at 9:36 PM Yunze Xu wrote: > The Project Management Committee (PMC) for Apache Pulsar has invited > Baodi Shi (https://github.com/shibd) to become a committer and we are > pleased to announce that he has accepted. > > Being a committer enables easier contribution to the project since > there is no need to go via the patch submission process. This should > enable better productivity. > > Welcome and congratulations, Baodi Shi! > > Please join us in congratulating and welcoming Baodi Shi onboard! > > Thanks, > Yunze on behalf of the Pulsar PMC >
Re: [ANNOUNCE] Nicolò Boschi as new PMC member in Apache Pulsar
Congratulations! Nicolò Best, Max Xu On Fri, Jan 20, 2023 at 8:36 PM Lari Hotari wrote: > Dear Community, > > We are thrilled to announce that Nicolò Boschi > (https://github.com/nicoloboschi) has been invited and has accepted the > role of member of the Apache Pulsar Project Management Committee (PMC). > > Nicolò Boschi has been a vital asset to our community, consistently > demonstrating his dedication and active participation through > significant contributions such as the development of the Pulsar Shell > and numerous bug fixes, security enhancements, and improvements to > Pulsar and its CI pipeline. In addition to his technical contributions, > Nicolò also plays an important role in reviewing pull requests and > ensuring the overall quality of our project. We look forward to his > continued contributions. > > On behalf of the Pulsar PMC, we extend a warm welcome and > congratulations to Nicolò Boschi. > > Best regards, Lari, on behalf of the Pulsar PMC >
Re: [ANNOUNCE] Bo Cong as new PMC member in Apache Pulsar
Congratulations! Bo Best, Max Xu On Wed, Jan 18, 2023 at 9:50 PM PengHui Li wrote: > Hi all, > > The Apache Pulsar Project Management Committee (PMC) has invited Bo Cong > (https://github.com/congbobo184) as a member of the PMC and we are > pleased to announce that he has accepted. > > He is very active in the community in the past few years and made a lot of > great contributions > such as transactions and schemas. > > Welcome Bo Cong to the Apache Pulsar PMC. > > Best Regards, > Penghui on behalf of the Pulsar PMC >
Re: [Vote] PIP-231: Add metric for topic load failed
+1 (non-binding) Best, Max Xu On Tue, Dec 27, 2022 at 4:27 PM Jiuming Tao wrote: > Hello pulsar community, > > I'm starting the VOTE for PIP-231: Add metric for topic load failed. > > Motivation: > Currently, we have a `topic_load_times` metric to track how long a topic > load succeeds. > But when loading a topic, there may be some chances the topic load failed > due to MetadataStore or Bookkeeper, and we don't have related metrics to > track it. > > For more details, please read the PIP at > https://github.com/apache/pulsar/issues/18979 > Discuss thread: > https://lists.apache.org/thread/h02wxj1yclo1o3r7otf9gp38hs0g03ym > > Thanks, > Tao Jiuming >
Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar
Congratulations! Yunze Best, Max Xu On Thu, Dec 29, 2022 at 8:42 PM Haiting Jiang wrote: > Hi all, > > The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu > (https://github.com/BewareMyPower) as a member of the PMC and we are > pleased to announce that he has accepted. > > He is very active in the community in the past few years and made a lot of > great contributions. > > Welcome Yunze to the Apache Pulsar PMC. > > Best Regards, > Haiting Jiang on behalf of the Pulsar PMC >
Re: [ANNOUNCE] New Committer: Cong Zhao
Congratulations! Cong Best, Max Xu On Mon, Nov 21, 2022 at 12:10 PM Haiting Jiang wrote: > The Project Management Committee (PMC) for Apache Pulsar has invited > Cong Zhao (https://github.com/coderzc) > to become a committer and we are pleased to announce that he has accepted. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > > Welcome and congratulations, Cong Zhao! > > Please join us in congratulating and welcoming Cong Zhao onboard! > > Best Regards, > Haiting on behalf of the Pulsar PMC >
Re: [ANNOUNCE] New Committer: Lin Chen
Congratulations! Lin Best, Max Xu On Mon, Nov 14, 2022 at 12:28 PM PengHui Li wrote: > The Project Management Committee (PMC) for Apache Pulsar has invited > Lin Chen (https://github.com/lordcheng10) > to become a committer and we are pleased to announce that he has accepted. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > > Welcome and congratulations, Lin Chen! > > Please join us in congratulating and welcoming Lin Chen onboard! > > Best Regards, > Penghui on behalf of the Pulsar PMC >
Re: [ANNOUNCE] New Committer: Zili Chen
Congratulations! Zili Best, Max Xu On Thu, Nov 10, 2022 at 8:16 AM Yu wrote: > The Project Management Committee (PMC) for Apache Pulsar has invited Zili > Chen (https://github.com/tisonkun) > to become a committer and we are pleased to announce that he has accepted. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > > Welcome and congratulations, Zili Chen! > > Please join us in congratulating and welcoming Zili Chen onboard! > > Best Regards, > Yu on behalf of the Pulsar PMC >
Re: [DISCUSS] Release Pulsar 2.9.4
+1 Best, Max Xu On Thu, Nov 3, 2022 at 2:01 PM 丛搏 wrote: > Hello, Pulsar community: > > I'd like to propose releasing Apache Pulsar 2.9.4. It's been about > three months since 2.9.3 was released. > > There are 123 PRs [0] needed to cherry-pick in branch-2.9. I will > cherry-pick these PRs for branch-2.9. Exclude some PRs that merge > directly into branch-2.9. > > There are 33 PRs [1] opened. I'll follow up on each of those PRs to > see if they will be completed soon or will need to be pushed to 2.9.5 > > If you have any important fixes or any questions, please reply to this > email, and we will evaluate whether to include them in 2.9.4 > > Thanks, > Bo > [0] - > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.9.4+-label%3Acherry-picked%2Fbranch-2.9+is%3Amerged > [1] - > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.9.4+is%3Aopen > I will >
Re: [ANNOUNCE] New Committer: Qiang Huang
Congratulations! Qiang Best, Max Xu On Fri, Oct 14, 2022 at 12:04 PM guo jiwei wrote: > The Project Management Committee (PMC) for Apache Pulsar has invited > Qiang Huang (https://github.com/hqebupt) to become a committer and > we are pleased to announce that he has accepted. > > Qiang Huang (with Github id: hqebupt) contributed many improvements > and bug fixes to Pulsar. > > Being a committer enables easier contribution to the project since > there is no need to go via the patch submission process. This should > enable better productivity. > > Welcome and Congratulations, Qiang Huang! > > Please join us in congratulating and welcoming Qiang Huang onboard! > > > Regards > Jiwei Guo on behalf of the Pulsar PMC >
Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2
+1 (non-binding) - Verified the sha-512 checksum - Build from the source code - Run producer and consumer Best, Max Xu On Thu, Sep 29, 2022 at 2:35 PM r...@apache.org wrote: > Hi everyone, > > Please review and vote on the release candidate #2 for the version 0.9.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > This is the second release candidate for Apache Pulsar Go client, > version 0.9.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-go/milestone/10?closed=1 > > Pulsar Client Go's KEYS file contains PGP keys we used to sign this > release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download these packages and review this release candidate: > - Review release notes https://github.com/apache/pulsar-client-go/pull/804 > - Download the source package (verify shasum, and asc) and follow the > README.md to build and run the pulsar-client-go. > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Source file: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.9.0-candidate-2/ > > The tag to be voted upon: > v0.9.0 > https://github.com/apache/pulsar-client-go/releases/tag/v0.9.0-candidate-2 > > SHA-512 checksums: > > 9731d6a0615288e77feb4b73fedbbdf6d275ebefeee3cee5fc4e849f38789863f0532c7e8b93eb1e601bd98f9bb21d50a714fcf87fac9987a745a052bbe23ca3 > apache-pulsar-client-go-0.9.0-candidate-2-src.tar.gz > > Best, > > Xiaolong Ran >
Re: [DISCUSS] Release Pulsar Client C++ 3.0.0
+1 Thanks, Matteo. It's a great work! Best, Max Xu On Fri, Oct 7, 2022 at 2:07 AM Matteo Merli wrote: > We have moved the C++ client to its own separate repo > (https://github.com/apache/pulsar-client-cpp) as part of PIP-209. > > There are several new features and fixes in the main branch that it > would be good to get released, as well to get the new release process > all flushed out. > > Matteo > > > -- > Matteo Merli > >
Re: [VOTE] PIP-209: Separate C++/Python clients to own repositories
+1 (non-binding) Best, Max Xu On Tue, Sep 27, 2022 at 4:50 PM Anon Hxy wrote: > +1 (non binding) > > Thanks, > Xiaoyu Hou > > Nicolò Boschi 于2022年9月27日周二 16:39写道： > > > +1 (non binding) > > Nicolò Boschi > > > > > > Il giorno mar 27 set 2022 alle ore 10:17 Qiang Huang < > > qiang.huang1...@gmail.com> ha scritto: > > > > > +1 (non-binding) > > > > > > Yunze Xu 于2022年9月27日周二 11:35写道： > > > > > > > +1 (non-binding) > > > > > > > > Thanks, > > > > Yunze > > > > > > > > > > > > > > > > > > > > > On Sep 27, 2022, at 11:11, Zixuan Liu wrote: > > > > > > > > > > +1(non-binding) > > > > > > > > > > Thanks, > > > > > Zixuan > > > > > > > > > > Haiting Jiang 于2022年9月27日周二 09:56写道： > > > > > > > > > >> +1 (non) > > > > >> > > > > >> Haiting > > > > >> > > > > >> On Tue, Sep 27, 2022 at 9:30 AM Zike Yang > wrote: > > > > >>> > > > > >>> +1 (non-binding) > > > > >>> > > > > >>> > > > > >>> Zike Yang > > > > >>> > > > > >>> On Tue, Sep 27, 2022 at 9:24 AM Kai Wang < > > wangkai744567...@gmail.com > > > > > > > > >> wrote: > > > > >>>> > > > > >>>> +1 (non-binding) > > > > >>>> > > > > >>>> Thanks, > > > > >>>> Kai > > > > >> > > > > > > > > > > > > > > -- > > > BR, > > > Qiang Huang > > > > > >
Re: [ANNOUNCE] New Committer: Zixuan Liu
Congratulations! Zixuan. Well deserved! Best, Max Xu On Thu, Jul 7, 2022 at 6:04 PM Yu wrote: > Hi team, > > The Project Management Committee (PMC) for Apache Pulsar has invited > Zixuan Liu (https://github.com/nodece) to become a committer > and we are pleased to announce that he has accepted. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > > Welcome and congratulations, Zixuan Liu! > > Please join us in congratulating and welcoming Zixuan Liu onboard! > > Best Regards, > Yu on behalf of the Pulsar PMC >
Re: [ANNOUNCE] New Committer: Dezhi Liu
Congratulations! Dezhi. Well deserved! Best, Max Xu On Tue, Jun 7, 2022 at 2:46 PM Hang Chen wrote: > The Project Management Committee (PMC) for Apache Pulsar has invited > Dezhi Liu (https://github.com/liudezhi2098) to become a committer and > we are pleased to announce that he has accepted. > > Dezhi Liu (with Github id liudezhi2098) contributed many improvements > and bug fixes to Pulsar. > > Being a committer enables easier contribution to the project since > there is no need to go via the patch submission process. This should > enable better productivity. > > Welcome and Congratulations, Dezhi Liu! > > Please join us in congratulating and welcoming Dezhi Liu onboard! > > Best Regards, > Hang Chen on behalf of the Pulsar PMC >
Re: [VOTE] [PIP-204] Extensions for BrokerInterceptor
+1 (non-binding) Best, Max Xu On Thu, Sep 1, 2022 at 12:12 PM tison wrote: > +1 (non-binding) > > Best, > tison. > > > PengHui Li 于2022年9月1日周四 11:20写道： > > > +1 (binding) > > > > Penghui > > > > On Thu, Sep 1, 2022 at 11:06 AM guo jiwei wrote: > > > > > +1 (binding) > > > > > > Regards > > > Jiwei Guo (Tboy) > > > > > > > > > On Wed, Aug 31, 2022 at 10:11 AM Haiting Jiang > > > > wrote: > > > > > > > +1 > > > > > > > > Thanks, > > > > Haiting > > > > > > > > On Tue, Aug 30, 2022 at 8:26 PM Enrico Olivelli > > > > > wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > > > > > > Enrico > > > > > > > > > > Il giorno mar 30 ago 2022 alle ore 13:24 lin chen > > > > > ha scritto: > > > > > > > > > > > > +1 > > > > > > > > > > > > Aloys Zhang 于2022年8月30日周二 19:02写道： > > > > > > > > > > > > > Hi devs, > > > > > > > > > > > > > > This is the VOTE thread for PIP-204 Extensions for > > > > BrokerInterceptor. > > > > > > > > > > > > > > PIP issue: https://github.com/apache/pulsar/issues/17267 > > > > > > > > > > > > > > Discussion thread: > > > > > > > > https://lists.apache.org/thread/3zgpbxffo7gzsb5mdh0sk2rq27bgw2bo > > > > > > > > > > > > > > This voting will open for at least 72h. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > Aloys > > > > > > > > > > > > > > > > > > > > > >
Re: [VOTE] PIP-205: Reactive Java client for Apache Pulsar
+1 (non-binding) Best, Max Xu On Wed, Aug 31, 2022 at 10:06 PM Lari Hotari wrote: > Hello, > > This is the official VOTE thread for PIP-205: Reactive Java client for > Apache Pulsar. > PIP link: https://github.com/apache/pulsar/issues/17335 > discussion: > https://lists.apache.org/thread/xkfl5px7qgt5rrxw5pj0g318r6mbdlz1 > > Given the proposal is accepted, as the next step I will proceed to request > the creation of the proposed empty git repository > https://github.com/apache/pulsar-client-reactive and open it for > contributions. > > This vote is open for 72h and closes Sep-03-2022 at 15:30 UTC. > > BR, Lari >
Re: [VOTE] PIP-200 Package Pulsar Trino distro and config in a dedicated folder
+1 (non-binding) Thanks tison for driving this work! Best, Max Xu On Wed, Aug 31, 2022 at 8:06 PM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il giorno mer 31 ago 2022 alle ore 13:47 PengHui Li > ha scritto: > > > > +1 (binding) > > > > Penghui > > > > On Mon, Aug 29, 2022 at 10:18 PM Nicolò Boschi > wrote: > > > > > +1 (non binding) > > > Thanks for taking care of this > > > > > > Nicolò Boschi > > > > > > > > > Il giorno lun 29 ago 2022 alle ore 15:26 tison > ha > > > scritto: > > > > > > > Hi devs, > > > > > > > > This is the official thread VOTE for PIP-200 Package Pulsar Trino > distro > > > > and config in a dedicated folder. > > > > > > > > Here is the PIP issue: https://github.com/apache/pulsar/issues/17137 > > > > Here is the discussion thread: > > > > https://lists.apache.org/thread/s985ypf0r0hzcm0mx653n5h2rt7n273v > > > > Here is the link to the draft PR: > > > > https://github.com/apache/pulsar/pull/17062 > > > > > > > > Voting will stay open for at least 72h. > > > > > > > > Best, > > > > tison. > > > > > > > >
Re: [DISCUSS] Use Github project to track the multi clients development
Reviewed and left a comment: the actions/add-to-project says itself does not support the Classic GitHub Project. [1] We may need to be aware of this. [1] https://github.com/actions/add-to-project#actionsadd-to-project Best, Max Xu On Thu, Aug 25, 2022 at 7:43 PM Zike Yang wrote: > > I think that the main problem is that in our community we have plenty > of Java developers and there are a few committers that review > the patches on non-Java client. > > Yes. The primary purpose of this project is to keep track of many > uncaught-up features of other languages clients. And there will be a > lot of features that we need to develop. > > If there is no objection, please help review and merge this PR: > https://github.com/apache/pulsar/pull/17201 Thanks. > > > Best, > Zike Yang > > On Wed, Aug 24, 2022 at 9:20 PM Enrico Olivelli > wrote: > > > > I think that the main problem is that in our community we have plenty > > of Java developers and there are a few committers that review > > the patches on non-Java client. > > The same problem is also for other projects like the Helm Chart. > > Also, the Java client is used internally by the broker so it is > > usually more used and it needs more work > > > > That said I agree that with the proposal in this thread > > > > Enrico > > > > Il giorno mer 24 ago 2022 alle ore 14:32 Qiang Huang > > ha scritto: > > > > > > It makes sense to me. I'm thinking, if an issue is encountered in a > Java > > > client, it is possible to be in other clients. If so, the Java client > board > > > is also needed. > > > > > > mattison chao 于2022年8月22日周一 16:00写道： > > > > > > > +1 > > > > > > > > Best, > > > > Mattison > > > > > > > > On Mon, 22 Aug 2022 at 15:52, Baodi Shi > > > > > wrote: > > > > > > > > > Nice idea! > > > > > > > > > > Thanks, > > > > > Baodi Shi > > > > > > > > > > > On Aug 22, 2022, at 12:4250, Zike Yang wrote: > > > > > > > > > > > > Hi, all > > > > > > > > > > > > Currently, many features or bug fixes of some clients like the > C++ > > > > > > client and Python client have not caught up with the Java > client. For > > > > > > better tracking of these features or bug fixes, I have created a > > > > > > Github project called `Apache Pulsar / Multi Clients`[0] under > the > > > > > > pulsar main repo. It can be removed if we don't like it this way. > > > > > > > > > > > > There are six columns in this Github project: > > > > > > * Backlog: Low priority issues or issues(or cards) that have not > been > > > > > > initially investigated. > > > > > > * Todo: Newly added issues and issues suitable for contributors > to pick > > > > > first. > > > > > > * In progress: Work in progress issues or PRs. > > > > > > * Review in progress: The PRs or issues that are waiting for > review. > > > > > > * Reviewer approved: The PRs or issues that are waiting to merge. > > > > > > * Done: Merged PRs and Solved issues. > > > > > > > > > > > > This not only helps to track the status of other clients' > features and > > > > > > bug fixes but also helps contributors who want to participate in > other > > > > > > language client feature development to pick the task. > > > > > > > > > > > > This Project is currently only for clients maintained by the main > > > > > > pulsar repository, such as C++ and Python clients. > > > > > > > > > > > > I have created a PR [1] to add C++ and Python client issues and > PRs to > > > > > > the Multi Clients project. > > > > > > > > > > > > Please let me know what you think. Thanks! > > > > > > > > > > > > [0] https://github.com/apache/pulsar/projects/12 > > > > > > [1] https://github.com/apache/pulsar/pull/17201 > > > > > > > > > > > > Best, > > > > > > Zike Yang > > > > > > > > > > > > > > > > > > > > > > > -- > > > BR, > > > Qiang Huang >
Re: Pulsar CI congested, master branch build broken
And +1 vote for "Provide information about GitHub Actions usage for apache organization", which would be greatly helpful by making these information transparency. Best, Max Xu On Fri, Aug 26, 2022 at 8:00 PM Lari Hotari wrote: > Hi, > > GitHub Actions builds have been piling up in the build queue in the last > few days. > I posted on bui...@apache.org > https://lists.apache.org/thread/6lbqr0f6mqt9s8ggollp5kj2nv7rlo9s and > created INFRA ticket https://issues.apache.org/jira/browse/INFRA-23633 > about this issue. > There's also a thread on the-asf slack, > https://the-asf.slack.com/archives/CBX4TSBQ8/p1661512133913279 . > > It seems that our build queue is finally getting picked up, but it would > be great to see if we hit quota and whether that is the cause of pauses. > > Another issue is that the master branch broke after merging 2 conflicting > PRs. > The fix is in https://github.com/apache/pulsar/pull/17300 . > > Merging PRs will be slow until we have these 2 problems solved and > existing PRs rebased over the changes. Let's prioritize merging #17300 > before pushing more changes. > > I'd like to point out that a good way to get build feedback before sending > a PR, is to run builds on your personal GitHub Actions CI. The benefit of > this is that it doesn't consume the shared quota and builds usually start > instantly. > There are instructions in the contributors guide about this. > https://pulsar.apache.org/contributing/#ci-testing-in-your-fork > You simply open PRs to your own fork of apache/pulsar to run builds on > your personal GitHub Actions CI. > > BR, > > Lari > > > > > > > >
Re: Pulsar CI congested, master branch build broken
Hi, Lari Thanks for bringing this to our attention! I was wondering if we could consider using the self-hosted runner? As there are currently more than 2k projects in one apache org. Best, Max Xu On Fri, Aug 26, 2022 at 8:00 PM Lari Hotari wrote: > Hi, > > GitHub Actions builds have been piling up in the build queue in the last > few days. > I posted on bui...@apache.org > https://lists.apache.org/thread/6lbqr0f6mqt9s8ggollp5kj2nv7rlo9s and > created INFRA ticket https://issues.apache.org/jira/browse/INFRA-23633 > about this issue. > There's also a thread on the-asf slack, > https://the-asf.slack.com/archives/CBX4TSBQ8/p1661512133913279 . > > It seems that our build queue is finally getting picked up, but it would > be great to see if we hit quota and whether that is the cause of pauses. > > Another issue is that the master branch broke after merging 2 conflicting > PRs. > The fix is in https://github.com/apache/pulsar/pull/17300 . > > Merging PRs will be slow until we have these 2 problems solved and > existing PRs rebased over the changes. Let's prioritize merging #17300 > before pushing more changes. > > I'd like to point out that a good way to get build feedback before sending > a PR, is to run builds on your personal GitHub Actions CI. The benefit of > this is that it doesn't consume the shared quota and builds usually start > instantly. > There are instructions in the contributors guide about this. > https://pulsar.apache.org/contributing/#ci-testing-in-your-fork > You simply open PRs to your own fork of apache/pulsar to run builds on > your personal GitHub Actions CI. > > BR, > > Lari > > > > > > > >
Re: [VOTE] [PIP-201] Extensions mechanism for Pulsar Admin CLI tools
+1 (non-binding) It's a cool idea! Best, Max Xu On Wed, Aug 24, 2022 at 9:46 PM PengHui Li wrote: > +1 (binding) > > Best, > Penghui > > On Wed, Aug 24, 2022 at 9:39 PM Dave Fisher wrote: > > > +1 (binding) > > > > Best, > > Dave > > > > Sent from my iPhone > > > > > On Aug 24, 2022, at 12:43 AM, Yunze Xu > > wrote: > > > > > > +1 (non binding) > > > > > > Thanks, > > > Yunze > > > > > > > > > > > > > > >> 2022年8月24日 15:38，Nicolò Boschi 写道： > > >> > > >> +1 (non binding) > > >> Nicolò Boschi > > >> > > >> > > >>> Il giorno mer 24 ago 2022 alle ore 09:11 Enrico Olivelli < > > >>> eolive...@gmail.com> ha scritto: > > >>> > > >>> Hello, > > >>> this is the official thread VOTE for PIP-201 Extensions mechanism for > > >>> Pulsar Admin CLI tools > > >>> > > >>> This is the PIP link https://github.com/apache/pulsar/issues/17155 > > >>> This is the discussion: > > >>> https://lists.apache.org/thread/287ft8twc11cp4s1y4qkcx5nmh451cyo > > >>> > > >>> I am still working on the PR, that is the subject of the VOTE. > > >>> > > >>> Best regards > > >>> Enrico Olivelli > > >>> > > > > > > > >
Re: [Discussion] PIP 198 - How to define [type] and [scope]?
LGTM. And I think we should also update our issue templates. Best, Max Xu On Tue, Aug 23, 2022 at 6:04 PM Yu wrote: > Hi team, > > Many thanks for your feedback! We've adjusted the convention based on your > suggestions! > > Below is a brief summary of what we have reached a consensus on: > > > > 1. Convention > > Continue to follow our existing convention (it's customized on Agular) [1] > > > > 2. Definition > > [type] must be one of the following: > - feat (abbr for "feature") > - improve > - fix > - cleanup > - refactor > - revert > > [scope] must be one of the following: > - admin > - broker > - cli (changes to CLI tools) > - io > - fn (abbr for "function") > - meta (abbr for "metadata") > - monitor > - proxy > - schema > - sec (abbr for "security") > - sql > - storage > - offload (changes to tiered storage) > - txn > - java > - cpp > - py > - ws (changes to WebSocket) > - test (changes to code tests) > - ci (changes to CI workflow) > - build (changes to dependencies, docker, build or release script) > - misc > - doc > - blog > - site > > For full details, see [Guide] Pulsar Pull Request Naming Convention [2] > > > > If you have any concerns, feel free to comment before 13:00 August 25 (UTC > +8). > > We'll start implementing it if there is no objection after that time. > > Thank you! > > > > [1] https://lists.apache.org/thread/90rcjf1dv0fbkb5hm31kmgr65fj0nfnn > [2] > > https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno > > Yu and mangoGoForward > > On Tue, Aug 23, 2022 at 5:59 PM Yu wrote: > > > Hi Jiuming, Yunze, tison, > > Thanks for your vote! > > > > > > > > Hi tison, > > > > > "packaging logics" > > > For example, build the docker image, build & publish shell scripts. > > > > If you refer to these changes, they belong to [build] scope. > > > > Yu and Zixuan > > > > On Tue, Aug 23, 2022 at 1:25 PM tison wrote: > > > >> Hi Yu, > >> > >> Reply inline: > >> > >> > Besides, the existing scope, [tool], refers to Pulsar CLI tools [1]. > >> > We're considering to rename it to [cli] since: > >> > >> Make sense. > >> > >> > "deployment logic" If so, can we ignore this? > >> > >> I saw you already remove [deploy] scope. No comment here. It should be > >> fine. > >> > >> > "packaging logics" > >> > >> For example, build the docker image, build & publish shell scripts. > >> > >> > How about defining [build] refer to the following? > >> > >> Make sense. > >> > >> > Two quick questions need your vote! > >> > >> To save letters, B & A. > >> > >> Best, > >> tison. > >> > > >
Re: [ANNOUNCE] Jiwei Guo as a new PMC member in Pulsar
Congratulations! Jiwei Best, Max Xu On Thu, Aug 18, 2022 at 7:24 PM PengHui Li wrote: > Hi, all > > I'm glad to announce that the Apache Pulsar PMC invited Jiwei Guo to join > the > PMC and he accepted. > > Please join in celebrating! > > Best, > Penghui >
Re: [DISCUSS] Create a new Github Project to track the flaky tests
+1 It would be awesome to utilize the GitHub Project to track issues. BTW, seems this is a Classic Project[2], and the New Project[1] can provide more features than the Classic Project[2]. [1] https://github.com/apache/pulsar/projects?type=new [2] https://github.com/apache/pulsar/projects?type=classic Best, Max Xu On Thu, Aug 11, 2022 at 11:26 AM Zixuan Liu wrote: > +1 > > Thanks, > Zixuan > > Anon Hxy 于2022年8月11日周四 10:26写道： > > > +1 > > Good idea. We are on the way making CI more robust > > > > Thanks, > > Xiaoyu Hou > > > > PengHui Li 于2022年8月10日周三 16:35写道： > > > > > Hi all, > > > > > > For better tracking flaky test fix, I have tried to create a Github > > > Project under the Pulsar repo > > https://github.com/apache/pulsar/projects/11 > > > (It can be removed if we don't like this way) > > > This will help us to have a more intuitive view of all the flaky tests, > > > how many are in progress, in the review stage, and approved. > > > > > > The project is public for all the contributors, so if you want > > > to contribute some flaky tests fixes, > > > you can go to the Github Project to peek up items in the Todo column. > > > > > > And I also created a PR https://github.com/apache/pulsar/pull/17038 to > > > add the PRs and issues > > > with `flaky-tests` label to this project automatically. > > > > > > BTW, I also have some questions about the Github Project automation. As > > > the description of > > > column `Review in progress, it said the PR with request changes would > go > > > to this column > > > automatically. But it doesn't work. I'm not sure why. > > > [image: image.png] > > > > > > Best, > > > Penghui > > > > > > > > >
Re: [VOTE] PIP-190: Simplify Pulsar documentation release and maintenance strategy
+1 Best, Max Xu On Thu, Jul 28, 2022 at 9:35 AM Yu wrote: > +1 since it improves the efficiency of managing docs. > > On Thu, Jul 28, 2022 at 8:16 AM M Jun wrote: > > > Hi, Pulsar community, > > > > I'd like to start a vote on PIP-190: Simplify Pulsar documentation > release > > and maintenance strategy. > > > > You can find the proposal at > https://github.com/apache/pulsar/issues/16637 > > and the discussion thread at > > https://lists.apache.org/thread/g5b8lcwtn10ox7vd67n31om9w1rxn4l7. > > > > The vote will stay open for at least 48 hours. > > > > > > Cheers, > > momo-jun > > >
Re: [Discuss] PIP-190: Simplify Pulsar documentation release and maintenance strategy
+1 Documentation will definitely benefit from it. Best, Max Xu On Wed, Jul 27, 2022 at 12:19 PM Huanli Meng wrote: > +1 as it may save a lot of effort and time for both the release manager > and TWs. > > BR//Huanli > > > On Jul 27, 2022, at 11:33 AM, Liu Yu wrote: > > > > +1 for this proposal since it improves the efficiency of managing docs. > > > > We'll take it as we reach a lazy consensus and implement this plan if > there is no objection until tomorrow. > > > > On 2022/07/25 09:13:50 M Jun wrote: > >> Hi Asaf, > >> > >> The doc files for all older versions are independent copies, stored at > https://github.com/apache/pulsar/tree/master/site2/website/versioned_docs. > >> > >> For example, the doc for 2.10.0 was a copy saved from the next (master) > doc at that milestone. > >> > >> 发件人: Asaf Mesika > >> 发送时间: 2022年7月24日 21:00 > >> 收件人: dev@pulsar.apache.org > >> 主题: Re: [Discuss] PIP-190: Simplify Pulsar documentation release and > maintenance strategy > >> > >> If I understand correctly, using tags, you can automatically create the > >> docs for the next minor version? > >> So for older minor versions, where those files will be at? using tags > from > >> git? > >> > >> On Sat, Jul 23, 2022 at 7:04 AM Ma Jun wrote: > >> > >>> Hi, Pulsar community, > >>> > >>> Happy weekend! > >>> > >>> I'd like to open a discussion about PIP-190: Simplify Pulsar > documentation > >>> release and maintenance strategy. > >>> > >>> Proposal link: https://github.com/apache/pulsar/issues/16637. > >>> > >>> > >>> > - > >>> > >>> ## Motivation > >>> > >>> This proposal is focused on improving and simplifying the release and > >>> maintenance strategy of the existing Apache Pulsar documentation. > >>> > >>> In general, this proposal provides equal values and a better user > >>> experience without sacrificing unpredictable efforts in the release and > >>> maintenance process. The benefits include: > >>> * Improve user experience when they look for the documentation of a > >>> specific release. > >>> * Optimize the doc development and release process for bug-fix > releases: > >>> * Turn doc development for bug-fix releases from post-release into > >>> just-in-time. > >>> * Save Release Manager’s effort in generating doc files for bug-fix > >>> releases. > >>> * Save a great amount of the community’s effort in syncing doc > >>> improvements and fixes to historical doc versions that are in the > >>> maintenance cycle. > >>> > >>> > >>> Since there are quite a few illustrations and links in this proposal, I > >>> didn't copy and paste the complete content into this email thread. You > can > >>> access the GitHub link to review the proposal with a better view. > >>> > >>> > >>> Cheers! > >>> > >>> momo-jun > >>> > >>> > >> > >
Re: [ANNOUNCE] Micheal Marshall as a new PMC member in Pulsar
Congratulations, Michael ! Best, Max Xu On Wed, Jul 27, 2022 at 2:04 PM Kai Wang wrote: > Congratulations Michael! > > Thanks, > Kai >
Re: [VOTE] Enable GitHub Discussion for user-facing discussion
+1 Best, Max Xu On Thu, Jul 14, 2022 at 10:17 AM Michael Marshall wrote: > +1 > > - Michael > > On Wed, Jul 13, 2022 at 11:05 AM Zixuan Liu wrote: > > > > +1 > > > > Zixuan > > > > PengHui Li 于2022年7月13日周三 23:58写道： > > > > > +1 > > > > > > Penghui > > > > > > On Wed, Jul 13, 2022 at 11:44 PM Anon Hxy wrote: > > > > > > > +1 > > > > > > > > tison 于2022年7月12日周二 18:01写道： > > > > > > > > > Hi, > > > > > > > > > > In the previous email[1] I started a discussion about enabling > GitHub > > > > > Discussions in apache/pulsar repository and we meet a consensus to > > > avoid > > > > > making development discussions truth happen on the sources. It's > also a > > > > > requirement of INFRA team[2] > > > > > > > > > > Apart of it, for user-facing discussions it's conventions for > Pulsar > > > > users > > > > > who have a GitHub account but are unfamiliar with mailing list to > throw > > > > > their use case and questions on GitHub discussion. > > > > > > > > > > Dave has opened and issue[2][3] and prepare the patch[4] for > turning on > > > > the > > > > > discussion option but obviously we still need an explicit consensus > > > among > > > > > the community and it's also required before INFRA team takes > action. > > > > > > > > > > I'd like to start this voting thread for "Enable GitHub Discussion > for > > > > > user-facing discussion", please reply with your opinion: > > > > > > > > > > [ ] +1 approve > > > > > [ ] +0 no opinion > > > > > [ ] -1 disapprove (and reason why) > > > > > > > > > > Best, > > > > > tison. > > > > > > > > > > [1] > https://lists.apache.org/thread/1y7zbchlbokwnpd0jv2tt5jtzg6px6yn > > > > > [2] https://issues.apache.org/jira/browse/INFRA-23477 > > > > > [3] https://github.com/apache/pulsar/issues/16275 > > > > > [4] https://github.com/apache/pulsar/pull/16528 > > > > > > > > > > > > >
Re: [DISCUSS] PIP-181: Pulsar Shell
Hi Nicolò, This is definitely a very awesome job, thank you for bringing Pulsar Shell to us! Also, I was wondering if we could integrate the pulsar shell entrypoint directly into the existing pulsar command[1]? (i.e, invoke ./bin/pulsar shell) So that we can reuse the current CLI instead of adding a new CLI into the bin folder. *Best,* *Max Xu* [1] https://github.com/apache/pulsar/blob/master/bin/pulsar On Mon, Jul 11, 2022 at 6:24 PM Nicolò Boschi wrote: > Hi Asaf, > > Actually it's in the "Future works" of the PIP. > > I already implemented a PoC of it and you can see it here: > > https://github.com/nicoloboschi/pulsar/commit/f227be324c96daeaf89566260a63eb558357f34f > There are still some issues with some runtime config since GraalVM requires > to declare most of the reflection accesses you will do at runtime. And > Pulsar does a lot of reflections. > > Anyway, I don't think it is a different direction but instead a future > optimization and we should push to have it after the base Pulsar shell is > fully committed to the master branch. > > BR, > Nicolò Boschi > > > Il giorno lun 11 lug 2022 alle ore 12:18 tison ha > scritto: > > > Hi Asaf, > > > > Why not compile the related package with graal and submit a report on the > > master issue[1] :) > > > > AFAIK Pulsar didn't optimize for graal compilation so that you MAY meet > > some issues, and pulsar-shell actually depends on other core module so > that > > it's not an orphan issue to resolve. > > > > Best, > > tison. > > > > [1] https://github.com/apache/pulsar/issues/16250 > > > > > > Asaf Mesika 于2022年7月11日周一 18:05写道： > > > > > Looks awesome. > > > I was wondering if you have thought about another direction which is > > > supplying a GraalVM compiled binary. This should take care of load > time. > > So > > > in effect, you can have a single command, which boots in microseconds, > > and > > > has shell auto-complete? > > > > > > On Mon, Jul 4, 2022 at 4:34 PM Hang Chen wrote: > > > > > > > +1 Great work! > > > > > > > > Thanks, > > > > Hang > > > > > > > > PengHui Li 于2022年7月4日周一 19:36写道： > > > > > > > > > > + 1 > > > > > > > > > > Penghui > > > > > On Jul 4, 2022, 18:22 +0800, Dezhi Liu , > wrote: > > > > > > +1, Great Job. > > > > > > > > > > > > Thanks, > > > > > > Dezhi > > > > > > > > > > > > On 2022/06/28 08:06:01 Nicolò Boschi wrote: > > > > > > > Hi all, > > > > > > > > > > > > > > I opened a new PIP about Pulsar CLI tools. > > > > > > > Looking forward to seeing comments and suggestions. > > > > > > > > > > > > > > PIP: https://github.com/apache/pulsar/issues/16250 > > > > > > > > > > > > > > I posted a short video that shows how the new tool will work: > > > > > > > > > > > > > > > > > https://user-images.githubusercontent.com/23314389/176125261-35e123a1-1826-4553-b912-28d00914c0e4.mp4 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ## Motivation > > > > > > > > > > > > > > Currently Pulsar comes with a couple of utility scripts with > the > > > > goal of > > > > > > > managing an existing cluster, test behaviours and verify > > > > performances: > > > > > > > these tools are available as SH script inside the `bin` > > directory. > > > > > > > The `pulsar-admin` is the CLI tool supposed to help users and > > > > operators to > > > > > > > configure the system, operate over policies, install functions > > and > > > > much > > > > > > > else. > > > > > > > > > > > > > > This proposal basically aims to solve two different problems: > > > > > > > > > > > > > > 1. `pulsar-admin` is terribly slow. Every time the script is > > > > triggered, a > > > > > > > new JVM process is spawned. The JVM process creation is heavy > and > > > > most of > > > > > > > the time is spent by the JVM initialization process. A very >
Re: [ANNOUNCE] New Committer: Zixuan Liu
Congratulations! Zixuan Best Max Xu On Thu, Jul 7, 2022 at 8:55 PM Nicolò Boschi wrote: > Congrats! > > Nicolò Boschi > > > Il giorno gio 7 lug 2022 alle ore 13:28 Haiting Jiang < > jianghait...@apache.org> ha scritto: > > > Congratulates, Zixuan! > > > > BR, > > Haiting > > > > On 2022/07/07 10:03:36 Yu wrote: > > > Hi team, > > > > > > The Project Management Committee (PMC) for Apache Pulsar has invited > > > Zixuan Liu (https://github.com/nodece) to become a committer > > > and we are pleased to announce that he has accepted. > > > > > > Being a committer enables easier contribution to the > > > project since there is no need to go via the patch > > > submission process. This should enable better productivity. > > > > > > Welcome and congratulations, Zixuan Liu! > > > > > > Please join us in congratulating and welcoming Zixuan Liu onboard! > > > > > > Best Regards, > > > Yu on behalf of the Pulsar PMC > > > > > >
Re: [VOTE] Pulsar Manager Release 0.3.0 Candidate 3
+1 (non-binding) - Validate checksum - Start pulsar-manager - Create an environment (add a pulsar instance) - Create and delete tenants/namespaces/topics. But unable to create token Thanks, Max Xu On Wed, May 18, 2022 at 6:58 PM Hang Chen wrote: > +1(binding) > - Validate checksum > - Deploy pulsar-manager service and add pulsar cluster > - Create tenants, namespace and topics, delete topics. > > Thanks, > Hang > > Guangning E 于2022年5月12日周四 20:39写道： > > > > +1(non-binding) > > Validate checksum > > Start pulsar-manager service > > Create tenant and topic > > > > Thanks, > > Guangning > > > > Li Li 于2022年5月10日周二 14:14写道： > > > > > Hi everyone, > > > Please review and vote on the release candidate #3 for the version > 0.3.0, > > > as follows: > > > [ ] +1, Approve the release > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > The complete staging area is available for your review, which includes: > > > * Release notes [1] > > > * The official Apache source and binary distributions to be deployed to > > > dist.apache.org <http://dist.apache.org/> [2] > > > * Source code tag "v0.3.0-candidate-3" [4] with git sha > > > > 951095a71f7471dca028da0a330bc1a5e0707333a61fa4a09c8ea0f0a144d5628b511487e2442ebe290b9642b6b8ca7dee486a18a8339c893c37253724ad5fd4 > > > apache-pulsar-manager-0.3.0-src.tar.gz > > > > > > PulsarManager's KEYS file contains PGP keys we used to sign this > release: > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS < > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS> > > > > > > Please download these packages and review this release candidate: > > > > > > - Review release notes > > > - Download the source package (verify shasum, and asc) and follow the > > > instructions to build and run the pulsar-manager front end and back end > > > service. > > > - Download the binary package (verify shasum, and asc) and follow the > > > instructions to run run the pulsar-manager front end and back end > service. > > > > > > The vote will be open for at least 72 hours. It is adopted by majority > > > approval, with at least 3 PMC affirmative votes. > > > > > > > > > Source and binary files: > > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz > > > < > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz > > > < > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz > > > > > > > > > > SHA-512 checksums: > > > > > > > 6ffa5921765ee94a404792e98eb4b3cbda9e016c6661ef12e4e873e7e452301bc05650709955b012d08048e418133948a628ad55bc91ac65836022e1ea426d6f > > > apache-pulsar-manager-0.3.0-bin.tar.gz > > > > 951095a71f7471dca028da0a330bc1a5e0707333a61fa4a09c8ea0f0a144d5628b511487e2442ebe290b9642b6b8ca7dee486a18a8339c893c37253724ad5fd4 > > > apache-pulsar-manager-0.3.0-src.tar.gz > > > > > > > > > > > > >
Re: New Pulsar Website is Live!
This new website looks awesome, love it! Thank you! Max Xu On Thu, May 12, 2022 at 1:24 AM Aaron Williams wrote: > Looks great! Thank you > > > On Wed, May 11, 2022 at 10:19 AM Chris Latimer > wrote: > > > It looks really good, thank you to everyone who worked on this! > > > > On Wed, May 11, 2022 at 1:31 AM Liu Yu wrote: > > > > > Hi everyone, > > > > > > As you may notice, the new Pulsar website goes live! [1] > > > > > > We hope you enjoy the new content and the fresh appearance! > > > > > > Do not hesitate to leave your comment here [2] if you have any > > suggestions > > > or concerns, thanks! > > > > > > [1] https://pulsar.apache.org/ > > > [2] https://github.com/apache/pulsar/issues/15538 > > > > > > Yu and Lili > > > > > > On 2022/05/10 02:43:12 Yu wrote: > > > > Hi everyone, > > > > > > > > The New Pulsar Website (beta) has been running for more than 3 > months. > > > > We've optimized the website based on the feedback from the New Pulsar > > > > Website Survey [1]. > > > > > > > > Now everything goes fine except few known issues: > > > > - Search function may not work very well > > > > - Some pages are not completely translated > > > > > > > > However, they do not block the switchover, and we're continually > > > improving > > > > them all the time. > > > > > > > > Consequently, we plan to launch the New Pulsar Website on May 11, > > > Wednesday > > > > (UTC+8). > > > > > > > > Feel free to comment if you have any suggestions or concerns on the > > > > switchover, thanks! > > > > > > > > [1] https://lists.apache.org/thread/xjccxbozlw7jqlldm2dw0yc74cydknvd > > > > > > > > Yu and Lili > > > > > > > > > >
Re: [ANNOUNCE] new Committer Qiang Zhao (mattisonchao)
Congratulations! Qiang Thanks, Max Xu On Thu, May 5, 2022 at 9:19 AM Hang Chen wrote: > Congrats Qiang! > > Thanks, > Hang > > Baozi 于2022年5月5日周四 08:59写道： > > > > Congrats ! > > > > Thanks, > > Baozi > > > > > 2022年5月5日 08:4032，PengHui Li 写道： > > > > > > Congrats > > >
