3.4.13 rc0 is out (see the vote thread here <https://lists.apache.org/thread.html/7322fa9489421e2ada868691da6eb988a826479c41a152662a676dd0@%3Cdev.zookeeper.apache.org%3E>), please try it and vote.
On Thu, Jun 21, 2018 at 8:50 PM, Michael Han <h...@apache.org> wrote: > I have limited bandwidth recently so it would take a while before I can > get back to ZOOKEEPER-2184 (for master/3.5 version). That however should > not block 3.4.13 release. > > I am preparing the release candidate for 3.4.13 release, will send out > email to dev list for vote soon. > > On Mon, Jun 18, 2018 at 9:54 AM, Molnár Andor <an...@nu.hu> wrote: > >> Michael is waiting for the master version of ZOOKEEPER-2184 to be >> committed. >> >> I think I've addressed all the issues, so there shouldn't be any blockers >> anymore. >> >> >> Andor >> >> >> >> >> >> On 06/18/2018 04:22 PM, Patrick Hunt wrote: >> >>> I'm just back from vacation so I may have missed it - Michael any >>> progress >>> on this? Should we/can we start the release cycle? If not what's the >>> blocker? >>> >>> Regards, >>> >>> Patrick >>> >>> On Tue, Jun 5, 2018 at 7:22 AM Michael Han <h...@apache.org> wrote: >>> >>> Perhaps you can commit the 3.5/trunk changes for 2184 prior to the 3.4 >>>>>> >>>>> release? >>>> >>>> Sounds good, I'll take another look at the port and commit it this week >>>> if >>>> no other issues. >>>> >>>> On Tue, Jun 5, 2018 at 12:44 AM, Patrick Hunt <ph...@apache.org> wrote: >>>> >>>> +1 - sounds good. 2959 and 2184 will be good to get out to users. >>>>> >>>>> Perhaps you can commit the 3.5/trunk changes for 2184 prior to the 3.4 >>>>> release? Just to ensure that we didn't miss anything and the releases >>>>> are >>>>> consistent, at least initially. >>>>> >>>>> Regards, >>>>> >>>>> Patrick >>>>> >>>>> >>>>> On Sat, Jun 2, 2018 at 12:59 AM Michael Han <h...@apache.org> wrote: >>>>> >>>>> ZOOKEEPER-2184 is now merged and I think we are good to prepare a >>>>>> >>>>> release >>>> >>>>> now given many eger users waiting for ZOOKEEPER-2184. I am also >>>>>> >>>>> interested >>>>> >>>>>> to take the role of RM for next release as I committed ZOOKEEPER-2184 >>>>>> >>>>> (and >>>>> >>>>>> witnessed the commit of ZOOKEEPER-2959 :). >>>>>> >>>>>> I took a look at other 3.4.x issues, there are no blocking issues for >>>>>> >>>>> now. >>>>> >>>>>> The next release will contain 16 resolved issues most of which are bug >>>>>> fixes. >>>>>> >>>>>> >>>>>> On Tue, May 22, 2018 at 9:09 PM, Michael Han <h...@apache.org> wrote: >>>>>> >>>>>> I am reviewing ZOOKEEPER-2184, and hope to merge it in next few days. >>>>>>> I'll also try to review and clean up some of the top pending requests >>>>>>> >>>>>> and >>>>> >>>>>> merge those in 3.4 as appropriate. I think it's a good idea to cut >>>>>>> >>>>>> another >>>>>> >>>>>>> release after ZK-2184 is in (ZK-2959 was already committed two weeks >>>>>>> >>>>>> ago), >>>>>> >>>>>>> as this is a long awaited feature and many users want it. >>>>>>> >>>>>>> On Mon, May 21, 2018 at 10:21 AM, Patrick Hunt <ph...@apache.org> >>>>>>> >>>>>> wrote: >>>>> >>>>>> We've made solid progress on the next 3.4 release >>>>>>>> http://bit.ly/1UCURuM >>>>>>>> >>>>>>>> In particular Alexander committed a change which is marked as a >>>>>>>> >>>>>>> blocker: >>>>> >>>>>> http://bit.ly/2LlVCbk >>>>>>>> Notice there are two blockers - Andor has been working with the >>>>>>>> >>>>>>> community >>>>>> >>>>>>> to resolve ZOOKEEPER-2184 >>>>>>>> >>>>>>>> After these two issues are addressed it looks like a reasonable >>>>>>>> >>>>>>> update >>>> >>>>> to >>>>>> >>>>>>> push. Does anyone have time to look at the serious/major issues that >>>>>>>> >>>>>>> are >>>>> >>>>>> attached to the release? >>>>>>>> >>>>>>>> Thoughts? >>>>>>>> >>>>>>>> Patrick >>>>>>>> >>>>>>>> >>>>>>> >>>>>> -- >>>>>> Cheers >>>>>> Michael >>>>>> >>>>>> >> >
