By "strange" I mean "not familiar with" :)
- Hongchao Deng

> Subject: Re: zookeeper-3.4.7 timeframe
> From: [email protected]
> Date: Sun, 19 Apr 2015 17:26:34 +0100
> To: [email protected]
> 
> What's strange about the issues resolved?
> 
> -Flavio
> 
> > On 18 Apr 2015, at 20:19, Hongchao Deng <[email protected]> wrote:
> > 
> > TBH the commits from 3.4.6 to latest look a little strange to me. I don't 
> > think I could take that responsibility. I would like to do the RM job for 
> > 3.5.2 :)
> > - Hongchao Deng
> > 
> >> From: [email protected]
> >> Date: Fri, 17 Apr 2015 08:30:13 -0700
> >> Subject: Re: zookeeper-3.4.7 timeframe
> >> To: [email protected]; [email protected]
> >> 
> >> One of our new committers perhaps? Hongchao or Raul interested?
> >> 
> >> Patrick
> >> 
> >> On Fri, Apr 17, 2015 at 1:20 AM, Flavio Junqueira <
> >> [email protected]> wrote:
> >> 
> >>> I have volunteered to RM 3.4.7, but I'm more than happy to pass if anyone
> >>> else wants to do a release.
> >>> -Flavio
> >>> 
> >>> 
> >>>     On Friday, April 17, 2015 8:22 AM, Michi Mutsuzaki <
> >>> [email protected]> wrote:
> >>> 
> >>> 
> >>> 
> >>> Hi Konstantin,
> >>> 
> >>> Yes, I'd like us to start preparing for 3.4.7 soon. We have 36 out of
> >>> 44 issues resolved. Any volunteer to manage the 3.4.7 release? I'd
> >>> like to get more committers to get familiarized with the release
> >>> process.
> >>> 
> >>> On Thu, Apr 16, 2015 at 4:25 PM, Konstantin Boudnik <[email protected]>
> >>> wrote:
> >>>> Hello ZK team!
> >>>> 
> >>>> We are looking into upgrading ZK to 3.4.6 in the coming Bigtop 1.0
> >>> release.
> >>>> However, as expressed in BIGTOP-1468, we are concerned a bit about
> >>> deviating
> >>>> from 'official release only' policy we had so far. But as explained
> >>> above,
> >>>> there are a few issues that are we need to address if we want to switch:
> >>>>   ZOOKEEPER-1911
> >>>>   ZOOKEEPER-2064
> >>>>   ZOOKEEPER-1506 (potentially)
> >>>> 
> >>>> I was wondering if you guys are planning on releasing 3.4.7 soon, that
> >>> will
> >>>> hopefully address at least the top two issues? I am not subscribed to
> >>>> [email protected] so I'd appreciate if you can include [email protected]
> >>> into
> >>>> your reply as well.
> >>>> 
> >>>> Thanks in advance!
> >>>> Cos
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >                                       
> 
                                          

Reply via email to