Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

you looked into our past blog posts, we >>> have been pointing people to the Pulsar website and Slack channel. >>> >>> - Sijie >>> >>> >>> >>> On Thu, Dec 9, 2021 at 12:13 PM Dave Fisher wrote: >>> >>> OK. I see the new name.

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

l. This tweet https://twitter.com/streamnativeio/status/1469366308022013953 from today implies SN wants to control the roadmap. In the Apache Way the project roadmap is discussed on the dev list. If it’s not on the dev list it didn’t happen. Dave > > - Sijie > > > > On Th

Re: Status of Pulsar 2.9.0 and starting 2.9.1

It can be the case that releases are not announced. For example with Tomcat a version which fails to pass the vote is skipped. Let’s not announce 2.9.0 and go on to 2.9.1. Maybe there’s some website fixes to hide 2.9.0. Sent from my iPhone > On Dec 12, 2021, at 5:28 PM, PengHui Li wrote: >

Re: Status of Pulsar 2.9.0 and starting 2.9.1

2.9.0. They will also worry about the release >> quality of Apache Pulsar if we have found the critical bugs before it >> is released but not included it into the release version. For Pulsar >> 2.9.0, it couldn't be deployed into the production environment due to >> the

Re: [DISCUSS] Release Pulsar 2.7.4

I see 2 PRs still open at https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.7.4 Sent from my iPhone > On Dec 12, 2021, at 8:22 PM, guo jiwei wrote: > > I have pushed out some fixes in https://github.com/apache/pulsar/pull/13243 > After the tests get passed, I will

Re: Status of Pulsar 2.9.0 and starting 2.9.1

p on Maven), if it's not >> "announced", that's just a "publicity" effort because the 2.9.0 release is >> out there. >> >> >> >> On Sun, Dec 12, 2021 at 11:34 PM Dave Fisher >> wrote: >> >>> (1) we have

Re: [Great News] Pulsar Hits 10,000 GitHub Stars Milestone!

ide people to contribute to >> >> the >> >>> project roadmap and empower the community. If anyone is interested in how >> >>> the Ambassador Program works, I would encourage everyone to sign up for >> >> the >> >>> program to help

Log4j2 Zero Day vulnerability (CVE-2021-44228)

Please see the blog post @ https://pulsar.apache.org/blog/ December 11, 2021 Matteo Merli <> Yesterday, a new serious vulnerability was reported regarding Log4j that can allow remote execution for attackers. The vulnerability issue is described and tracked under CVE-2021-44228

Log4j 2.16.0 a more complete fix to Log4Shell

https://lists.apache.org/thread/d6v4r6nosxysyq9rvnr779336yf0woz4

Log4Shell Vulnerability

We should provide updates to secur...@apache.org about our status regarding Log4Shell. Here is the current blog post about impacted projects: https://blogs.apache.org/security/entry/cve-2021-44228 Here is a blog post about Log4j exploits; https://blogs.apache.org/foundation/entry/apache-log4j-cv

Re: PIP 116: Create Pulsar Writing Style Guide

Thanks Yu for this initiative. I made a small correction in the document. Regards, Dave > On Dec 14, 2021, at 7:17 PM, Yu wrote: > > Hi Pulsar enthusiasts, > > > As you may notice, there are more and more documentation contributions > nowadays, which is great! > > > Similar to coding style

Re: [DISCUSS] How to handle stale PRs

> >> On Fri, Dec 3, 2021 at 1:25 PM Jonathan Ellis wrote: >>> >>> Agreed. >>> >>> I don't think I understand tison's objection to closing very stale PRs >>> automatically -- if it's gone that long without attention the situatio

Re: [DISCUSS] How to handle stale PRs

tomatically -- if it's gone that long without attention the situation >>> isn't likely to change. And the submitter can always reopen it if it's >>> still relevant. >>> >>> On Fri, Dec 3, 2021 at 1:17 PM Dave Fisher wrote: >>> >>>

Re: [DISCUSS] How to handle stale PRs

; Getting consensus and creating a process here could help make our >>> committers more efficient. >>> >>> - Michael >>> >>> >>> On Fri, Dec 3, 2021 at 1:25 PM Jonathan Ellis wrote: >>>> >>>> Agreed. >>>> >>>

Re: [DISCUSS] How to handle stale PRs

