I'm still using Curator 2.6.0 because of the CURATOR-188 issue. Any idea when it will be fixed ?
On Tue, Apr 21, 2015 at 5:17 PM, Ricardo Ferreira <[email protected]> wrote: > I'd also like to see CURATOR-192 included. It seems an easy enough fix > that can still be part of a next release. > > On Tue, Apr 21, 2015 at 5:09 PM, Mike Drob <[email protected]> wrote: > >> I'd like to see CURATOR-204. I'll check later today if there is an >> apache-parent-17 that we should be using instead of 16, even. >> >> Maybe we can also do CURATOR-164, I'll try to finish it up this week. >> >> CURATOR-164 would be nice, but I'm not sure how those look from a >> compatibility viewpoint. >> >> We should also pay attention to the ask in CURATOR-193 and make sure that >> we don't run into anything similar for 2.8.0. >> >> Mike >> >> On Tue, Apr 21, 2015 at 9:01 AM, Jordan Zimmerman < >> [email protected]> wrote: >> >>> I think we have enough for a 2.8.0 release. Discuss now, please, if >>> you’d like to see any other issues in the next release. >>> >>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12329300 >>> >>> -Jordan >>> >> >> >
