Do we want to do anything with https://issues.apache.org/jira/browse/CURATOR-570?
I have spent some time investigating, and have proposed a fix, but I'm not sure if it is actually worthwhile. I think the main issues encountered in the bug have already been fixed via CURATOR-551, which is already released. cheers On Tue, Jun 23, 2020 at 11:56 PM Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > I'll have a look at ZOOKEEPER-3803 > > > On Jun 23, 2020, at 6:34 AM, Enrico Olivelli <eolive...@gmail.com> > wrote: > > > > Hi guys, > > with 5.0 we introduced a nasty regression and I have committed a fix. > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CURATOR%20AND%20fixVersion%20%3D%205.1.0 > > > > It looks like it is too little stuff for a release to be cut. > > > > Do you have other items to commit before cutting the release ? > > > > We should release it a 5.1.0 because the fix implies a breaking change on > > an API, introduced with 5.0. > > > > It looks like this issue on ZooKeeper deserves a fix on Curator > > https://issues.apache.org/jira/browse/ZOOKEEPER-3803 > > > > Does anyone has time to work on it on Curator ? > > > > In my opinion we can wait until the next week for a release. > > > > Best regards > > Enrico > >
