Any updates? Are we comfortable getting this cut?

Thanks,
C


On Tue, Feb 11, 2014 at 8:00 PM, Camille Fournier <cami...@apache.org>wrote:

> Yeah I think we should put a bullet in this.
>
>
> On Tue, Feb 11, 2014 at 7:56 PM, Michi Mutsuzaki <mi...@cs.stanford.edu>wrote:
>
>> Should we move ZOOKEEPER-1833 to 3.4.7 now and get 3.4.6 out?
>>
>> On Sat, Jan 11, 2014 at 3:17 PM, Michi Mutsuzaki <mi...@cs.stanford.edu>
>> wrote:
>> > +1
>> >
>> > On Sat, Jan 11, 2014 at 10:18 AM, Patrick Hunt <ph...@apache.org>
>> wrote:
>> >> +1, great idea re setting a deadline now that we're close (keep in
>> >> mind we an always do further fix releases). Kudos on the windows work,
>> >> love to see it!
>> >>
>> >> Patrick
>> >>
>> >> On Sat, Jan 11, 2014 at 9:40 AM, Camille Fournier <cami...@apache.org>
>> wrote:
>> >>> +1
>> >>> On Jan 11, 2014 10:18 AM, "Flavio Junqueira" <fpjunque...@yahoo.com>
>> wrote:
>> >>>
>> >>>> We only have one blocker for 3.4.6 now which is ZOOKEEPER-1833. I'd
>> like
>> >>>> to get the windows build to pass on jenkins, and we have made a lot
>> of
>> >>>> progress already. Although we have focused on the windows build,
>> most of
>> >>>> the changes were small bugs that don't manifest as easily in other
>> >>>> platforms, so it has been a chance to clean up the test cases.
>> Thanks a lot
>> >>>> for the great community work, Germán, Rakesh, Michi et al.
>> >>>>
>> >>>> To avoid postponing the 3.4.6 release even further, it sounds like a
>> good
>> >>>> idea to put a deadline on ZOOKEEPER-1833. I would say that if we
>> don't have
>> >>>> ZOOKEEPER-1833 done by the end of January, we should cut a release
>> and push
>> >>>> some of the work to 3.4.7. Any concern here?
>> >>>>
>> >>>> -Flavio
>>
>
>

Reply via email to