We are close! There are currently 4 issues remaining targeted to 3.5.2. ZOOKEEPER-2247 was mentioned as desired for 3.5.2. Flavio and Rakesh, do you think this can get closed down and committed soon? If so, I will hold up the release.
ZOOKEEPER-1460 has a fix committed to branch-3.5, but it remains open to track a back-port to branch-3.4. At this point, I will close the issue, targeted only to 3.5.2, and create a separate issue targeted to 3.4.9 for specifically tracking that back-port. ZOOKEEPER-2366 and ZOOKEEPER-2380 are reviewed and +1'd already. I will commit them before creating the release candidate. --Chris Nauroth On 6/21/16, 12:05 PM, "Chris Nauroth" <[email protected]> wrote: >I'd like to propose a deadline of 12 noon Thursday, 6/23 PST. If anyone >needs a later deadline, please let me know. > >--Chris Nauroth > > > > >On 6/21/16, 10:08 AM, "Patrick Hunt" <[email protected]> wrote: > >>1045 is currently only against 3.4. Once we have that solid I would think >>we'd port it to 3.5 and include it in a future release (3.5.3?) >> >>Patrick >> >>On Tue, Jun 21, 2016 at 10:02 AM, Flavio Junqueira <[email protected]> >>wrote: >> >>> ZK-2366 and ZK-2247 should be ready for commit shortly. We aren't >>> including ZK-1045 in 3.5.2, right? >>> >>> -Flavio >>> >>> > On 21 Jun 2016, at 17:43, Patrick Hunt <[email protected]> wrote: >>> > >>> > Can we set a deadline/date for the release? It's fine to have >>>blockers >>> > while we're still in alpha. We should cut a release for folks that >>>want >>> to >>> > get access to the latest. >>> > >>> > Patrick >>> > >>> > On Mon, Jun 20, 2016 at 5:17 PM, Chris Nauroth >>><[email protected] >>> > >>> > wrote: >>> > >>> >> I am about to take the plunge and start deferring all JIRA issues >>> >> currently targeted to 3.5.2 into 3.5.3. I will likely start doing >>>this >>> >> sometime around 12 noon PST on Tuesday, 6/21. Nearly every issue in >>> this >>> >> list will be deferred: >>> >> >>> >> https://s.apache.org/Y0jP >>> >> >>> >> I know we have a few blocker and critical issues still under active >>>code >>> >> review that we want for 3.5.2. I'll keep those in. >>> >> >>> >> --Chris Nauroth >>> >> >>> >> >>> >> >>> >> >>> >> On 5/12/16, 2:44 PM, "Patrick Hunt" <[email protected]> wrote: >>> >> >>> >>> Hi Chris. +1 on that. I believe it's imperative that we get >>>3.5.2-alpha >>> >>> out >>> >>> and continue to drive towards stability. I'll work with Michael to >>>get >>> >>> 2405 >>> >>> finalized. >>> >>> >>> >>> Patrick >>> >>> >>> >>> On Tue, May 10, 2016 at 2:54 PM, Chris Nauroth < >>> [email protected]> >>> >>> wrote: >>> >>> >>> >>>> When we last discussed a ZooKeeper 3.5.2-alpha release candidate, >>>we >>> >>>> wanted to take time to knock down current blocker and critical >>>issues. >>> >>>> Since then, we've heard interest from multiple users that they >>>would >>> >>>> like >>> >>>> to see a 3.5.2-alpha release soon. At this point, I'd like to >>>push >>> the >>> >>>> majority of remaining open issues ahead to 3.5.3 in the interest >>>of >>> >>>> expediting a release candidate. >>> >>>> >>> >>>> I currently see 12 blockers and 18 criticals remaining targeted to >>> >>>> 3.5.2. >>> >>>> I count 67 fixed issues already committed for 3.5.2, and I think >>> that's >>> >>>> plenty of content to justify proceeding with a release. I'd like >>>to >>> ask >>> >>>> everyone to please consider pushing your issues ahead to 3.5.3 and >>> limit >>> >>>> the remaining 3.5.2 issues only to what you consider to be >>>must-haves. >>> >>>> Speaking for myself, I think the really important remaining ones >>>are >>> >>>> ZOOKEEPER-2366 (hampers uptake of dynamic reconfig), >>>ZOOKEEPER-2380 >>> >>>> (potential stability problem) and ZOOKEEPER-2405 (security risk). >>>I >>> >>>> will >>> >>>> focus my code review time on these, but I could even be convinced >>>to >>> >>>> defer >>> >>>> these. >>> >>>> >>> >>>> Please keep in mind that we can aim for a quicker 3.5.3-alpha >>>release >>> >>>> after this if your favorite issue doesn't quite make it into >>> >>>> 3.5.2-alpha. >>> >>>> >>> >>>> Please let me know your thoughts on the plan, and thank you. >>> >>>> >>> >>>> --Chris Nauroth >>> >>>> >>> >> >>> >> >>> >>> > >
