Dave,
Il giorno ven 3 dic 2021 alle ore 04:16 Li Li
ha scritto:
> +1 Good idea, we will take a look and do some optimizations
>
> Thanks,
> LiLi
>
> > On Dec 3, 2021, at 5:04 AM, Dave Fisher wrote:
> >
> > Hi -
> >
> > I noticed some things about the website build.
> https://github.com/apache/p
The Project Management Committee (PMC) for Apache Pulsar
has invited Michael Marshal to become a committer and we are pleased to
announce that he has accepted.
Michael contributed a lot of interesting additions to the project and he is
very active in the community.
Being a committer enables easi
First I agree with Jonathan that we should perform some changes with
the original PR descriptions.
Then, classifying these PRs is also necessary, otherwise the release notes
would be meaningless. There are a lot of PRs that should be classfied in
Misc part of https://github.com/apache/pulsar/pull/
+1
Thanks,
LiLi
> On Dec 1, 2021, at 2:26 PM, Hang Chen wrote:
>
> +1
>
> Thanks,
> Hang
>
> Lan Liang 于2021年12月1日周三 下午2:14写道：
>>
>> +1, Thanks for your work.
>>
>>
>>
>>
>>
>>
>> Best Regards,
>> Lan Liang
>> On 11/29/2021 17:17，Enrico Olivelli wrote：
>> +1
>>
>>
>>
>>
>>
>> Enr
+1 Good idea, we will take a look and do some optimizations
Thanks,
LiLi
> On Dec 3, 2021, at 5:04 AM, Dave Fisher wrote:
>
> 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
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 to
> There is already a label `release/note-required` that is being used to
> call out PR/issues when compiling the release notes.
+1 I think we should use this label more--it has only been used 12 times [0].
[0] -
https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2Fnote-required+
-
There is already a label `release/note-required` that is being used to
call out PR/issues when compiling the release notes.
--
Matteo Merli
On Thu, Dec 2, 2021 at 10:07 AM Michael Marshall wrote:
>
> > I would suggest that the PMC needs to provide more support to
> > whoever the RM for a rele
> I would suggest that the PMC needs to provide more support to
> whoever the RM for a release is. RMs are perhaps the most
> valuable committers we have and let’s try not to overburden them
> with extra tasks.
+1 - this is especially important if we want to have more
frequent releases.
I see two
> 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 added
> 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 / re
I don't think a raw dump of PRs is right for release notes even if the
commit messages are perfectly written by God. It's too low level for
almost everyone, and the people who really do want commit-level detail can
just use git, which is a better tool for exploring history than a static
text file.
wangshu3000 opened a new pull request #183:
URL: https://github.com/apache/pulsar-helm-chart/pull/183
…n new k8s version, this change keep backward compatibility for lower
kubernetes version
Fixes #157
### Motivation
The ingress api extensions/v1beta1 version will not
Hello community,
There is an open discussion on the Pulsar 2.9.0 release notes PR:
https://github.com/apache/pulsar/pull/12425
I have created the block of release notes by downloading the list of PR
using some GitHub API.
Then I have manually classified:
- News and Noteworthy: cool things in the
wangshu3000 opened a new pull request #182:
URL: https://github.com/apache/pulsar-helm-chart/pull/182
Fixes #177
### Motivation
When deploying the pulsar helm chart, if i open the dashboard indicator,
it'll be failed, and show message say the component is unknown field. Reason
massakam commented on pull request #182:
URL:
https://github.com/apache/pulsar-client-node/pull/182#issuecomment-984501591
@lipeining Thank you for your contribution. The change looks good to me.
But why is the destination branch `branch-1.3` instead of `master`? Do you
want v1.3.x
Yuri,
IIUC with this change the client will control which metrics are reported by
the broker ?
I am not sure it is a good idea, because metrics are usually managed by the
owners of the brokers, who sometimes are not the same who run the clients.
Also, I am not sure if this way it is possible for
17 matches
Mail list logo
