Hello all,
These are the additional commits going into 2.3.2
https://github.com/apache/pulsar/compare/v2.3.1...branch-2.3
Best,
Jerry
On Sun, May 19, 2019 at 11:10 PM Jerry Peng
wrote:
> Shivji,
>
> We can probably do that given that there aren't any major merge conflicts
>
> Best,
>
> J
Shivji,
We can probably do that given that there aren't any major merge conflicts
Best,
Jerry
On Sun, May 19, 2019 at 11:07 PM PengHui Li wrote:
> +1
>
> Shivji Kumar Jha 于2019年5月20日周一 下午12:12写道：
>
> > HI Jerry,
> >
> > Can we include this in 2.3.2 please?
> > https://github.com/apache/pulsa
+1
Shivji Kumar Jha 于2019年5月20日周一 下午12:12写道：
> HI Jerry,
>
> Can we include this in 2.3.2 please?
> https://github.com/apache/pulsar/pull/4136
>
> This is critical because prometheus output is not parsed by some monitoring
> tools (telegraf for instance).
>
> Regards,
> Shivji Kumar Jha
> http:/
HI Jerry,
Can we include this in 2.3.2 please?
https://github.com/apache/pulsar/pull/4136
This is critical because prometheus output is not parsed by some monitoring
tools (telegraf for instance).
Regards,
Shivji Kumar Jha
http://www.shivjijha.com/
+91 8884075512
On Sat, May 18, 2019 at 5:07 P
+1
On Sat, May 18, 2019 at 2:43 AM Jerry Peng
wrote:
> Hello all,
>
> I think it might be time for a 2.3.2 release. There are already quite a
> few PRs that have gone in for 2.3.2:
>
> https://github.com/apache/pulsar/milestone/23
>
> What does everyone else think?
>
> Best,
>
> Jerry
>
Hello all,
I think it might be time for a 2.3.2 release. There are already quite a
few PRs that have gone in for 2.3.2:
https://github.com/apache/pulsar/milestone/23
What does everyone else think?
Best,
Jerry
