Let's not vote until there is a call to vote, folks...
On Thu, Jan 16, 2020, 18:31 Jacob Barrett wrote:
> I would characterize my vote as 0. I really don’t care either way. Just
> sharing I think they have no value in a release.
>
> > On Jan 16, 2020, at 6:08 PM, Owen Nichols wrote:
> >
> >
I would characterize my vote as 0. I really don’t care either way. Just sharing
I think they have no value in a release.
> On Jan 16, 2020, at 6:08 PM, Owen Nichols wrote:
>
> Geode PMC has 52 members. If this were a vote, it looks like the results
> would have been:
> +1: 2 (Anthony, Dan)
>
Geode PMC has 52 members. If this were a vote, it looks like the results would
have been:
+1: 2 (Anthony, Dan)
-1: 1 (Jake)
If the next release manager were to go ahead and put geode-benchmarks in the
Geode 1.12.0 source release, at least 3 PMC members would need to be willing to
vote +1. So
> If geode-benchmarks is included, that implies that an RC cannot be
approved until reviewers can successfully run the benchmark suite from the
geode-benchmarks source distribution. Is that what we want?
I think it would be sufficient to run the tests of the benchmarks, eg
./gradlew test
> Deplo
When voting on RC candidates, PMC members "are required to download the signed
source code package, compile it as provided, and test the resulting executable
on their own platform”.
If geode-benchmarks is included, that implies that an RC cannot be approved
until reviewers can successfully run
I suspect there may be a recent membership/distribution/locator or even
security change that has caused LocatorUDPSecurityDUnitTest to start
failing with a suspect string.
Any ideas what might have broken this? I'm busy working on other dunit
tests so it'll be a while before I can look into this.
The language “sufficient for a user to build and test the release” suggest to
me that "./gradlew test” should work (i.e. don’t release *just* src). It would
be a slippery slope to construe this guideline as a mandate to include any and
all tools, scripts, etc that may ever have been used in con
We are supposed to be including all of the source necessary to test Geode
in the source release [1] - I think that would include benchmarks as well.
I don't really see any compelling reason *not* to include the benchmarks,
let's go ahead and get them into our source release!
[1]
http://www.apache
Hi team
I am working with geode 1.4 and trying to connect from client outside of EAAS
to Geode server on EAAS.
I am managed to connect to the external ip of the locator (10.xxx.xxx.xxx) but
when the client gets the list of geode servers to work with it gets it with the
internal ip (192.xx.xx.xx
