> In other words, can I just replace Curator jars on an application built for > 4.x?
As long as your Curator 4.x app targets ZooKeeper 3.5.x you should be binary compatible. However, there are a very few breaking changes (and thus the major version number increment) that we document here: https://github.com/apache/curator/blob/master/src/site/confluence/breaking-changes.confluence <https://github.com/apache/curator/blob/master/src/site/confluence/breaking-changes.confluence> (the formatting will be better when we generate the website). Note: we have a new module that tests against ZooKeeper 3.5.x: https://github.com/apache/curator/tree/master/curator-test-zk35 Is there a particular concern you have? -Jordan > On May 19, 2020, at 12:10 AM, Enrico Olivelli <[email protected]> wrote: > > Cameron, > > thanks for putting this together. > It is not clear to me if this version is 100% binary compatible with 4.x. > In other words, can I just replace Curator jars on an application built for > 4.x? > This is very important in order to be able to upgrade to 5.x > > > Enrico > > Il Mar 19 Mag 2020, 02:58 Cameron McKenzie <[email protected]> ha > scritto: > >> Hello, >> >> This is the vote for Apache Curator version 5.0.0 >> >> *** Please download, test and vote within approx. 72 hours >> >> Note that we are voting upon the source (tag) and binaries are provided for >> convenience. >> >> Link to release notes: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12347240 >> >> Staging repo: >> https://dist.apache.org/repos/dist/dev/curator/5.0.0/ >> >> Binary artifacts: >> https://repository.apache.org/content/repositories/orgapachecurator-1049 >> >> The tag to be voted upon: >> >> https://gitbox.apache.org/repos/asf?p=curator.git;a=commit;h=e0bb2fb251dd0ad3a75d829ad94d6f9e02c5461c >> >> Curator's KEYS file containing PGP keys we use to sign the release: >> http://www.apache.org/dist/curator/KEYS >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >>
