[VOTE] Pulsar Release 3.2.1 Candidate 2

This is the second release candidate for Apache Pulsar version 3.2.1. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.2.1+label%3Acherry-picked%2Fbranch-3.2+ *** Please download, test and verify on this release. This vote will stay o

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

My fault for missing the discussion mails for these PIPs because I didn't check the archives of previous months. Thanks, Yunze On Thu, Mar 7, 2024 at 3:05 PM Lari Hotari wrote: > > On Thu, 7 Mar 2024 at 08:14, Girish Sharma wrote: > > There is for 310 - > > https://lists.apache.org/thread/13ncs

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

On Thu, 7 Mar 2024 at 08:14, Girish Sharma wrote: > There is for 310 - > https://lists.apache.org/thread/13ncst2nc311vxok1s75thl2gtnk7w1t Girish, thank you for sharing the link to the PIP-310 thread. We also met in community meetings to discuss PIP-310 (https://lists.apache.org/thread/y1sqpyv37fo

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> > know I’m not trying to be disrespectful, but it’s not respectful to be > biased and act like an expert during the reviews, while you’ve contributed > just for documentation PRs. When I talk about experience, I’m talking about > reviewers who don’t contribute to the project, they ask questions t

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

Hello, Please find the discussion thread for PIP-337 on the Dev mailing list: https://lists.apache.org/thread/v4xh3fqy2t62xdk37b2ghvkrvvnqrx80 In the case of PIP-337, Lari was prompt in helping review the PIP and PR and providing valuable feedback. I acknowledged it via slack direct message to hi

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

On Thu, Mar 7, 2024 at 11:38 AM Yunze Xu wrote: > Regarding PIP-332 and PIP 310, similar to PIP-337, there is no > discussion mail in the dev mail list. David left a comment [1] in > There is for 310 - https://lists.apache.org/thread/13ncst2nc311vxok1s75thl2gtnk7w1t Regards -- Girish Sharma

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

Regarding PIP-332 and PIP 310, similar to PIP-337, there is no discussion mail in the dev mail list. David left a comment [1] in PIP-332 and there is no response. We can see discussions among Lari, Asaf and the author in PIP-310. And eventually PIP-310 is closed because the author has a different w

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

On Wed, Mar 6, 2024 at 7:02 PM Kalwit S wrote: > I know I’m not trying to be disrespectful, but it’s not respectful to be > biased and act like an expert during the reviews, while you’ve contributed > just for documentation PRs. When I talk about experience, I’m talking about > reviewers who don’

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> Our team has also tried to submit multiple enhancements and also PIP, but most of them are bogged down by reviewers who are very new to Pulsar, might not understand messaging correctly, or don’t find such enhancements useful for their usecases. If your PRs or PIPs are not taken enough care of,

Re: [VOTE] Pulsar Client Go Release 0.12.1 Candidate 1

+1 (binding) - Verified checksum and signatures - Run OAuth2 e2e examples with 0.12.1-candidate-1 - Built from source and run perf to produce and consume Thanks, Yunze On Thu, Feb 29, 2024 at 11:05 AM Zike Yang wrote: > > Hi everyone, > Please review and vote on the release candidate #1 for the

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> On Mar 6, 2024, at 10:01 PM, Kalwit S wrote: > > Also, Pulsar may have > numbers of non-SM PMC’s and committers, but if you look at the numbers over > the last 2-3 years, you’ll see that 99% are from SM. If you are saying that this is the proportion of new committers and PMC members in the

Re: [DISCUSS] PIP-343: Use picocli instead of jcommander

Sync conversations from Slack. Lari Hotari: After this PR is completed, I will add the automatic completion feature. sounds great. Just wondering if there's an overlap with pulsar-shell. Is there a way to unite pulsar-admin and pulsar-shell in the future? Would that make sense? /cc @Nicoló Boschi

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

I know I’m not trying to be disrespectful, but it’s not respectful to be biased and act like an expert during the reviews, while you’ve contributed just for documentation PRs. When I talk about experience, I’m talking about reviewers who don’t contribute to the project, they ask questions to get to

Re: [VOTE] Pulsar Release 3.2.1 Candidate 1

Close this candidate, as we have a new fix, #22202, that needs to be contained in the release. I will raise a new candidate soon. Regards Jiwei Guo (Tboy) On Wed, Mar 6, 2024 at 7:08 PM PengHui Li wrote: > +1 (binding) > > - Built from source > - Checked the signatures > - Run standalone > -

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

I have not seen any specific asks or examples that give rise to these gripes, so it's all hypotheticals as of now. Please, as Enrico said, bring up specific issues. (1) How many reviewers (less than 1) have been involved in PIP review outside of the streamnative provider and how many of them have

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

On Wed, Mar 6, 2024 at 12:49 PM Kalwit S wrote: > Thanks for your reply. But I wasn’t going to go after a specific person. I > Though that's precisely what your message was doing, in a very rude way. (1) How many reviewers (less than 1) have been involved in PIP review > outside of the streamna

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

Kalwit, Il Mer 6 Mar 2024, 21:49 Kalwit S ha scritto: > Thanks for your reply. But I wasn’t going to go after a specific person. I > just wanted to point out this is an example of what we’ve been seeing for a > while now. And I wanted to point out why we’re not going to go with Pulsar. > Becaus

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

Thanks for your reply. But I wasn’t going to go after a specific person. I just wanted to point out this is an example of what we’ve been seeing for a while now. And I wanted to point out why we’re not going to go with Pulsar. Because if Streamnative is on the same trajectory as Confluent, then the

