@Jordan Zimmerman <[email protected]>  I have looked again into
https://issues.apache.org/jira/browse/ZOOKEEPER-3803
It is an issue to be resolved on ZooKeeper.

@Cameron McKenzie <[email protected]>
Regarding CURATOR-570 <https://issues.apache.org/jira/browse/CURATOR-570> if
we have some kind of non manual reproducer it would be easier to
investigate.
It is a long standing issue IIUC, so maybe it is not a blocker for cutting
5.1.

The only issue on 5.1 is fixing a regression.
Maybe I can do some housekeeping and check for instance if we have third
party dependencies to upgrade and to upgrade to Apache Parent Pom

Regards
Enrico


Il giorno mer 24 giu 2020 alle ore 00:41 Cameron McKenzie <
[email protected]> ha scritto:

> 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 <
> [email protected]> wrote:
>
> > I'll have a look at ZOOKEEPER-3803
> >
> > > On Jun 23, 2020, at 6:34 AM, Enrico Olivelli <[email protected]>
> > 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
> >
> >
>

Reply via email to