> I was actually not thinking of changing the denomination of 2.11. On
> one hand, it could make sense for being the first Java 17 release, but
> on the other, we'd be releasing 2 LTSs super close between each other
> and we'd have to support 1 release more for the time being.
>
> I'd like to hea
urfreespace merged PR #103:
URL: https://github.com/apache/pulsar-site/pull/103
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@pulsar.a
RobertIndie commented on issue #105:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/105#issuecomment-1149609173
I think we may need to add reflection support here. Users only need to
provide the required class name and auth parameters to generate the
IAuthentication.
--
This is
urfreespace merged PR #104:
URL: https://github.com/apache/pulsar-site/pull/104
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@pulsar.a
+1 (binding)
Enrico
Il giorno mer 8 giu 2022 alle ore 05:39 PengHui Li
ha scritto:
>
> +1
>
> Penghui
> On Jun 8, 2022, 09:32 +0800, Rui Fu , wrote:
> > +1
> >
> > Best,
> >
> > Rui Fu
> > 在 2022年6月8日 +0800 04:51，Neng Lu ，写道：
> > > Hi All,
> > >
> > > +1 (non-binding)
> > >
> > > On Tue, Jun 7,
Hi, Enrico.
Thank review, I changed it.
Thanks,
Baodi Shi
> On Jun 8, 2022, at 11:3828, PengHui Li wrote:
>
> I have left one last minute comment, can you please take a look ? then
> I will post my +1
michaeljmarshall commented on PR #104:
URL: https://github.com/apache/pulsar-site/pull/104#issuecomment-1150077264
@urfreespace - can you describe the problem you are fixing here? This PR was
merged without any helpful description. Thanks.
--
This is an automated message from the Apache G
I would suggest first having some concrete implementations in a separate
repo.
After verifying its functionality and performance, then we can move into
the main pulsar repo.
On Fri, Jun 3, 2022 at 5:09 AM Enrico Olivelli wrote:
> Overall I agree with the proposal.
> I left some minor feedback on
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` -> regular release
> > * `3.2` -> regular release
> > * `4.0` ->
--
Matteo Merli
On Wed, Jun 8, 2022 at 12:33 AM Haiting Jiang wrote:
>
> > I was actually not thinking of changing the denomination of 2.11. On
> > one hand, it could make sense for being the first Java 17 release, but
> > on the other, we'd be releasing 2 LTSs super close between each other
>
rdhabalia opened a new issue, #268:
URL: https://github.com/apache/pulsar-helm-chart/issues/268
### Motivation
Right now, [chart
dynamically](https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/zookeeper-statefulset.yaml#L140)
creates zk cluster with zk pods i
> 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`
> Schedules always slip. Would you say that if the 3.x feature releases take
> too long with these hypothetical dates that 3.5 would be dropped in order to
> release 4.0 on schedule?
Yes, there needs to be clarity for the users on when releases are to
be expected, even more so for LTS releases.
rdhabalia opened a new pull request, #269:
URL: https://github.com/apache/pulsar-helm-chart/pull/269
Fixes #268
### Motivation
Right now, [chart
dynamically](https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/zookeeper-statefulset.yaml#L140)
creates zk
Dear Pulsar community,
Our engineers from StreamNative would like to contribute to improving the
broker load balancer.
To collaborate with the community from the early phase, we opened a slack
channel and summarized the improvement ideas in this document.
pulsar slack channel : *#broker-load-bal
> From the code-freeze point, to minimize the risk of delaying the
> release, only bug fixes involving a regression of behavior compared to
> a previous release should be allowed. Occasional exceptions will be
> possible after higher scrutiny of the change.
It's a frequent point of discussion to d
1. We can compose some charts/tables as https://endoflife.date/python on
the Pulsar website to help people understand the time frame.
2. Regarding the LTS release proposal, one thing I need some clarification
is will the LTS release include major new features compared to last release?
For exam
+1 (binding)
Thanks,
Hang
Baodi Shi 于2022年6月8日周三 22:23写道：
>
> Hi, Enrico.
>
> Thank review, I changed it.
>
>
> Thanks,
> Baodi Shi
>
> > On Jun 8, 2022, at 11:3828, PengHui Li wrote:
> >
> > I have left one last minute comment, can you please take a look ? then
> > I will post my +1
>
Thank you everyone!
Dezhi
-- --
??:
"dev"
htt
The PIP passes with 3 bindings +1: Hang Chen, Penghui Li and Enrico.
I will start working, @Penghui Li Please help to move to wiki.
Thanks,
Baodi Shi
> On Jun 9, 2022, at 10:2029, Hang Chen wrote:
>
> +1 (binding)
>
> Thanks,
> Hang
>
> Baodi Shi 于2022年6月8日周三 22:23写道：
>>
>> Hi, Enrico.
>
20 matches
Mail list logo
