Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/256

[Discuss] Member Launcher API

Hello, all. There has been some discussion [1] on the JIRA regarding GEODE-3584, to reduce code duplication and improve clarity across LocatorLauncher, ServerLauncher, and AbstractLauncher classes. In no particular order, I think the following would be a good starting point for refactoring

Re: Next release: 1.5.0

Just checking in as we’re approaching the end of February. We’ve finished around 200 issues and enhancements with 3 documentation updates open [1]. Is this a good time for another release? Any takers to do the release management tasks for 1.5.0? Anthony [1]

Re: Next release: 1.5.0

Status on the 3 doc issues: GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered GEODE-4101: redirect-output - Dave, in process, on track GEODE-3948: client timeout - Dave, in process. Probably on track - will keep you posted On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker

Re: [Discuss] Member Launcher API

You might want to also consider moving these Launcher classes from org.apache.geode.distributed to some other package such as one of the following: 1) org.apache.geode 2) org.apache.geode.api 3) org.apache.geode.launcher 4) org.apache.geode.management 5) org.apache.geode.process The existing

Geode unit tests completed in 'develop/AcceptanceTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/322