Re: Apache Edgent

> Hi Dave, > > I created the JIRA issue and am trying to follow up now on getting that > JIRA implemented. When I contacted them, they basically said to commit a PR > for them to review, but I haven't had the time to do so. > > Regards, > David Kjerrumgaard > >

Re: Limitations on No.Of Producers and Consumers

Message was moderated onto the list, including the OP Sent from my iPhone > On Nov 12, 2018, at 2:28 AM, Ivan Kelly wrote: > > Hi Koushik, > >> I just got introduced to Apache pulsar and studying it to solve a problem at >> hand. >> As I understand that Pulsar supports 1M of topics, Is there

Re: All commits to the Pulsar repository

Oops! I meant to reject this. Sent from my iPhone > On Oct 8, 2018, at 8:13 PM, wangkai1 wrote: > > > 王凯 > 北京东方国信科技股份有限公司 > 电信事业部 > 技术中心－大数据技术部 > 手机：17503461125 > 邮箱：wangk...@bonc.com.cn > > 地址：北京市朝阳区来广营创达三路1号院1号楼东方国信大厦 > 邮编：100102 > 网址：http://www.bonc.com.cn

Re: Pulsar release 2.2

sparently >> redirects >>> the repository after renames, though... of course there will be some >> things >>> to polish here and there :) >>> >>> >>> >>> On Fri, Sep 21, 2018 at 5:49 PM Dave Fisher >> wrote: >>> >>&g

Moving to a TLP

Hi Everyone, Congratulations on Graduation! Matteo and the PMC have some tasks which are described here to move the project out of the Incubator and to Pulsar! https://incubator.apache.org/guides/transferring.html I will look into

Re: Pulsar release 2.2

BTW - the Infra team just now moved the repository out of the incubator! Check the release scripts! Sent from my iPhone > On Sep 21, 2018, at 4:29 PM, Sijie Guo wrote: > > I would suggest holding off a bit. trying to get those PR merged. > > - Sijie > >> On Fri, Sep 21, 2018 at 4:26 PM Joe

Re: [ANNOUNCE] Apache Pulsar

Hi - Sent from my iPhone > On Jan 6, 2019, at 8:55 PM, Sijie Guo wrote: > > That’s a good suggestion. I also think that provides a better way to > organize sub modules for now or even mid-term. > > However in long term, we should try to move out them out of Pulsar repo, or > even to push to

Re: About explicitly choose partition topic

Adding the OP who I moderated onto the list. (You subscribe by sending an email to dev-subscr...@pulsar.apache.org) Sent from my iPhone > On Jan 10, 2019, at 9:26 PM, Matteo Merli wrote: > > Hi Ruoruo, > > In order to consume messages in order on a partitioned topic, you should > use the

Re: subscribe request

You subscribe by sending an email to dev-subscr...@pulsar.apache.org and replying to the verification email. Regards, Dave Sent from my iPhone > On Mar 25, 2019, at 12:43 AM, jian he wrote: > > subscribe request

Re: PIP-31: Add support for transactional messaging

Hi - Is this a case where a Pulsar function base class for transactions would help? Regards, Dave Sent from my iPhone > On Mar 2, 2019, at 2:39 AM, Sijie Guo wrote: > > Pravega's model is a better model than Kafka - it addressed the > interleaving problems. However Pravega's model is based

Re: PIP-31: Add support for transactional messaging

. I’m not sure if it would work, but it seems that functions, spouts, and connectors make sense as opposed to burdening the highly performant brokers. Regards, Dave > > - Sijie > >> On Sun, Mar 3, 2019 at 1:52 AM Dave Fisher wrote: >> >> Hi - >> >

Re: PIP-31: Add support for transactional messaging

Hi Richard, I moderated your email onto the list. To participate please subscribe by sending an email to dev-subscr...@pulsar.apache.org and respond to the confirmation email as it instructs. Regards, Dave Sent from my iPhone > On Feb 27, 2019, at 8:35 PM, Richard Yu wrote: > > Hi all, >

Re: Google Season of Docs 2019

> On Mar 12, 2019, at 7:01 PM, Huxing Zhang wrote: > > Hi Dave, > > On Wed, Mar 13, 2019 at 2:14 AM Dave Fisher wrote: >> >> Hi - >> >> Looks pretty cool. > > Yes, all the ASF projects could benefit from it. I think ASF should > apply

