Re: Lingering Geode 1.10.0 release issues

Unfortunately I'm finding that our gradle build scripts are also using string comparisons on Geode versions.  You can't do something like     (oldGeodeVersion >= "1.7.0") and expect that to work when the version is "1.10.0" On 9/27/19 10:12 AM, Bruce Schuchardt wrote: Some

Re: Lingering Geode 1.10.0 release issues

Some backward-compatibility tests are using string comparisons on versions, which isn't working well with our new "1.10.0".  Others are converting version strings into numbers, so 1.10.0 becomes 1100.  That's working okay but is also a time-bomb.  I'm changing the tests to use a new

Re: Lingering Geode 1.10.0 release issues

Did the 'merge release branch into master and develop' go smoothly? On Fri, Sep 27, 2019 at 9:27 AM Dick Cavender wrote: > If you try and brew update to Geode 1.10.0 you won't get it until our > 1.10.0 homebrew PR > gets > through their

Re: Lingering Geode 1.10.0 release issues

Bruce has picked up GEODE-7250. -Dan On Fri, Sep 27, 2019 at 9:27 AM Dick Cavender wrote: > If you try and brew update to Geode 1.10.0 you won't get it until our > 1.10.0 homebrew PR > gets > through their checks and their Jenkins servers

Lingering Geode 1.10.0 release issues

If you try and brew update to Geode 1.10.0 you won't get it until our 1.10.0 homebrew PR gets through their checks and their Jenkins servers seem to be having problems this week so this is still in flight. On geode develop I've had to revert