ewers can review. >>>> >>>> >>>> Matteo >>>> >>>> -- >>>> Matteo Merli >>>> >>>> >>>> On Wed, Dec 15, 2021 at 1:05 PM Michael Marshall >>>> wrote: >>>>> >

Re: [DISCUSS] How to handle stale PRs

configuration: https://github.com/openmessaging/benchmark/blob/master/.github/stale.yml This bot is allowed in GitHub.com/apache/ where 11 repositories are currently using it. When we are ready we will simply create an INFRA JIRA. > On Dec 15, 2021, at 4:15 PM, Dave Fisher wrote: > >

Re: [apache/pulsar] [website] website upgrade (#11766)

This is a question for the dev@pulsar list and not a blocker for infrastructure. I don’t think there is an overriding requirement to preserve docs from incubating releases. If there were then there are other ways to find and regenerate these docs. Regards, Dave Sent from my iPhone > On Dec 19

Re: WebSite build CI job does work - blocker for announcing release !

Hi - A WebSite Build CI Job just completed. Please check that it created the new docs. I see the release notes for 2.9.1 - https://pulsar.apache.org/en/release-notes/ Regards, Dave > On Dec 21, 2021, at 11:33 PM, Nicolò Boschi wrote: > > I think the problem is that it times out (currently th

Re: WebSite build CI job does work - blocker for announcing release !

See this PR for 2.8.1 - https://github.com/apache/pulsar/pull/12089/files > On Dec 22, 2021, at 12:48 PM, Enrico Olivelli wrote: > > Thanks Dave, > I don't see 2.9.1 in the download page. > Did I miss to update some files? > > Enrico > > Il Mer 22 Dic 202

Re: Docs site cache down?

It looks like a caching issue / missing redirect / httpd configuration. If you navigate to the docs from the main page it’s good while if try to hand write a url you and I get a 503. Likely it should be an Infra JIRA issue. It could make sense to examine the asf-site branch in Apache/pulsar rep

Re: Docs site cache down?

Infra is on the case Sent from my iPhone > On Dec 23, 2021, at 5:50 PM, Dave Fisher wrote: > > It looks like a caching issue / missing redirect / httpd configuration. If > you navigate to the docs from the main page it’s good while if try to hand > write a url you

Re: Docs site cache down?

All better. Sent from my iPhone > On Dec 23, 2021, at 6:03 PM, Dave Fisher wrote: > > Infra is on the case > > Sent from my iPhone > >> On Dec 23, 2021, at 5:50 PM, Dave Fisher wrote: >> >> It looks like a caching issue / missing redirect / httpd confi

Re: [VOTE] Apache Pulsar 2.8.2 candidate 2

Hi Lin Lin - We really need to complete this release and announce it ASAP. Regards, Dave > On Dec 30, 2021, at 5:58 AM, Enrico Olivelli wrote: > > What's the status of this VOTE? > > Enrico > > Il Mer 22 Dic 2021, 10:34 Nicolò Boschi ha scritto: > >> +1 (non binding) >> >> Checks: >> - Ch

Re: Sending 2.6 release line to EOF

I don’t think we need a VOTE. Let’s do this by LAZY CONSENSUS. > On Jan 3, 2022, at 10:05 AM, Enrico Olivelli wrote: > > Hello, > We are no more cutting releases out of branch-2.6 > > We must declare 2.6 EOF. > > IIUC there is no process established for this at the moment in the Pulsar > proje

Re: Sending 2.6 release line to EOF

hink having a vote and quickly announce the EOF of 2.6.x will be better >> to the community. >> >> >> Dave Fisher 於 2022年1月4日 週二 06:06 寫道： >> >>> I don’t think we need a VOTE. Let’s do this by LAZY CONSENSUS. >>> >>>> On Jan 3, 2022, at 10:05

Voting time period minimum

The ASF considers that the minimum time for a vote is 72 hours for a few reasons particularly: (1) to allow the world to spin. People are in most time zones. (2) to allow for weekends. (3) to allow time for contributors who are not working full time on the project. Many projects use a 7 day vote

Re: Voting time period minimum

on [1]. > Maybe we should update the wiki and PIP template first? > > [1] > https://github.com/apache/pulsar/wiki/Pulsar-Improvement-Proposal-%28PIP%29 > >> On 2022/01/04 03:59:45 Dave Fisher wrote: >> The ASF considers that the minimum time for a vote is 72 hours for a f

Re: [DISCUSSION] PIP-132: Support Pulsar system event.

Sent from my iPhone > On Jan 5, 2022, at 8:10 PM, Haiting Jiang wrote: > >  >> CompletableFuture trigger(SystemEventMessage message); > > Maybe `record` make more sense? > >> SystemEventMessageBuilder properties(Map properties); >> >> SystemEventMessageBuilder addProperty(String key,

Re: Voting time period minimum

che.org/thread/m8dr0hz7qn7rkd48bcp430lcq2q3674g [2] https://lists.apache.org/list?dev@pulsar.apache.org:lte=1y:[VOTE] > > For other activities, this project follows the ASF 72 hours rule. > > - Sijie > > On Mon, Jan 3, 2022 at 8:17 PM Dave Fisher wrote: > >> Yes please! I did not notice that

Re: Voting time period minimum

> On Jan 7, 2022, at 2:59 PM, Matteo Merli wrote: > > On Fri, Jan 7, 2022 at 9:27 AM Dave Fisher wrote: >>> I believe 48 hours vote is only for PIP, which was agreed in the dev@. >> >> I would like to understand why Matteo chose 48 hours for this process. >

Re: [DISCUSS] Add icebox label for issues and PRs that have been inactive for more than 4 weeks

> On Jan 12, 2022, at 8:15 AM, PengHui Li wrote: > > Hi Pulsar Community, > > I want to start a discussion about introducing an icebox label that can be > added to > the issue or PR by pulsar bot automatically to help us can focus on the > active PRs > and issue. To avoid missing merge PRs, re

[ANNOUNCE] New PMC Member - Lari Hotari

Pulsar PMC Best Regards, Dave Fisher on behalf of the Pulsar PMC

Re: [DISCUSS] New repository for website - pulsar-site

new staging branch. From the PR it will be named ‘asf-site-next’ All the best, Dave > > Thanks! > > [1] https://github.com/apache/pulsar-site > [2] > https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#heading=h.n6wibg4w77xk > >> On 2

Re: [DISCUSS] New repository for website - pulsar-site

s://github.com/apache/pulsar-site/blob/ffc2e424a7565584e58c1f5a10bb0b1253497f53/.github/workflows/ci-pulsar-website-next-build.yaml#L78-L79> > > > Thanks, > Li Li > > >> On Jan 21, 2022, at 11:04 AM, Dave Fisher wrote: >> >> Hi Liu Yu, >> >>>>

Re: [DISCUSS] New repository for website - pulsar-site

Hi Li Li, Please see https://issues.apache.org/jira/browse/INFRA-22778 for further instructions. All the best, Dave > On Jan 20, 2022, at 10:16 PM, Dave Fisher wrote: > > It’s a bit late in my evening. > > You could access the-asf.slack.com #asfinfra and ask about saving/c

AWS Terraform Deployment - PRs

Hi - I found this PR - https://github.com/apache/pulsar/pull/7887 It does most of the terraform fixes needed to make https://github.com/apache/pulsar/tree/master/deployment/terraform-ansible functional which hasn’t worked since 2.6.0. I would like to merge this PR, but I’m not sure if it cause

Re: AWS Terraform Deployment - PRs

Sent from my iPhone > On Jan 28, 2022, at 1:26 PM, Dave Fisher wrote: > > Hi - > > I found this PR - https://github.com/apache/pulsar/pull/7887 > > It does most of the terraform fixes needed to make > https://github.com/apache/pulsar/tree/master/deployment/terrafo

Managing Projects Independently

The ASF has a number of resources created from decades of fostering hundreds of software communities in their missions to build amazing software components. One of the committees is the Community Development PMC (ComDev) Please review the following page: https://community.apache.org/projectInde

Re: [PR] Update .asf.yaml to protect current release branches

Before the asf-site branch can deleted the people working on the website need to finish the transition of https://github.com/apache/pulsar-site to build the main site and not a staging site. All the best, Dave > On Feb 15, 2022, at 8:55 AM, Michael Marshall wrote: > > Now that https://github.

Re: [VOTE] Pulsar Release 2.8.3 Candidate 1

> On Feb 15, 2022, at 3:59 PM, PengHui Li wrote: > >> I wonder if we should be more willing to share suspicions on the > mailing list when releases are actively being prepared. I would > have appreciated the notice, and I could have possibly helped > confirm the issue. On the other hand, I res

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

While it’s preferred that KEYS are signed it’s not required. The last Apache key signing party was at Apachecon Las Vegas in 2019. Here’s looking forward to the next one. Bring your government ids. Regards, Dave Sent from my iPhone > On Feb 16, 2022, at 6:11 PM, PengHui Li wrote: > > Hi Mi

Re: [NOTICE] Pulsar Helm Charts Repo is temporarily down

We can revert the PRs that switched over if necessary and follow with more testing. It’s a trade off. All the best, Dave Sent from my iPhone > On Feb 16, 2022, at 8:54 PM, Sijie Guo wrote: > > Hi everyone, > > Just want to let everyone know that the Pulsar Helm Charts repo is > temporarily

Re: Pulsar Helm Chart Repo is broken

Change L74 to pulsar-site Change L76 to asf-site-next All the best, Dave Sent from my iPhone > On Feb 16, 2022, at 9:02 PM, Sijie Guo wrote: > > Yes, we just need to change the CI process in `pulsar-helm-chart` to > publish the index.yaml file to the new website. > > See > https://github.co

Re: [VOTE] Pulsar Release 2.10.0 Candidate 1

Hi - Has anyone else found another breaking issue? Just asking to save Peng Hui time if there is another fix for RC2, All the best, Dave Sent from my iPhone > On Feb 22, 2022, at 8:31 PM, PengHui Li wrote: > > Hi all, > > This PR https://github.com/apache/pulsar/pull/14410 fixes a breaking

Re: [DISCUSS] PIP-139 : Support Broker send command to real close producer/consumer.

Hi - I hope I’m understanding what’s being discussed. If we are going to automatically delete tenants and namespaces for not containing topics then we need to make both of these automatic actions configurable with a default to NOT do so. Otherwise we break existing use cases. Automatic deletio

[ANNOUNCE] New Committer: Andrey Yegorov

for CVEs Welcome and Congratulations, Li Li! Please join us in congratulating and welcoming Andrey onboard! Best Regards, Dave Fisher on behalf of the Pulsar PMC

KEYS file update

We have two KEYS files stored on https://dist.apache.org one in the Release directory and one in the Dev directory. Apache Release Distribution Policy (https://infra.apache.org/release-download-pages.html) requires and on the Download page (https://pulsar.apache.org/en/download/) we refer to h

Re: [DISCUSS] Create a nightly docker image

The ASF has a JFrog artifactory instance that could help. Ask on bui...@apache.org! Regards, Dave Sent from my iPhone > On Mar 18, 2022, at 9:53 PM, PengHui Li wrote: > > I think we can use a separate org to maintain the nightly builded snapshot > images? > So that the external repo can pull

Re: [Guideline] Pulsar PR Naming Convention

Hi - I think that these guidelines are making it hard for new contributors. Our guidelines should make it super easy to make contributions. The guidelines are for contributions. Contributors are the community. Committers will review contributors PRs and can gently fix mistakes for them to show

Re: Pulsar download web page

Please Merge https://github.com/apache/pulsar/pull/14855 and test the website after the build to correct this issue. > On Mar 24, 2022, at 5:10 PM, Private List Moderation > wrote: > > Hi, > > I'm afraid I cannot approve this announcement because the download page has > an issue: > > The si

Fwd: [NOTICE] Introducing GitHub Actions build status notification for git repositories.

Hi - There is a new feature from ASF Infra for GitHub Action notification! ATB, Dave > Begin forwarded message: > > From: Daniel Gruno > Subject: [NOTICE] Introducing GitHub Actions build status notification for > git repositories. > Date: March 26, 2022 at 1:42:54 PM PDT > To: annou...@infra

Fwd: Call for Presentations now open, ApacheCon North America 2022

The Call For Presentations for ApacheCon NA in New Orleans is now open. There will be a Pulsar Event Streaming track. Please consider attending and submitting a talk. This will be an in-person conference only. Further details will come as we get closer to the event. All The Best, Dave > Begin

Re: [VOTE] Migrate TestNg Assertion to AssertJ

Hi - > On Apr 7, 2022, at 6:22 AM, Roc Marshal wrote: > > Hi Pulsar community, > > > Start voting for [DISCUSS] Migrate TestNg Assertion to AssertJ . It will > stay open for at least 48 hours. > The discussion thread is > https://lists.apache.org/thread/fo43qg3jtoqy62j2zyro3j88jfhtb

[NEXT STEPS] Pulsar Release 2.10.0 Candidate 5

Hi Peng Hui, Thank you for taking on the very difficult and tedious role of Release Manager. Please feel free to ask for volunteers to help you complete this release. If anyone notices anything Peng Hui has missed please see if you can help! All the Best, Dave Sent from my iPhone > On Mar 26,

Re: [VOTE] Migrate TestNg Assertion to AssertJ

nging all the tests is a huge amount of work. All the best, Dave > Thanks,Roc > At 2022-04-07 22:16:40, "Dave Fisher" wrote: >> Hi - >> >>> On Apr 7, 2022, at 6:22 AM, Roc Marshal wrote: >>> >>> Hi Pulsar community, >>> >>

Re: [DISCUSS] PIP-155: Drop support for Python2

+1 Sent from my iPhone > On Apr 16, 2022, at 11:15 AM, Matteo Merli wrote: > > Adding a bit on which Python versions to support, I found this very > helpful: https://endoflife.date/python > > Basically 3.5 and 3.6 releases have already reached end-of-life as > well and there will be no more s

Re: JDK 17 runtime compatibility

Bumping this thread so it’s current. > On Feb 14, 2022, at 6:09 AM, Christophe Bornet wrote: > > Big +1 > > Le lun. 14 févr. 2022 à 14:54, Nicolò Boschi a > écrit : > >> Dear Pulsar community, >> >> >> I would like to start a discussion about having a plan to make Pulsar >> runtime-compatib

Re: [VOTE] PIP-156: Build and Run Pulsar Server on Java 17

This is close and much work is done. +1. > On Apr 20, 2022, at 9:37 AM, Heesung Sohn > wrote: > > Dear Pulsar Community, > > Please review and vote on this PIP. > > PIP link : https://github.com/apache/pulsar/issues/15207 > > Thank you, > -- > > > > Heesung Sohn

Re: Enable GitHub Discussions?

I asked Infra. GitHub Discussions are not synchronized into ASF Infrastructure's GitBox. That means that there is not ability to change the notification scheme to send to a mailing list. Technically we can go down this path only if it is possible to set a notification within GitHub. You would n

Re: Enable GitHub Discussions?

PMC should discuss that. All The Best, Dave [3] http://theapacheway.com/consensus/ > > Then we can ask Infra to do the needed GitHub Admin tasks if we reach a > consensus on enabling it, thank you! > > [1] http://theapacheway.com/on-list/ > > Anonymitaet > > On Fri,

{CHERRY-PICK concerns] Re: [pulsar] branch master updated: [improve][broker] Tidy up the system topic. (#15252)

I am not saying we need to cherry pick this change. I want to note that this seemingly small change does touch a large number of files with 44 changed. Changing that many files may impact future changes that will need to be cherry picked. Those cherry picks of future PRs to 2.8.4, 2.9.3, and 2.1

Re: New Pulsar Website is Live!

You’re welcome Mellissa! Thanks to everyone who made this change possible! Sent from my iPhone > On May 11, 2022, at 8:33 AM, Melissa Logan wrote: > > Excited to see it go live! Thank you to all collaborators including Yu, > Lili, Paul, Dawn, Dave D, Dave F, Jun, Julia and everyone who provide

Re: Build Pulsar Server on Java 17- too strict ?

> On May 11, 2022, at 6:39 AM, Matteo Merli wrote: > > On Wed, May 11, 2022 at 1:10 AM Enrico Olivelli wrote: >> I am sorry, I missed this discussion. >> But until we cut a release we are in time to change our minds, if we >> find out that we can do better. > > Yes, but the precise point of

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

Hi - The two most important issues are search and translations. I’d like to know when these will be fixed. Also, I’ve been trying google as an alternative to our broken search and it is giving me ancient docs instead of latest. IMO - These graphical issues are comparatively trivial. That and th

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

In addition those who don’t like the light blue background have the dark option of a black background. Sent from my iPhone > On May 12, 2022, at 8:33 PM, Dave Fisher wrote: > > Hi - > > The two most important issues are search and translations. I’d like to know > when t

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

chives/C02Q4JLUB38/p1649233950692869 < >> https://apache-pulsar.slack.com/archives/C02Q4JLUB38/p1649233950692869> >> >> Anyway, May need cckell...@gmail.com to help with this >> >> >>> On May 13, 2022, at 11:33 AM, Dave Fisher wrote: >>> >>>

Re: [DISCUSS] Apache Pulsar 2.10.1 release

There are some PRs that are coming in that must be included. Thanks, Dave > On May 23, 2022, at 9:59 PM, Yunze Xu wrote: > > +1 > > Thanks, > Yunze > > > > >> 2022年5月23日 11:34，Hang Chen 写道： >> >> +1 >> >> There are a lot of transaction fixes. >> >> Thanks, >> Hang >> >> PengHui Li 于2

Re: [DISCUSS] Apache Pulsar 2.9.3 release

There are some PRs that are coming in that must be included. Thanks, Dave > On May 23, 2022, at 4:29 AM, PengHui Li wrote: > > +1 > > Thanks > Penghui > > On Mon, May 23, 2022 at 3:31 PM mattison chao > wrote: > >> Hello, Pulsar community: >> >> I'd like to propose to release Apache Pulsa

About 2.10.1, 2.9.2, 2.8.4 has this been cherry picked yet? [fix][java-client] Fix performance regression with message listener

This is a fix for a severe performance regression and I wanted to be sure that it gets cherry picked. > On May 31, 2022, at 6:48 PM, GitBox wrote: > > > dave2wave commented on PR #15162: > URL: https://github.com/apache/pulsar/pull/15162#issuecomment-1143028123 > > Has this been cherry pick

Re: [DISCUSS] Apache Pulsar 2.9.3 release

> On Jun 2, 2022, at 11:55 PM, mattison chao wrote: > > Hi Dave Fisher, > >> There are some PRs that are coming in that must be included. > > How's the progress on these PRs? They are merged. Regards, Dave > > Best, > Mattison > > On We

Re: [DISCUSS] Apache Pulsar 2.10.1 release

Please proceed with preparing the 2.10.1 release. > On May 24, 2022, at 1:17 PM, Dave Fisher wrote: > > There are some PRs that are coming in that must be included. > > Thanks, > Dave > >> On May 23, 2022, at 9:59 PM, Yunze Xu wrote: >> >> +1 >>

Re: [DISCUSS] Implementation for HTTP endpoint producer/consumer

If this is a REST endpoint then call it REST. It is very likely that users will want to use HTTPS to use it. Calling it HTTP is a misnomer. All The Best, Dave Sent from my iPhone > On Jun 7, 2022, at 7:25 AM, Zhengxin Cai wrote: > > Thanks for bringing this up. > I think building a separate

Re: [DISCUSS] PIP-175: Extend time based release process

Hi - Interesting, some responses inline. > On Jun 7, 2022, at 3:25 PM, Matteo Merli wrote: > > https://github.com/apache/pulsar/issues/15966 > > > > ## Motivation > > In PIP-47 > (https://github.com/apache/pulsar/wiki/PIP-47:-Time-Based-Release-Plan), > we have adopted a time-based

Re: [DISCUSS] PIP-175: Extend time based release process

> On Jun 8, 2022, at 11:44 AM, Matteo Merli wrote: > > On Tue, Jun 7, 2022 at 10:14 PM PengHui Li wrote: >> >> I'm not sure I fully understand the LTS release and feature release. >> >>> The LTS releases will be identified by being a `.0` version. For example: >>> * `3.0` -> LTS >>> * `3.1`

Re: [pulsar] branch master updated: [modify][admin] Change the permissions of the schema API from Admin to normal produce/consume (#15956)

Changes to admin permissions are decisions that require some discussion on dev@pulsar. Regards, Dave > On Jun 9, 2022, at 5:11 AM, techno...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > technoboy pushed a commit to branch master > in repository

Re: Pulsar Documentation Guides

Hi Yu, I have a request. Please make these guides part of the website and on project managed resources. Thank you, Dave Sent from my iPhone > On Jun 13, 2022, at 9:04 AM, Yu wrote: > >  > Hi team, > > This is a soft reminder: > > If you make contributions to Pulsar documentation, please f

Re: [DISCUSS] PIP-180: Shadow Topic, an alternative way to support readonly topic ownership.

On Jun 21, 2022, at 1:00 AM, Haiting Jiang wrote: > > Hi Pulsar community: > > I open a pip to discuss "Shadow Topic, an alternative way to support readonly > topic ownership." > > Proposal Link: https://github.com/apache/pulsar/issues/16153 > > --- > > ## Motivation > > The motivation i

Re: Any sign of 2.8.4?

Hi Frank, We need a Pulsar Committer to step up to be the Release Manager. Regards, Dave > On Jun 24, 2022, at 1:05 PM, Frank Kelly wrote: > > Hi All, >Last email I saw of a 2.8.4 release was May 31st is there still a > possibility or are folks working on 2.9.3 and upwards? > > Thanks! >

Re: [VOTE] Pulsar Release 2.10.1 Candidate 1

Hi - The Release Manager can vote. Shouldn’t you? Best Regards, Dave Sent from my iPhone > On Jun 26, 2022, at 5:51 PM, PengHui Li wrote: > > Hi all, > > Thanks for all your verification for 2.10.1 > > We currently have 2 (+1) bindings and 5 (+1) non-bindings. > We need one more (+1) bindi

Re: [DISCUSS] Enable GitHub Discussions?

Hi - Now that the ASF has a notifier on GitHub Discussions I have no objection to using discussions as long as these are visible on dev@pulsar.apache.org mailing list. > From the previous thread it seems that the Pulsar community has already > multiple channels to

Re: [VOTE] PIP-181: Pulsar Shell

+1 (binding) Sent from my iPhone > On Jul 4, 2022, at 7:46 AM, Nicolò Boschi wrote: > > Dear Community, > > I would like to start a VOTE on "PIP-181: Pulsar Shell" > > The proposal can be read at [0] and the discussion thread is available at > [1]. > Voting will stay open for at least 48h. >

Re: Trademark listing?

Hi Patrick, Pulsar is a trademark of the ASF.. It is not registered. Please use the ™ as appropriate. All The Best, Dave > On Jul 4, 2022, at 10:24 AM, Patrick McFadin wrote: > > Hi all, > > I was working with my publisher on an upcoming book project I'm working on > and found something I co

Re: Trademark listing?

missing from the ASF trademark page is that just an > email to trademark@ or is that something the PMC needs to do? The Pulsar > homepage should be updated as well. > > Patrick > > On Tue, Jul 5, 2022 at 4:15 PM Dave Fisher wrote: > >> Hi Patrick, >> >> Pulsar

Re: [DISCUSS] Enable GitHub Discussions?

-list-moderation.html I already moderate a large number of mailing lists. Mostly you will simply ignore some regular spammy phishing attacks. Regards, Dave > On Jun 28, 2022, at 9:13 AM, Dave Fisher wrote: > > Hi - > > Now that the ASF has a notifier on GitHub Discussions I have

[DISCUSSION] Improvements to Release Process Management

Hi - We need to tighten up our procedures around releases. There are several issues. 1. Maintaining the official KEYS file - https://dist.apache.org/repos/dist/release/pulsar/KEYS During the pulsar-manager-0.3.0 release the KEYS were not updated from https://dist.apache.org/repos/dist/dev/puls

Re: [VOTE] Enable GitHub Discussion for user-facing discussion

+1 - thanks. Emails will go to dev@pulsar initially. We should have a separate discussion about notifications since these are set on a repository by repository basis. > On Jul 12, 2022, at 4:04 AM, Yu wrote: > > Hi tison, thanks for creating this vote! > I thought we reached a lay consensus si

Re: [RESULT][VOTE] Enable GitHub Discussion for user-facing discussion

Hi - Discussions is now enabled at https://github.com/apache/pulsar/discussions We will see discussions activity on dev@pulsar. Once we begin to see how much activity, etc. then we can discuss if the email should go to users@ or a new discussions@ mailing list. Someone should start a discussio

Re: [VOTE] PIP-187 Add API to analyze a subscription backlog and provide a accurate value

+1 (binding) I support this enhancement for when a user occasionally requires accurate backlog stats. Once we bring this into service we can see if further guardrails are required. Regards, Dave > On Jul 19, 2022, at 10:02 AM, Enrico Olivelli wrote: > > This is the VOTE thread for PIP-187 >

Re: [DISCUSS] Apache Pulsar 2.8.4 release

Thank you for volunteering! > On Jul 21, 2022, at 12:57 AM, Yunze Xu wrote: > > Hello Pulsar Community, > > It has been several months since the 2.8.3 release and there are many > important fixes after that. For example, there is a performance > regression for message listener that was introduc

Re: [VOTE] PIP-174: Provide new implementation for broker dispatch cache

Sorry I’m late to this discussion. I think that the motivation is correct. There is really quite a bit of activity around this issue. Let’s take extra efforts to engage extra time with commits to confirm performance improvements. Let’s particularly pay attention to threading. +1 Regards, Dave

A note from your list moderator - please subscribe

Hi - Just a note that you will get your emails onto the list much faster if you subscribe to the list by sending an email to dev-suscr...@pulsar.apacche.org and responding to the confirmation email. If you don’t subscribe then you have to wait for a moderator to approve the email and that migh

Re: svn commit: r55993 - /release/pulsar/KEYS

Thank you! Sent from my iPhone > On Jul 27, 2022, at 5:01 AM, peng...@apache.org wrote: > > Author: penghui > Date: Wed Jul 27 09:01:00 2022 > New Revision: 55993 > > Log: > Added gpg key for jianghaiting > > Modified: >release/pulsar/KEYS > > Modified: release/pulsar/KEYS >

Re: [ANNOUNCE] Micheal Marshall as a new PMC member in Pulsar

Congratulations! Well deserved! > On Jul 26, 2022, at 11:21 AM, Enrico Olivelli wrote: > > I am glad to announce that the Apache Pulsar PMC invited Micheal to > join the PMC and he accepted. > > Micheal is doing a great job in stewarding our community > > Please join me and celebrate ! > > En

Re: [DISCUSS] Does stale bot make value for you?

Perhaps 30 days is too quick? 90 days might be better. Also in cases like this one it’s likely that a PR would get more discussion. The other aspect is it would be helpful if many Pulsar committers would spend effort every few weeks reviewing issues and PRs to engage the community. All the best

Re: [VOTE] PIP-193 : Sink preprocessing Function

+1 (binding) On 2022/07/28 10:39:35 Christophe Bornet wrote: > Hi, Pulsar community, > > I'd like to start a vote on PIP-193 : Sink preprocessing Function > > You can find the proposal at https://github.com/apache/pulsar/issues/16739 and > the discussion thread at > https://lists.apache.org/thre

Re: [DISCUSS] Skip unnecessary tests when there are only cpp/python related changes

Yes, please! Sent from my iPhone > On Aug 10, 2022, at 5:39 PM, PengHui Li wrote: > > +1 > > Best, > Penghui > >> On Wed, Aug 10, 2022 at 10:52 PM Yunze Xu >> wrote: >> >> LGTM >> >> Thanks, >> Yunze >> >> >> >> >>> 2022年8月10日 15:36，Zike Yang 写道： >>> >>> Hi, Pulsar community >>> >>

Re: Questions about the release process

Hi - One change that needs to be made is regarding the KEYS file. We should drop the use of https://dist.apache.org/repos/dist/dev/pulsar/KEYS instead we should carefully update https://dist.apache.org/repos/dist/release/pulsar/KEYS The two KEYS files are currently out of sync. The release fil

Re: Questions about the release process

docs part of versioned docs. > > I agree. > > Thanks, > Michael > > >> On Fri, Aug 12, 2022 at 10:32 PM Yunze Xu >> wrote: >> >>> The RM should ask a PMC member to help them add their KEY. >>> Do not make the release docs part of versio

Re: Questions about the release process

> On Aug 15, 2022, at 4:09 AM, Yunze Xu wrote: > >> One example is that `pool.sks-keyservers.net` in [1] seems not available > anymore, but I am not that confident enough to edit it directly. > > Yeah. It’s not available in my env as well. I made some changes recently, > but I’m also not sure

Re: Questions about the release process

> On Aug 15, 2022, at 3:30 AM, Haiting Jiang wrote: > >> Maybe we'd better move the release process doc and validation doc >> to the codebase, not the wiki pages. > > IMO, we can move all contributor documentation and committers documentation > to codebase. > One example is that `pool.sks-key

  1   2   3   4   >