[HOW TO FOLLOW GITHUB] Re: [PR] WIP: PIP-342: OTel client metrics support [pulsar]

For anyone who wishes to watch activity from with a Pulsar GitHub repository please consider subscribing to comm...@pulsar.apache.org by sending an email to commits-subscr...@pulsar.apache.org and replying to a CONF

Re: [VOTE] PIP-343: Use picocli instead of jcommander

+1 nonbinding Zixuan Liu 于2024年3月6日 周三23:04写道： > Hello, > > A new proposal to improve the CLI user experience. > > PIP: https://github.com/apache/pulsar/pull/22181 > Discussion thread: > https://lists.apache.org/thread/ydg1q064cd11pxwz693frtk4by74q32f > > PR: https://github.com/apache/pulsar/pull

Re: [DISCUSS] Community Meeting Notes Are Missing

Lari and Matteo, True to what both of you to wrote. My point is how this may look to new community members. Think outside in for a few minutes. Even if there is no agenda I think a reminder before the meeting and then a summary like what Michael provided, or even a recording would really, real

Re: [DISCUSS] Community Meeting Notes Are Missing

Hi Dave, The meeting is being conducted in the same exact way as it was when you we’re participating in it. -- Matteo Merli On Wed, Mar 6, 2024 at 6:43 AM Dave Fisher wrote: > Hi - > > I see from the last meeting the following agenda: > > > 2024/02/29 > > Attendees: > > Lari Hotari > > Jona

Re: [DISCUSS] Community Meeting Notes Are Missing

On Wed, 6 Mar 2024 at 16:43, Dave Fisher wrote: > I do not recall that any of this discussion made it to the mailing list. It > looks like decisions are being made in the meeting. Hi Dave, I apologize for not being able to keep up with everything and for not including all the details in the mee

Re: [VOTE] PIP-343: Use picocli instead of jcommander

+1 (binding) Enrico Il giorno mer 6 mar 2024 alle ore 16:04 Zixuan Liu ha scritto: > > Hello, > > A new proposal to improve the CLI user experience. > > PIP: https://github.com/apache/pulsar/pull/22181 > Discussion thread: > https://lists.apache.org/thread/ydg1q064cd11pxwz693frtk4by74q32f > > PR

[VOTE] PIP-343: Use picocli instead of jcommander

Hello, A new proposal to improve the CLI user experience. PIP: https://github.com/apache/pulsar/pull/22181 Discussion thread: https://lists.apache.org/thread/ydg1q064cd11pxwz693frtk4by74q32f PR: https://github.com/apache/pulsar/pull/22209 Thanks, Zixuan

[DISCUSS] Community Meeting Notes Are Missing

Hi - I see from the last meeting the following agenda: > 2024/02/29 > Attendees: > Lari Hotari > Jonas > Kevin Lu > Frank Kelly > Asaf Mesika > Chris Bono > David Jensen > > Agenda > PIP-341: Pluggable client metrics tracker interface > 1. Should the OTel implementation be included in the PIP, o

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> On Mar 6, 2024, at 4:50 AM, Lari Hotari wrote: > > Hi Kalwit, > > In Apache Pulsar, as in any other Apache project, everyone is equal > regardless of their committer or PMC status. All project participants > are free to express their opinions, and, where appropriate, have the > community co

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> On Mar 6, 2024, at 2:31 AM, Enrico Olivelli wrote: > > Kalwit, > All the committers are invited by the PMC, you can reach out to > priv...@pulsar.apache.org if you have any problems. > > Being a committer is not only about doing code contributions, but also > talking care of the project and

Re: Pulsar Version upgrade guidelines

Bumping this up. I cannot be the only one confused by these questions. Pulsar is at a stage where users have to constantly upgrade due to stability or feature needs. The answers to the questions I am asking should help everyone planning upgrades from 2.x to 3.x and other combinations. Regards On

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

Idea: don't require updating versioned docs from contributors. Making a small documentation fix in a single place is easy, but if we ask contributors to fix it in 5-10 places, it may prevent the initiative at all. It could increase the amount of contributions to the documentation. I'm not sure h

Re: [VOTE] Pulsar Release 3.2.1 Candidate 1

+1 (binding) - Built from source - Checked the signatures - Run standalone - Checked producer and consumer - Verified the Cassandra connector - Verified the Stateful function Regards, Penghui On Wed, Mar 6, 2024 at 3:38 PM guo jiwei wrote: > +1 (binding) > > - Built from source > - Checked the

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

Hi Kalwit, In Apache Pulsar, as in any other Apache project, everyone is equal regardless of their committer or PMC status. All project participants are free to express their opinions, and, where appropriate, have the community consider them when decisions are made. [1] I'm sorry to hear that you

Re: [VOTE] Pulsar Release 2.10.6 Candidate 1

It sounds like the version release was triggered due to security issues. If so, I think we need to update our release policy. Only when a fatal security issue occurs can we trigger a release of a new version, but we also need to clarify the maintenance cycle, otherwise this maintenance is endless.

Re: [VOTE] Pulsar Release 2.10.6 Candidate 1

Dear Zixuan, Thank you for your email and your ongoing commitment to the Pulsar project. I wanted to clarify that this release, 2.10.6, is a special case. It was primarily focused on addressing certain security issues that were deemed critical. This decision was made following internal discussion

Re: [VOTE] Pulsar Release 2.10.6 Candidate 1

Thank you for releasing 2.10.6. According to the release policy defined [0] by Pulsar, this version is EOL and does not require further maintenance. If we need to continue to maintain the 2.10, we must discuss the maintenance lifecycle of the 2.10, and update our doc. - [0] https://pulsar.apache