I thought we had moved GEODE-3052 to a later release, given that we have
a work around for this.
--Udo
On 6/10/17 10:15, Anthony Baker wrote:
Status update:
We have 2 issues left: GEODE-3054 and GEODE-3052. We also had a clean run of
the Geode-release jenkins job. So as soon as we can finish off these issues
and get another clean run through Jenkins I’ll create a release candidate. How
does early next week sound?
Anthony
On Jun 8, 2017, at 5:38 PM, Anthony Baker <[email protected]> wrote:
Sounds good. Please cherry-pick these changes onto release/1.2.0 when ready.
Anthony
On Jun 8, 2017, at 3:15 PM, Jared Stewart <[email protected]> wrote:
I think we probably ought to include GEODE-3045
<https://issues.apache.org/jira/browse/GEODE-3045> as well.
On Jun 8, 2017, at 3:12 PM, Kenneth Howe <[email protected]> wrote:
I think we should also include the fix for GEODE-3054 in 1.2. This is a bug
that was introduced in the recent changes to the Gfsh parser, and affects
Windows pathnames specified in options to gfsh commands.
https://issues.apache.org/jira/browse/GEODE-3054
<https://issues.apache.org/jira/browse/GEODE-3054>
The fix is currently in testing.
On Jun 8, 2017, at 2:23 PM, Bruce Schuchardt <[email protected]> wrote:
I'd like to include the fix for GEODE-3052 in the 1.2 release. It's under
review now and has passed new tests and is in precheckin testing.
https://issues.apache.org/jira/browse/GEODE-3052
"Restarting 2 locators within 1s of each other causes potential locator split
brain"