Fwd: Tying Dockerhub into development and release management

ussions of this nature because the party > line is “the ASF releases code” but the reality is that “people consume > binaries.” > > Until that juxtaposition is well and truly addressed, these discussions will > continue to happen ad nauseam. I have not reviewed the threads on legal

Re: Benchmarking Pulsar using OpenMessaging Benchmark

Since I moderated this email onto the list I am cc’ing the OP to assure that any replies are seen. Regards, Dave > On Feb 19, 2019, at 4:34 PM, Tyler Landle wrote: > > Hey Guys, > > I have been trying to benchmark pulsar and get some E2E latency data from > it, and try to stress it in

Re: [DISCUSSION] Delayed message delivery

ull/3155 does :). > We still need to decide if we want to add this feature at client side or > broker side, the pull request does it on the broker. > > -- > *Ezequiel Lovelle* > > > On Tue, 19 Feb 2019 at 17:06, Dave Fisher wrote: > >> Hi - >> >&

Re: [DISCUSSION] Delayed message delivery

Hi - My thoughts here may be completely useless but I wonder if clients can add an optional argument to the broker call when pulling events. The argument would be the amount of delay. Any messages younger than the delay are not returned by the broker. Regards, Dave > On Feb 19, 2019, at

Re: [DISCUSS] Skip tests for documentation related changes

Hi - Inline Sent from my iPhone > On Jan 28, 2019, at 1:12 PM, Sijie Guo wrote: > > both adding tag or checkbox are developer driven. but it is easier to > achieve with current github pull request builder in Jenkins. > so I think the responsibility of this approach is kind of spreading across

Is Slack Blocked in China?

Hi - I heard somewhere that Slack is blocked in China. Is this so? Regards, Dave

Re: PIP-40: Contribute Pulsar Manager

Hi - I see that MySQL is used. This would be a GPL dependency. Does the Pulsar Manager require MySQL, or can other Databases that are compliant with Apache Release Policy be used instead? Regards, Dave > On Aug 29, 2019, at 7:49 AM, Guangning E wrote: > > Hi all, > > We have developed a

Re: PIP-40: Contribute Pulsar Manager

t; >>>>>> Thanks, >>>>>> Sijie >>>>>> >>>>>> On Thu, Aug 29, 2019 at 12:08 PM Enrico Olivelli < >>> eolive...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>

Re: ApacheCon NA

; > On Wed, Sep 4, 2019 at 10:55 AM Dave Fisher wrote: > >> Hi - >> >> In addition to finding a time to meet there are two “official” ways to do >> this: >> >> (1) Birds of a Feather in the evening which may miss other events: >> https://www.apac

Re: ApacheCon NA

Hi - In addition to finding a time to meet there are two “official” ways to do this: (1) Birds of a Feather in the evening which may miss other events: https://www.apachecon.com/acna19/bof.html (2) Hackathon - https://www.apachecon.com/acna19/hackathon.html Regards, Dave > On Sep 4, 2019, at

Re: PIP-40: Contribute Pulsar Manager

s already covered by ICLAs. Infra can then help transfer the repository. Regards, Dave > > Thanks, > Sijie > > On Wed, Sep 4, 2019 at 9:41 AM Dave Fisher wrote: > >> BTW - Once the VOTE is complete to accept the codebase there is some >> paperwork. >

Re: [DISCUSS] Improve website publish process in release procedure

A logical conundrum! You can’t get it index until its published and you can’t control when the updated site is indexed. Is there anyway to trigger their index? If so, do it to minimize the trouble. Infra just announced a new .asf.yaml service. I can see how we could add Apache Solr indexing to

Re: [DISCUSS] PIP: Producer Send Message with Different Schema

So true Sijie! That said these discussions are critical! Regards, Dave Sent from my iPhone > On Sep 6, 2019, at 1:12 AM, Sijie Guo wrote: > > We haven't defined a PIP process. However the community has run PIP in the > lazy consensus mode. > > Lazy consensus means you don't have to insist

Re: PIP 49: Permission levels and inheritance

