; Is it right?
- Original Message -
From: Enrico Olivelli
To: DevZooKeeper , maoling199210...@sina.com
Subject: Re: Re: Time to think about a 3.6.0 release?
Date: 2019-07-15 21:55
Justin,
I think that current master has already plenty of new features and it is
worth to start thinking to a rele
ture. Look at an example of redis - the tracing
>> feature(PR-994). if having another time, integrating with opentracing
>> sounds a very good idea. - replace jute with thrift or PB may be put
>> into the 4.0.0 when wanting to break the backward compatibility? And at the
>> 4.0.0,
ure. Look at an example of redis
> > - the tracing feature(PR-994). if having another time, integrating with
> opentracing sounds a very good idea.
> > - replace jute with thrift or PB may be put into the 4.0.0 when wanting
> to break the backward compatibility? And at the 4.0.0, implemen
ea.
>
Thanks,
Andor
>
>
> - Original Message -
> From: Fangmin Lv
> To: dev@zookeeper.apache.org
> Subject: Re: Time to think about a 3.6.0 release?
> Date: 2019-06-26 07:33
>
> It's great to have a 3.6.0 release, currently all the FB contributed
> featu
good idea.
>
>
>
> - Original Message -
> From: Fangmin Lv
> To: dev@zookeeper.apache.org
> Subject: Re: Time to think about a 3.6.0 release?
> Date: 2019-06-26 07:33
>
> It's great to have a 3.6.0 release, currently all the FB contributed
> features has been
.
- Original Message -
From: Fangmin Lv
To: dev@zookeeper.apache.org
Subject: Re: Time to think about a 3.6.0 release?
Date: 2019-06-26 07:33
It's great to have a 3.6.0 release, currently all the FB contributed
features has been running inside FB for more than a month, so it
should be stable enough
Il mer 26 giu 2019, 11:20 Norbert Kalmar ha
scritto:
> Sorry, correction, I just followed up on ZOOKEEPER-2136, patch is not
> ready, and maybe not even a blocker for 3.6.0?
>
I would drop 3.6.0 label from ZOOKEEPER-2136, I have already commented
(with Patrick) on that issue about setting
Sorry, correction, I just followed up on ZOOKEEPER-2136, patch is not
ready, and maybe not even a blocker for 3.6.0?
On Wed, Jun 26, 2019 at 11:16 AM Norbert Kalmar
wrote:
> Hi Fangmin,
>
> I checked all 3 PRs, looks like they pretty much reviewed, some minor
> questions remain.
> But we have
Hi Fangmin,
I checked all 3 PRs, looks like they pretty much reviewed, some minor
questions remain.
But we have 302 tickets open where fixVersion is 3.6.0, good news is only 1
blocker (ZOOKEEPER-2136), which already has a patch. I'll see that this
blocker gets committed.
There is also 9 critical
Thanks Fangmin for pointing out these issues.
I’ll take a look at them once I have some free cycles - currently on holiday. :)
We should consider compiling a list of 3.6 blockers in Jira similar what we had
for 3.5.
Andor
> On 2019. Jun 26., at 1:26, Fangmin Lv wrote:
>
> It's great to
It's great to have a 3.6.0 release, currently all the FB contributed
features has been running inside FB for more than a month, so it
should be stable enough for community to use.
Also I agreed with Patrick's point to review all flags and consider to turn
on by default.
For the pending PRs, the
Good idea. Agree on including anything we've postponed to a new cycle - the
patch from mapr is an obvious one to consider.
We should also look at things we've disabled by default and consider
whether we can turn them on by default. If not why not, and what can we do
to fix this in a subsequent
On Persistent/Recursive watches: I’m willing to rebase, etc if there’s
confidence it will be merged.
Jordan Zimmerman
> On Jun 15, 2019, at 10:59 AM, Andor Molnar wrote:
>
> Hi Enrico!
>
> Very good point, I entirely support the idea.
>
> Question to Friends@Facebook
Hi Enrico!
Very good point, I entirely support the idea.
Question to Friends@Facebook and Twitter contributors: how many outstanding
Jiras/PRs do you have which you would like to see in 3.6?
I'd also like to highlight the long outstanding PR from Mapr:
Hi Zookeepers !
I checked on JIRA and it seems that master in good shape, no real blockers
that mine the stability of the code.
We have plenty of cool pull requests almost ready to be merged (mostly from
Facebook friends and Twitter fork)
Current master branch is full of great features in
15 matches
Mail list logo
