Il Sab 15 Mag 2021, 07:45 Ammar Khaku <[email protected]> ha scritto:
> Our team manages ZK ensembles as well as thin wrappers around Curator that > are used across a number of teams at the company. A lot of those teams use > spring-cloud-zookeeper 2.2.x, which depends on Curator 4. We also make > heavy use of Exhibitor on the server side. Upgrading to Curator 5+ would be > a fairly large effort across a few teams, so we're going to be on Curator 4 > for a while and it would be nice to be able to pull in patches in the > meantime. > I see. We could cut a release with that fix. Let's see if other people in the community agree. Cutting a release involves a few steps that must be carried on by the community as a whole, because we need people to test the release candidate Enrico > -Ammar > > On Fri, May 14, 2021 at 10:31 PM Enrico Olivelli <[email protected]> > wrote: > > > Ammar > > Usually we cut releases only from the latest version of the code. > > > > Can't you upgrade to latest Curator? > > I am going to cut a new release next week > > > > Enrico > > > > Il Sab 15 Mag 2021, 01:42 Ammar Khaku <[email protected]> ha > scritto: > > > > > Hi, we recently merged in a fix for > > > https://issues.apache.org/jira/browse/CURATOR-526 with > > > https://github.com/apache/curator/pull/382. I'd love to be able to use > > > that > > > soon in the 4.x branch - do y'all plan on cutting a release soon? Note > > that > > > I don't see a 4.x branch in Github so we'll need to make sure that > commit > > > is included in a potential new 4.3.1 release. > > > > > > Let me know how I can help! Happy to take on any grunt work to get this > > > moving. > > > > > > -Ammar > > > > > >