I’m not diving in but thinking about the logical implication of this dichotomy. For any object’s attributes some ought to be controlled by object level permissions and others by sysadmin permissions. How can developers tell? Best Regards, Dave Sent from my iPhone > On Nov 7, 2019, at 8:02

Re: [VOTE] PIP-47: Time Based Release Plan

-1 (binding) This proposal has NOT been properly discussed in the Apache Way on the mailing list. There has been absolutely no discussion of this policy. There has been no attempt to reach consensus. Apache projects do NOT proceed like this. Please rescind this VOTE! Start a proper discussion

Re: [DISCUSS] Create the first pulsar-manager apache release

> On Oct 24, 2019, at 1:16 PM, Enrico Olivelli wrote: > > Guangnin, > The documents looks good. > Just one clarification: > > When you say > > Source and binary files: > > > You don't provide a link to the staging area but only to the github tag > > Is this expected? > IMHO we should

Re: [DISCUSS] Homebrew libpulsar

Hi - I’ve played with Homebrew before and from the git log I can see that Matteo created the initial version, but for the most part the Homebrew community has maintained the script. Here is the current script: Formula/libpulsar.rb class Libpulsar < Formula desc "Apache Pulsar C++ library"

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

-1 - What artifacts are we voting on? Where is the source package on the Apache servers? Packages here https://github.com/apache/pulsar-client-go/releases are not immutable. There are no checksums or signatures. No update to the KEYS file. Please put release candidates here:

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

specify the Git tag hash, both here in > the vote thread as in the release notes. > > Dave, do you thing that this would be an acceptable way to "release" a > blessed tag? > -- > Matteo Merli > > > > On Thu, Mar 26, 2020 at 9:26 AM Dave Fisher wrote: >> >

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

ttps://issues.apache.org/jira/browse/LEGAL-512 > > - Sijie > > > On Thu, Mar 26, 2020 at 11:29 AM Dave Fisher wrote: > >> Hi - >> >> There is an official release policy - >> http://www.apache.org/legal/release-policy.html#policy >> >> It does

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

well as the expected language approved way. This gives Pulsar’s users the ability to validate what’s on the official channel vs. the platform channel. The source is open forever. Thanks, Dave > > - Sijie > > >> On Thu, Mar 26, 2020 at 11:59 AM Dave Fisher wrote: >> >&g

Re: [IMPORTANT] - Migration to ci-builds.a.o

t 1:35 PM, Dave Fisher wrote: > > Migration technique: > https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees > > Helpful info: > https://cwiki.apache.org/confluence/display/INFRA/Kicking+off+a+Jenkins+build+with+a+GitHub+PR > > >

Re: [IMPORTANT] - Migration to ci-builds.a.o

ters can > confirm if that is the case. > > - Sijie > > > On Tue, Aug 18, 2020 at 11:39 AM Dave Fisher wrote: > >> Hi - >> >> It is critical to complete this migration THIS WEEK. >> >> I’ve submitted https://issues.apache.org/jira/browse/

Re: [IMPORTANT] - Migration to ci-builds.a.o

lete them. > > > - Sijie > > On Tue, Aug 18, 2020 at 11:52 AM Dave Fisher wrote: > >> Hi Sijie, >> >> They are still running on builds.apahce.org. >> >> Regards, >> Dave >> >>> On Aug 18, 2020, at 10:50 AM, Sijie Guo wro

Fwd: [IMPORTANT] - Migration to ci-builds.a.o

Hi - There is a critical migration for Jenkins builds that the project is missing. Several PMC members ought to be subscribed to bui...@apache.org. Please act quickly. Regards, Dave > Begin forwarded message: > > From: Gavin McDonald > Subject: [IMPORTANT] - Migration to ci-builds.a.o >

Re: [IMPORTANT] - Migration to ci-builds.a.o

Migration technique: https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees Helpful info: https://cwiki.apache.org/confluence/display/INFRA/Kicking+off+a+Jenkins+build+with+a+GitHub+PR > On Aug 14, 2020, at 12:48 PM, Dave Fisher wrote: >

Re: [DISCUSS] Protobuf 2.4.1

