Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

Enrico, There are 40 closed PRs https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.9.3+is%3Aclosed and most of them cherry-picked to branch-2.9, so you mean the 2.9.2 contains all of them? or just contain https://github.com/apache/pulsar/pull/14192 ? I have no objection if we rol

[DISCUSS] Release Pulsar 2.7.5

Hello Pulsar Community, We have had several important fixes since we released 2.7.4 on Dec 27, 2021. I propose we start the process to release 2.7.5, and I volunteer to be the release manager. Here [0] you can find the list of 11 commits to branch-2.7 since the 2.7.4 release. There are 3 closed P

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

Gao, The patch https://github.com/apache/pulsar/pull/14192 has been merged. I believe that is better to roll out a new RC and have Pulsar 2.9.2 released Thanks for the good discussion Enrico Il giorno gio 10 feb 2022 alle ore 05:11 PengHui Li ha scritto: > > It should not be a blocking issue,

Re: [DISCUSS] Releasing Pulsar-client-go 0.8.0

+1 -Lari to 10. helmik. 2022 klo 4.44 r...@apache.org kirjoitti: > Hello Everyone: > > > I hope you’ve all been doing well. In the past two months, we have > > fixed a number of bugs related to connection leaks and added > > some new features. For more information refer to: > > > https://github

Re: [ANNOUNCE] New Committer: Aloys Zhang

Congratulations, Aloys Zhang Thanks, Penghui On Thu, Feb 10, 2022 at 11:19 AM ZhangJian He wrote: > Congratulations, Aloys Zhang! > > Thanks > ZhangJian He > > r...@apache.org 于2022年2月10日周四 11:16写道： > > > Congratulations, Aloys Zhang! > > > > -- > > Thanks > > Xiaolong Ran > > > > linlin 于20

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

It should not be a blocking issue, as I mentioned before we can work around and the issue happens for specific conditions And there are some other ongoing transaction fixes, for transactions using the latest branch-2.9 is the best option, not 2.9.2 even contain https://github.com/apache/pulsar/pull

Re: [DISCUSS] Release Pulsar 2.8.3

+1 Thank you! - Penghui On Thu, Feb 10, 2022 at 3:18 AM Lari Hotari wrote: > +1 > Thank you, Michael, for volunteering to be the release manager for 2.8.3. > > -Lari > > On Wed, Feb 9, 2022 at 8:16 PM Michael Marshall > wrote: > > > Hello Pulsar Community, > > > > We have had several importan

Re: [ANNOUNCE] New Committer: Aloys Zhang

