[GitHub] [pulsar-helm-chart] tisonkun commented on pull request #292: replace handmade release script with official action

2022-10-08 Thread GitBox
tisonkun commented on PR #292: URL: https://github.com/apache/pulsar-helm-chart/pull/292#issuecomment-1272464800 cc @michaeljmarshall @ericsyh @mattisonchao @yaalsn -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [pulsar-helm-chart] tisonkun commented on a diff in pull request #292: replace handmade release script with official action

2022-10-08 Thread GitBox
tisonkun commented on code in PR #292: URL: https://github.com/apache/pulsar-helm-chart/pull/292#discussion_r990736904 ## .github/workflows/lint.yml: ## @@ -43,9 +42,22 @@ jobs: id: check_changes run: echo "::set-output name=docs_only::${{ fromJSON(steps.chang

[GitHub] [pulsar-helm-chart] tisonkun commented on a diff in pull request #292: replace handmade release script with official action

2022-10-08 Thread GitBox
tisonkun commented on code in PR #292: URL: https://github.com/apache/pulsar-helm-chart/pull/292#discussion_r990735145 ## .github/workflows/release.yml: ## @@ -17,39 +17,36 @@ # under the License. # -name: Post commit - Publish Pulsar Helm Chart +name: Release Pulsar Helm Ch

[GitHub] [pulsar-helm-chart] tisonkun opened a new pull request, #292: replace handmade release script with official action

2022-10-08 Thread GitBox
tisonkun opened a new pull request, #292: URL: https://github.com/apache/pulsar-helm-chart/pull/292 This refers to #290. The `helm/chart-releaser-action` update `index.yaml` in an incremental manner, so we need to push the existing `index.yaml` file to `gh-pages` later. -- This is

[GitHub] [pulsar-helm-chart] tisonkun commented on issue #290: Release Pulsar Helm Chart in GitHub Pages flavor

2022-10-08 Thread GitBox
tisonkun commented on issue #290: URL: https://github.com/apache/pulsar-helm-chart/issues/290#issuecomment-1272455470 I'm going to submit a pull request to this repo. And it still needs a committer to help create the `gh-pages` branch (identical to master is OK for initialization). -- T

Re: [DISCUSS] Add an auth data const for refresh the original auth data

2022-10-08 Thread Zixuan Liu
See https://github.com/apache/pulsar/issues/17517. Asaf Mesika 于2022年10月3日周一 19:47写道: > I kind of lost you here Zixuan. > > Is there any chance you describe the authentication flow including the > commands? Then specify the change you wish to make? > > > On Thu, Aug 18, 2022 at 5:21 AM Zixuan Li

[ANNOUNCE] Apache Pulsar Go Client v0.9.0 released

2022-10-08 Thread r...@apache.org
The Apache Pulsar team is proud to announce Apache Pulsar Go Client version v0.9.0. 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

Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2

2022-10-08 Thread r...@apache.org
The vote is now closed and the release was approved with 8 +1s(3 bindings and 6 non-binding); Binding votes: * Penghui Li * Hang Chen * Jiwei Guo Non-Binding votes: * Xiaolong Ran * Guangning E * Zike Yang * Qiang Huang * Rui Fu * Max Xu Thank you all guys for voting! Max Xu 于2022年10月8日周六 16:3

Re: [DISCUSS] Planning for Apache Pulsar 3.0

2022-10-08 Thread Rajan Dhabalia
I would say first we should gather a list of changes which we want to target and find out which improvements really need major version release. We can take the Pulsar-1.0 to Pulsar-2.0 upgrade example to avoid major interruption and impact on existing systems and still achieve our goal. So, the fir

Re: [DISCUSS] Planning for Apache Pulsar 3.0

2022-10-08 Thread Devin Bost
I'm noticing some pushback on the idea of pre-emptively proposing any kind of breaking upgrade that would necessitate cutting a 3.0 release. I do understand the concern about introducing a breaking change... For a distributed messaging application like Pulsar, if clients needed to be simultaneously

Re: [DISCUSS] Planning for Apache Pulsar 3.0

2022-10-08 Thread Rajan Dhabalia
This sounds like the current state of Apache Pulsar has a lot of issues and it requires fundamental design changes to make it promising which is definitely not true and I disagree with it. And I would be careful comparing with Kafka as I still don't think the Kafka release has anything to do with P

Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2

2022-10-08 Thread Max Xu
+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, Ap

Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2

2022-10-08 Thread Rui Fu
+1 (non-binding) - Verify sha-512 checksum - Build from the source - Run tests - Run producer and consumer Best, Rui Fu 在 2022年10月8日 +0800 11:50,Qiang Huang ,写道: > +1 (non-binding) > - Build from the source code > - Run producer and consumer > > guo jiwei 于2022年10月8日周六 11:27写道: > > > +1 (binding

Re: [DISCUSS] Release Pulsar Client C++ 3.0.0

2022-10-08 Thread Haiting Jiang
+1 This is GREAT for simplifying the release process. Thanks, Haiting On Sat, Oct 8, 2022 at 10:44 AM Dave Fisher wrote: > > Hi Matteo, > > Thank you for this critical work pulling the C++ (and Python) clients out of > the main repository and into separate repositories and release cycles! I >

Re: [VOTE] Pulsar Release 2.10.2 Candidate 2

2022-10-08 Thread Haiting Jiang
Hi Xiaoyu, > The fixed PR is here: > https://github.com/apache/pulsar/pull/17948 > > This should be a release blocker I think. Great catch, Thank you! The publish throughput is down by almost half with default setup, this is definitely a release blocker. Thanks, Haiting On Sat, Oct 8, 2022 at 1