> On May 22, 2020, at 10:52 AM, Sijie Guo wrote: > > Hi all, > > I would like to kick off a discussion about what we should do for protobuf > 2.4.1 and figure out what is the long term plan. > > Currently, Pulsar is using a customized version of protobuf 2.4.1 for wire > protocol. The

Re: [DISCUSS] PIP-67: Contribute Pulsarctl to Apache Pulsar

Very cool! This contribution may need to go through IP clearance. https://incubator.apache.org/ip-clearance/ Regards? Dave Sent from my iPhone > On Jun 18, 2020, at 8:16 PM, Yong Zhang wrote: > > It seems that there are no objections to accepting this repo. > > What should I do in the

Re: [PROPOSAL] PIP 75: Replace protobuf code generator

s > > > Matteo > > > > -- > Matteo Merli > > > On Wed, Dec 23, 2020 at 10:20 AM Dave Fisher wrote: >> >> Hi Matteo, >> >> I looked at the dependencies in Splunk LightPro and the following are not >> acc

Re: [PROPOSAL] PIP 75: Replace protobuf code generator

Hi Matteo, I looked at the dependencies in Splunk LightPro and the following are not acceptable in an Apache Binary: org.openjdk.jmh jmh-core ${jmh.version} org.openjdk.jmh

Re: Proposal for Consumer Filtering in Pulsar brokers

Sorry, for the top post. I was reading what you wrote and knew where you were heading. Couldn’t these filtering functions / dispatchers be a special configuration of functions? (1) Topic (2) Filtered function (3) Filtered topic Isn’t the whole point of Functions to compute, filter, and

Re: Haskell Client: transfer of ownership

One important consideration is if there are enough community members who can support Haskiel. Another is if Gabriel will stick around and support the client code. Best Regards, Dave Sent from my iPhone > On Jan 4, 2021, at 6:25 PM, Sijie Guo wrote: > > Hi Gabriel, > > Thank you for

Re: [DISCUSS] Propose More Formal Policy for Security Patches and EOL of Versions

> On May 27, 2021, at 2:49 PM, Michael Marshall wrote: > > Hi Pulsar Community, > > > I would like to discuss defining and documenting a process for an official > Pulsar version EOL policy. This process will help users know when the > version they are running will no longer be supported

Re: Five minute interview blog posts

Inline Sent from my iPhone > On Feb 12, 2021, at 9:36 AM, Jonathan Ellis wrote: > >  > To make a specific proposal, I've attached a mockup of what a streamlined > home page would look like. > > Commentary: > - Introduction and Quickstart will follow Kafka’s model >

Re: Five minute interview blog posts

> >> Clean up the header by folding Clients, REST APIs, and Cli into Docs > > One of the reasons that why "Clients, REST APIs, and CLI" are added to the > menu, not the sidebar is due to the limitation of the documentation > framework we are using. If there is a way to improve this, that would

Re: Proposing a meetup organizing committee

BCC: private@ The bulk of this discussion should proceed with good intent on dev@ with a separate thread on private@ only if needed. I have prepared a set of links to documentation about the Apache Way that is worth reviewing: https://petri.apache.org/way

Re: Pulsar website concepts -- please vote

This is the Apache Pulsar project, not Pulsar. There are numerous compliant project sites. Goto www.Apache.org and link to one of 200 project sites from the bottom. Sent from my iPhone > On Sep 14, 2021, at 5:05 PM, Dave Fisher wrote: > > None of these concepts meets Apache project

Re: Pulsar website concepts -- please vote

None of these concepts meets Apache project branding requirements (and neither does the current site) https://whimsy.apache.org/site/project/pulsar Sent from my iPhone > On Sep 14, 2021, at 3:43 PM, Melissa Logan wrote: > > Reminder to cast your vote for the Pulsar website design concept by