Congratulations, Aloys Zhang! Thanks ZhangJian He r...@apache.org 于2022年2月10日周四 11:16写道： > Congratulations, Aloys Zhang! > > -- > Thanks > Xiaolong Ran > > linlin 于2022年2月10日周四 10:46写道： > > > The Apache Pulsar Project Management Committee (PMC) has invited Aloys > > Zhang > > > > (https://gith

Re: [ANNOUNCE] New Committer: Aloys Zhang

Congratulations, Aloys Zhang! -- Thanks Xiaolong Ran linlin 于2022年2月10日周四 10:46写道： > The Apache Pulsar Project Management Committee (PMC) has invited Aloys > Zhang > > (https://github.com/aloyszhang) to become a committer and we are pleased > to > > announce that he has accepted. > > Aloys Zhan

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

My personal opinion: If this is a blocking issue, we should tag the issue and raise it in the discussion stage, not in the final release stage, which will waste a lot of time of the release manager. But I see this issue is already closed. https://github.com/apache/pulsar/pull/14097 We can eva

Re: [DISCUSS] Releasing Pulsar-client-go 0.8.0

+1 -- Matteo Merli On Wed, Feb 9, 2022 at 6:44 PM r...@apache.org wrote: > > Hello Everyone: > > > I hope you’ve all been doing well. In the past two months, we have > > fixed a number of bugs related to connection leaks and added > > some new features. For more information refer to: > > > htt

[ANNOUNCE] New Committer: Aloys Zhang

The Apache Pulsar Project Management Committee (PMC) has invited Aloys Zhang (https://github.com/aloyszhang) to become a committer and we are pleased to announce that he has accepted. Aloys Zhang joined the Pulsar community in June 2020 and contributed a lot of commits to the community, includin

[DISCUSS] Releasing Pulsar-client-go 0.8.0

Hello Everyone: I hope you’ve all been doing well. In the past two months, we have fixed a number of bugs related to connection leaks and added some new features. For more information refer to: https://github.com/apache/pulsar-client-go/milestone/9

[GitHub] [pulsar-manager] xuesongxs opened a new pull request #444: Simplified classpath

xuesongxs opened a new pull request #444: URL: https://github.com/apache/pulsar-manager/pull/444 Fixes #443 for example:  -- This is an automated message from the

[GitHub] [pulsar-manager] xuesongxs opened a new issue #443: Simplify the classpath in the bin/pulsar-manager script

xuesongxs opened a new issue #443: URL: https://github.com/apache/pulsar-manager/issues/443 The classpath in the original bin / pulsar manager script is realized by splicing jar packages, which leads to the command of PS process is too long, so it needs to be simplified. ![image](https

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

> given the fact that Transactions are not something that you can use in production in 2.9 Yes, for transactions, it's better to use the latest branch-2.9, not 2.9.1 or 2.9.2. > If it is a matter of fixing the problem reported by Nicolò, then we should fix it and let people try out transactions.

Re: [DISCUSS] Release Pulsar 2.8.3

+1 Thank you, Michael, for volunteering to be the release manager for 2.8.3. -Lari On Wed, Feb 9, 2022 at 8:16 PM Michael Marshall wrote: > Hello Pulsar Community, > > We have had several important fixes since we released 2.8.2 a month > ago. I propose we start the process to release 2.8.3, and

[DISCUSS] Release Pulsar 2.8.3

Hello Pulsar Community, We have had several important fixes since we released 2.8.2 a month ago. I propose we start the process to release 2.8.3, and I volunteer to be the release manager. Here [0] you can find the list of 90 commits to branch-2.8 since the 2.8.2 release. There are 14 closed PRs

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

Peng Hui, given the fact that Transactions are not something that you can use in production in 2.9, then we could move forward with this release. But this would be a real pity, because we are stating that users should not use transactions because they are not stable. If it is a matter of fixing t

Re: [DISCUSS] Apache Pulsar 2.10.0 release

Yes, I agree, it's a good idea. But it depends on the features freeze time. cherry-picking fix it ok, but does not work for BIG PRs with protocol changes, API changes, such huge changes might introduce new problems during the cherry-picking. After the features are completed, I will create the new

[GitHub] [pulsar-helm-chart] lhotari commented on pull request #225: allow specifying the nodeSelector for the init jobs

lhotari commented on pull request #225: URL: https://github.com/apache/pulsar-helm-chart/pull/225#issuecomment-1033539128 > what do i do for the bookkeeper_cluster_initalize jobs? specify another nodeSelector value? or use the pulsar_metadata.nodeSelector value there as well? I thin

[GitHub] [pulsar-client-node] csauvage commented on issue #189: Fail to build `pulsar-client` on M1

csauvage commented on issue #189: URL: https://github.com/apache/pulsar-client-node/issues/189#issuecomment-1033513581 The first one worked perfectly, not the second one. Thx ! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [pulsar-client-node] csauvage closed issue #189: Fail to build `pulsar-client` on M1

csauvage closed issue #189: URL: https://github.com/apache/pulsar-client-node/issues/189 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsub

Re: [DISCUSS] Apache Pulsar 2.10.0 release

PengHui, There is a recent discussion with Matteo (at the community meetings) about preparing the release branch a couple of weeks before sending out the official VOTE. What about creating the branch-2.10 as soon as possible? We will commit to that branch only the fixes needed to make 2.10.0 stabl

Re: [DISCUSS] Apache Pulsar 2.10.0 release

Hi all, Sorry for the late reply, due to my vacation these days, we got a delay here. Most of the changes of 2.10.0 are getting merged, for now, there are 14 opened PRs(10 approved) https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.10.0 I will take care of them and try to

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

> Does this mean that transactions are not yet stable in 2.9? I think we need to clarify this point and then communicate that to our users. At least currently it is not a stable version, all the components have been completed but at least not verified on a large scale, the performance needs to be