It's past the announced deadline and we have enough votes to close the vote.
Voting status
==
+1: 5 binding votes, 3 non-binding votes
* Udo Kohlmeyer (PMC member)
* Juan Ramos (PMC member)
* Dave Barnes (PMC member)
* Jinmei Liao (PMC member)
* John Blum (PMC member)
+0: zero votes
-0:
@Jens, @Owen,
With the discussion to cut a 1.11 release, I think we are safe in saying
that change can make it into that release and a 1.10.1 is not required.
UNLESS there is another third part
This fix was only included in the 1.9.2 release, because this is the
version that Spring Data
Hi Owen,
As this vote is now closing I'd like to quickly comment on your
(non-binding) vote.
I understand your concern that these changes are not currently on the 1.10
branch, however I think that concern is somewhat premature as we may never
end up with a 1.10.1 release. If that does happen we
+1
Built Spring Data for Apache Geode on 1.9.2 with success.
On Tue, Oct 22, 2019 at 1:28 PM Jinmei Liao wrote:
> +1
>
> On Tue, Oct 22, 2019 at 11:47 AM Dave Barnes wrote:
>
> > +1
> > Downloaded, successfully built Geode and Geode-Native docs form source.
> >
> > On Tue, Oct 22, 2019 at
+1
On Tue, Oct 22, 2019 at 11:47 AM Dave Barnes wrote:
> +1
> Downloaded, successfully built Geode and Geode-Native docs form source.
>
> On Tue, Oct 22, 2019 at 2:17 AM Ju@N wrote:
>
> > +1,
> >
> > Downloaded and built from source, created two clusters with multiple
> > members and verified
+1
Downloaded, successfully built Geode and Geode-Native docs form source.
On Tue, Oct 22, 2019 at 2:17 AM Ju@N wrote:
> +1,
>
> Downloaded and built from source, created two clusters with multiple
> members and verified WAN replication (along with some gateway related
> commands) work
+1
Downloaded source code, build and ran tests.
Started a cluster and was able to execute basic operations.
Compiled and ran examples
Validated pipeline was run successfully for the SHA we are shipping
On Tue, Oct 22, 2019 at 2:17 AM Ju@N wrote:
> +1,
>
> Downloaded and built from source,
+1,
Downloaded and built from source, created two clusters with multiple
members and verified WAN replication (along with some gateway related
commands) work properly.
Best regards.
On Mon, Oct 21, 2019 at 8:04 PM Udo Kohlmeyer wrote:
> +1,
>
> Checked that WAR's are generated for geode-web
+1,
Checked that WAR's are generated for geode-web and geode-web-api.
Also ran set of examples and tests from Spring Data Geode (Moore), to
confirm that it has not broken functionality.
--Udo
On 10/21/19 8:20 AM, Jens Deppe wrote:
Since the deadline has expired without enough votes, I am
Since the deadline has expired without enough votes, I am going to extend
it for another 48(ish) hours until 8am PST, Wednesday , 23rd October.
Thanks
--Jens
On Tue, Oct 15, 2019 at 10:47 AM Jens Deppe wrote:
> Hello Geode Dev Community,
>
> This is a release candidate for Apache Geode version
+1
built and ran tests for native client on windows.
-michael
On Wed, Oct 16, 2019 at 2:21 PM Blake Bender wrote:
> Okay I'm convinced we're okay, so switching to a +1. Standard PEBKAC error
> here, I managed to produce a native client build which was missing the jar
> file we use for a
No worries and thanks for taking the time to look at the bits!
--Jens
On Wed, Oct 16, 2019 at 2:21 PM Blake Bender wrote:
> Okay I'm convinced we're okay, so switching to a +1. Standard PEBKAC error
> here, I managed to produce a native client build which was missing the jar
> file we use for
Okay I'm convinced we're okay, so switching to a +1. Standard PEBKAC error
here, I managed to produce a native client build which was missing the jar
file we use for a whole bunch of tests, so all failed.
Thanks,
Blake
On Wed, Oct 16, 2019 at 1:03 PM Blake Bender wrote:
> I'm a -1 on this
I'm a -1 on this one, for the time being, sorry. I ran native client
integration tests against it on my dev workstation and am seeing an
inordinate number of failures. It's gonna take me some time to understand
what's going on, but I'll update everyone shortly as to whether I think we
have a
Hi there Owen,
Whilst I share your concern of consistence, the Geode user community did
not notice that the artifacts changed from war -> jar (GEODE-7241). The
Spring Data Geode project is currently the only downstream project which
discovered this regression.
As Spring Data Geode 2.2 will
I am concerned that this 1.9.2 release contains features that are not in 1.10:
GEODE-7241 Publish war artifacts for geode-web , geode-web-api and
geode-web-management to Maven Central.
GEODE-7261 Fix compatibility with launching geode-web (admin REST API) when
Spring 5.x jars are on the
Hello Geode Dev Community,
This is a release candidate for Apache Geode version 1.9.2.RC1.
Thanks to all the community members for their contributions to this release!
Please do a review and give your feedback, including the checks you
performed.
Voting deadline:
3PM PST Sun, October 20 2019.
17 matches
Mail list logo