Re: [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1

You need at least 3 +1 (binding) votes for this release vote to succeed. Sent from my iPhone > On Oct 11, 2021, at 10:22 PM, Masahiro Sakamoto > wrote: > > Closing the vote with 3 +1 and no -1. > > 2 +1 bindings are: > * Yuto > * Nozomi > 1 +1 non-binding is: > * Guangning > > Masahiro

Re: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1

At least 3 +1 (binding) votes are required. I suggest that you hold this open until you get the 3rd vote otherwise this vote fails. Regards, Dave Sent from my iPhone > On Oct 11, 2021, at 10:19 PM, Masahiro Sakamoto > wrote: > > Closing the vote with 2 +1 and no -1. > > 2 +1 bindings are:

Re: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1

> On Oct 8, 2021, at 3:20 AM, Masahiro Sakamoto wrote: > > This is the first release candidate for Apache Pulsar Node.js client, version > 1.3.2. > > It fixes the following issues: > https://github.com/apache/pulsar-client-node/milestone/9?closed=1 > > *** Please download, test and vote on

Re: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1

Hi Masahiro, If you VOTE then there will be 3 +1 (binding) Votes. Best Regards, Dave > On Oct 12, 2021, at 3:20 AM, Masahiro Sakamoto wrote: > > This is the first release candidate for Apache Pulsar Node.js client, version > 1.3.2. > > The artifacts are exactly the same as the first vote,

Apache Releases - Current Lines

This note will cover several points about Apache Release Distribution Policy. [1][2] All of the official Apache Pulsar release artifacts should be on the project’s download page. [3] What are the currently supported release artifacts? Where must all source release artifacts be on Apache

Re: Cutting releases for 2.7 and 2.6 branches

No better place than the download page to communicate the lifecycle. Sent from my iPhone > On Oct 4, 2021, at 9:19 PM, Michael Marshall wrote: > > Hi Enrico, > > Thank you for starting this conversation. I have been meaning to > follow up on this topic for some time, so I already have some

Re: [Proposal] Creating an Apache Pulsar Outreach Working Group

Hi - Even without an official group it should be possible to discuss improvements to outreach here on the dev@ mailing list. There is a page full of logos (some missing) at https://pulsar.apache.org/powered-by/ While that is a good starting place there

Re: [DISCUSS] cut pulsar-client-go 0.7.0 release

Are you volunteering to roll this release? If so then you should look at the PR and decide if you want to include it. Sent from my iPhone > On Oct 21, 2021, at 6:52 PM, Chris Kellogg wrote: > > What's the policy for waiting on PRs to merge? I was hoping to cut a > release sometime next week

Re: Revote: Pulsar website concepts

Hi - Great choices. Thank you Melissa. Here are my preferences in order: 1, 3B, 3A, and 2. I think that the body text should be slightly larger - roughly 90% of the heading in size. I agree about larger icons. We can “bikeshed” about other adjustments later after picking the design. All The

[ANNOUCEMENT] Welcome to our newest PMC Member - Yu Liu!

Hi everyone, The Apache Pulsar Project Management Committee (PMC) has invited Yu Liu (https://github.com/anonymitaet) as a member of the PMC and we are pleased to announce that she has accepted. She is very active in the community and organizes the documentation-related work of the community

Re: Missing check on .jar files committed to the source repo

> On Dec 3, 2021, at 11:45 AM, Michael Marshall wrote: > >> Automated checks are useful because we are human and we usually miss to >> validate this kind of boring stuff. > > +1 I think it sounds appropriate to add an automated check. If a use > case arises where we need to add compiled

Re: [DISCUSS] How to handle stale PRs

I think that any Pulsar committer ought to close any PR that is more than one year old. That would clear about 75 from the backlog. The OP should be informed and if they are still interested then they can discuss it here. So when a stale PR is closed we should suggest that the OP subscribe to

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

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 / http

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?

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

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 2021, 21

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

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: >> -

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

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 >

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

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

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

I’m making progress here, but I need help getting the pulsarbot GH secret into the pulsar-site repository. If that secret can be shared directly to me then I can fully test before adding my PR. Thanks, Dave > On Nov 17, 2021, at 3:57 PM, Dave Fisher wrote: > > I’m going to wor

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

s/publish-website.sh > > > -- > Matteo Merli > > > On Wed, Nov 17, 2021 at 12:29 PM Dave Fisher wrote: >> >> Show me where the code is that commits to the asf-site branch. >> >>> On Nov 17, 2021, at 12:25 PM, Matteo Merli wrote: >>> >

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

nd we need to ear more voices. >> >> Enrico >> >> Il Mer 17 Nov 2021, 19:28 Sijie Guo ha scritto: >> >>> I think we should have a PIP for this. Because this impacts all the >>> developers who are making documentation changes. >>> &g

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

te the new repository I will copy all of the asf-site branch which will take care of transferring the parts of the site not actively being built. Regards, Dave > > > -- > Matteo Merli > > > On Wed, Nov 17, 2021 at 12:46 PM Dave Fisher wrote: >> >&g

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

/confluence/display/INFRA/git+-+.asf.yaml+features > > Regards, > Dave > >> >> >> -- >> Matteo Merli >> >> >> On Wed, Nov 17, 2021 at 12:46 PM Dave Fisher wrote: >>> >>> If we change ORIGIN_REPO[1] to point to a new puls

[DISCUSS] New repository for website - pulsar-site

Hi - There are two efforts happening in the community around website refresh. (1) Docusaurus upgrades. (2) New web design. There is an effort to eliminate all the extra commits in the asf-site branch of the main repository. In that thread I proposed a new repository for the website. We can

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

m not saying that we shouldn't go this way, but it would be kind of a >> pain for someone and we need to ear more voices. >> >> Enrico >> >> Il Mer 17 Nov 2021, 19:28 Sijie Guo ha scritto: >> >>> I think we should have a PIP for this. Because

Re: Size of Asf-site branch in Pulsar repo

Hi - > On Oct 29, 2021, at 12:02 PM, Matteo Merli wrote: > > The Pulsar website is getting published through a CI job that updates > the generated HTML files and commits them in the Pulsar repo, in a > separate branch ('asf-site'). From there the site is immediately > visible on the web. > >

Re: Creating Good Release notes

> On Dec 2, 2021, at 3:11 AM, Enrico Olivelli wrote: > > Hello community, > > There is an open discussion on the Pulsar 2.9.0 release notes PR: > https://github.com/apache/pulsar/pull/12425 In reading through the comments there I’m noticing these main themes. (1) Wanting to standardize /

[Website] CI - Pulsar Website Build takes a long time

Hi - I noticed some things about the website build. https://github.com/apache/pulsar/actions/workflows/ci-pulsar-website-build.yaml (1) It runs for nearly 2 hours. (2) If it exceeds 2 hours then it is canceled. (3) It runs every 6 hours. We share runners with all of the ASF. I think we need

Re: [DISCUSS] Pulsar Protocol For Client Timeouts and Creating Producers

> On Dec 1, 2021, at 10:21 AM, Michael Marshall wrote: > > Following up here, I am still in need of reviews for PR [0]. It > introduces an important clarification to the Pulsar Protocol Spec. > Please take a look, if you are able. > > [0] - https://github.com/apache/pulsar/pull/12948 I

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

e. > > Best, > Dianjin Wang > > > On Thu, Dec 9, 2021 at 2:34 PM Sijie Guo wrote: > >> Hi Dave, >> >> Will follow up tomorrow morning (Pacific Time). >> >> - Sijie >> >> On Wed, Dec 8, 2021 at 9:35 PM Dave Fisher wrote: >>

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

This is great news! However the ending of the blog post [1] does not follow the Apache Way This bullet point is misleading and serves to split the community. > • Join the 2022 Pulsar Ambassador Program and work directly with Pulsar PMCs > and top contributors to co-host events, promote new

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

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 critical

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

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

ooked 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: Status of Pulsar 2.9.0 and starting 2.9.1

>> "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 published 2.9.0 at >>> htt

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

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

eople 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 us g

Log4j 2.16.0 a more complete fix to Log4Shell

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

Re: [DISCUSS] How to handle stale PRs

elp make our >>> committers more efficient. >>> >>> - Michael >>> >>> >>> On Fri, Dec 3, 2021 at 1:25 PM Jonathan Ellis wrote: >>>> >>>> Agreed. >>>> >>>> I don't think I understand tison's objecti

Re: [DISCUSS] How to handle stale PRs

gt;> Matteo Merli >>>> >>>> >>>> On Wed, Dec 15, 2021 at 1:05 PM Michael Marshall >>>> wrote: >>>>> >>>>> I am +1 for closing PRs that are over a year old. >>>>> >>>>> Does anyone

Re: [DISCUSS] How to handle stale PRs

is their 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 wr

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

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 situation >>> isn't likely

  1   2   3   4   >