Re: [DISCUSSION] Pulsar maturity model assessment

Short answers inline after a very quick review. Sent from my iPhone > On Aug 28, 2018, at 5:35 PM, Matteo Merli wrote: > >> On Tue, Aug 28, 2018 at 5:04 PM Dave Fisher wrote: >> >> Hi - >> >> The contributing guide is a 404 on the website and I don’t see it on the >> menus. (Is it translated

Re: [DISCUSSION] Pulsar maturity model assessment

On Tue, Aug 28, 2018 at 5:04 PM Dave Fisher wrote: > Hi - > > The contributing guide is a 404 on the website and I don’t see it on the > menus. (Is it translated? I thought I saw an initial commit for it > yesterday. The PR is still not merged. Waiting for some flaky tests on CI to let it go th

Re: [DISCUSSION] Pulsar maturity model assessment

Hi - The contributing guide is a 404 on the website and I don’t see it on the menus. (Is it translated? I thought I saw an initial commit for it yesterday.) The descriptions on the team page are a little off - Members are both Committers and PPMC members. Please make that distinct. (In the ASF

RE: [DISCUSSION] Pulsar maturity model assessment

Great work! +1 Nozomi 差出人: Matteo Merli 送信日時: 2018年8月28日 15:43:24 宛先: dev@pulsar.incubator.apache.org 件名: [DISCUSSION] Pulsar maturity model assessment I have started a draft of the maturity model assessment. You can find it on the wiki: https://github.com/apac

Jenkins build is unstable: pulsar-master #758

See

Build failed in Jenkins: pulsar-master #756

See Changes: [jiazhai] Fixed few links in contact and download pages (#2458) -- [...truncated 1.10 MB...] Progress (1): 1.1 kBDownloaded: http://repositor

Re: [DISCUSSION] Pulsar maturity model assessment

Great work, Matteo! +1; #shipit - Sijie On Mon, Aug 27, 2018 at 11:43 PM Matteo Merli wrote: > I have started a draft of the maturity model assessment. > > You can find it on the wiki: > > https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar > > Please r

Build failed in Jenkins: pulsar-master #755

See Changes: [jiazhai] Support compaction options in Go client (#2449) -- [...truncated 994.42 KB...] [INFO] Pulsar Functions :: Proto-shaded ... SUCCESS [ 6.

Re: Accidently pushed a change to branch-1.22

Hi - Got it. I just wanted it clarified. Thanks for bringing it up here! Regards, Dave Sent from my iPhone > On Aug 28, 2018, at 9:18 AM, Ivan Kelly wrote: > > Dave (Fischer), > > It was to the release branch, not the release tag, so confusing users > shouldn't be a problem. > > -Ivan > >>

Re: Accidently pushed a change to branch-1.22

Dave (Fischer), It was to the release branch, not the release tag, so confusing users shouldn't be a problem. -Ivan On Tue, Aug 28, 2018 at 6:11 PM, Matteo Merli wrote: > I would say to leave it there. If someone will want to to a 1.22.2 release > it would be a good idea to include it. > > > >

Re: Accidently pushed a change to branch-1.22

On Tue, Aug 28, 2018 at 9:10 AM Dave Fisher wrote: > What was released as 1.22 is still tagged and available as such in Git? > > Reasoning is you don’t want confusion about what was truly released. > > It depends on how users might pick up 1.22. > Yes, the release is still tagged as `v1.22.1-inc

Re: Accidently pushed a change to branch-1.22

I would say to leave it there. If someone will want to to a 1.22.2 release it would be a good idea to include it. On Tue, Aug 28, 2018 at 5:28 AM Ivan Kelly wrote: > Hi folks, > > I accidently pushed a change to branch-1.22 to fix #2401. > > > https://github.com/apache/incubator-pulsar/commit

Re: Accidently pushed a change to branch-1.22

What was released as 1.22 is still tagged and available as such in Git? Reasoning is you don’t want confusion about what was truly released. It depends on how users might pick up 1.22. Regards, Dave Sent from my iPhone > On Aug 28, 2018, at 9:05 AM, David Kjerrumgaard wrote: > > If the bug i

Re: Accidently pushed a change to branch-1.22

If the bug is also in the 1.22 code base, which appears to be the case, then you should leave it in. On Tue, Aug 28, 2018 at 5:28 AM, Ivan Kelly wrote: > Hi folks, > > I accidently pushed a change to branch-1.22 to fix #2401. > > https://github.com/apache/incubator-pulsar/commit/ > 92b809784f631

Build failed in Jenkins: pulsar_release_nightly_snapshot #188

See Changes: [guosijie] Issue #2330: change getTopicName in MultiTopicsConsumer (#2346) [guosijie] Added Reader.HasNext in Go client (#2450) [github] Add multi-topic and regex consumer in Go clien

Accidently pushed a change to branch-1.22

Hi folks, I accidently pushed a change to branch-1.22 to fix #2401. https://github.com/apache/incubator-pulsar/commit/92b809784f631bc6b72cc1116761e8fac02ef41c Should I revert immediately? It's a pretty straightforward change given what the bug was. -Ivan

Jenkins build is unstable: pulsar-master #754

See

Build failed in Jenkins: pulsar-master #753

See Changes: [github] [Schema] Provide a generic record interface for representing a typed [guosijie] Fixed {{pulsar.version}} into {{pulsar:version}} in few pages (#2455) [guosijie] Fix flake in DiscoveryServiceTe