Apache Geode 1.14.4 RELEASE

[Dick Cavender]

Today is the voting deadline and we have enough to close the vote so we're 
doing that ahead of the afternoon deadline. 

Voting status
==
+1: 4 binding votes
* Eric Shu  (PMC member)
* Donal Evans  (PMC member)
* Dave Barnes (PMC member)
* Dan Smith (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.14.4.RC1 has passed the vote and we will finalize the release 
shortly.

Thanks everyone for the great work!

-Dick Cavender

[VOTE] Apache Geode 1.14.4.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.14.4.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 Fri, March 18 2022

Please note that we are voting upon the source tag:
rel/v1.14.4.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.4

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.14.4.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1137

GitHub:
https://github.com/apache/geode/tree/rel/v1.14.4.RC1
https://github.com/apache/geode-examples/tree/rel/v1.14.4.RC1
https://github.com/apache/geode-native/tree/rel/v1.14.4.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.14.4.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.14.4.RC1 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1137
 build runAll

Regards
Dick Cavender

[ANNOUNCE] Apache Geode 1.13.8

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.13.8.

Geode is a data management platform that provides a database-like consistency
model, reliable transaction processing and a shared-nothing architecture
to maintain very low latency performance with high concurrency processing.

Apache Geode 1.13.8 contains a number of bug fixes.
Users are encouraged to upgrade to the latest 1.14.x release (currently 1.14.3).
For the full list of changes please review the release notes at:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.8

Release artifacts and documentation can be found at the project website:
https://geode.apache.org/releases/
https://geode.apache.org/docs/guide/113/about_geode.html

We would like to thank all the contributors that made the release possible.

Regards,

Dick Cavender on behalf of the Apache Geode team

Apache Geode 1.13.8 RELEASE

[Dick Cavender]

Today is the voting deadline and we have enough to close the vote.

Voting status
==
+1: 3 binding votes
* Dan Smith  (PMC member)
* Donal Evans  (PMC member)
* Nabarun Nag (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.13.8.RC1 has passed the vote and we will finalize the release 
shortly.

Thanks everyone for the great work!

-Dick Cavender

[ANNOUNCE] Apache Geode 1.12.9

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.12.9.

Geode is a data management platform that provides a database-like consistency
model, reliable transaction processing and a shared-nothing architecture
to maintain very low latency performance with high concurrency processing.

Apache Geode 1.12.9 contains a number of bug fixes.
Users are encouraged to upgrade to the latest 1.14.x release (currently 1.14.3).
For the full list of changes please review the release notes at:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.9

Release artifacts and documentation can be found at the project website:
https://geode.apache.org/releases/
https://geode.apache.org/docs/guide/112/about_geode.html

We would like to thank all the contributors that made the release possible.

Regards,

Dick Cavender on behalf of the Apache Geode team

[VOTE] Apache Geode 1.13.8.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.13.8.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 Tue, March 15 2022.

Please note that we are voting upon the source tag:
rel/v1.13.8.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.8

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.13.8.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1135

GitHub:
https://github.com/apache/geode/tree/rel/v1.13.8.RC1
https://github.com/apache/geode-examples/tree/rel/v1.13.8.RC1
https://github.com/apache/geode-native/tree/rel/v1.13.8.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.13.8.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.13.8.RC1 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1135
 build runAll

Regards
Dick Cavender

Apache Geode 1.12.9 RELEASE

[Dick Cavender]

Today is the voting deadline and we have enough to close the vote.

Voting status
==
+1: 4 binding votes
* Dan Smith  (PMC member)
* Donal Evans  (PMC member)
* Nabarun Nag (PMC member)
* Dave Barnes (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.12.9.RC1 has passed the vote and we will finalize the release 
shortly.

Thanks everyone for the great work!

-Dick Cavender

[VOTE] Apache Geode 1.12.9.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.12.9.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 Wed, March 9 2022.

Please note that we are voting upon the source tag:
rel/v1.12.9.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.9

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.12.9.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1131

GitHub:
https://github.com/apache/geode/tree/rel/v1.12.9.RC1
https://github.com/apache/geode-examples/tree/rel/v1.12.9.RC1
https://github.com/apache/geode-native/tree/rel/v1.12.9.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.12.9.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.12.9.RC1 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1131
 build runAll

Regards
Dick Cavender

[ANNOUNCE] Apache Geode 1.14.3

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.14.3.

Geode is a data management platform that provides a database-like consistency
model, reliable transaction processing and a shared-nothing architecture
to maintain very low latency performance with high concurrency processing.

Apache Geode 1.14.3 contains a number of bug fixes.
Users are encouraged to upgrade to this latest release.
For the full list of changes please review the release notes at:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.3

Release artifacts and documentation can be found at the project website:
https://geode.apache.org/releases/
https://geode.apache.org/docs/guide/114/about_geode.html

We would like to thank all the contributors that made the release possible.

Regards,
Dick Cavender on behalf of the Apache Geode team

Apache Geode 1.14.3 RELEASE

[Dick Cavender]

Today is the voting deadline and we have enough to close the vote.

Voting status
==
+1: 4 binding votes
* Donal Evans  (PMC member)
* Udo Kohlmeyer (PMC member)
* Dave Barnes (PMC member)
* Eric Shu (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.14.3.RC1 has passed the vote and we will finalize the release 
shortly.

Thanks everyone for the great work!

-Dick Cavender

[VOTE] Apache Geode 1.14.3.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.14.3.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 Tuesday, January 25 2022

Please note that we are voting upon the source tag:
rel/v1.14.3.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.3

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.14.3.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1128

GitHub:
https://github.com/apache/geode/tree/rel/v1.14.3.RC1
https://github.com/apache/geode-examples/tree/rel/v1.14.3.RC1
https://github.com/apache/geode-native/tree/rel/v1.14.3.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.14.3.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.14.3.RC1 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1128
 build runAll

Regards
Dick Cavender

Apache Geode 1.13.7 RELEASE

[Dick Cavender]

Today is the voting deadline and we have enough to close the vote.

Voting status
==
+1: 4 binding votes
* Kirk Lund (PMC member)
* Donal Evans  (PMC member)
* Nabarun Nag (PMC member)
* Dave Barnes (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.13.7.RC1 has passed the vote and we will finalize the release 
shortly.

Thanks everyone for the great work!

-Dick Cavender

[ANNOUNCE] Apache Geode 1.13.7

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.13.7.

Geode is a data management platform that provides a database-like consistency
model, reliable transaction processing and a shared-nothing architecture
to maintain very low latency performance with high concurrency processing.

Apache Geode 1.13.7 contains a number of bug fixes.
Users are encouraged to upgrade to the latest 1.14.x release (currently 1.14.2).
For the full list of changes please review the release notes at:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.7

Release artifacts and documentation can be found at the project website:
https://geode.apache.org/releases/
https://geode.apache.org/docs/guide/113/about_geode.html

We would like to thank all the contributors that made the release possible.

Regards,
Dick Cavender on behalf of the Apache Geode team

[VOTE] Apache Geode 1.13.7.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.13.7.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 Thursday, January 20 2022.

Please note that we are voting upon the source tag:
rel/v1.13.7.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.7

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.13.7.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1126

GitHub:
https://github.com/apache/geode/tree/rel/v1.13.7.RC1
https://github.com/apache/geode-examples/tree/rel/v1.13.7.RC1
https://github.com/apache/geode-native/tree/rel/v1.13.7.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.13.7.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.13.7.RC1 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1126
 build runAll

Regards
Dick Cavender

Apache Geode 1.12.8 RELEASE

[Dick Cavender]

Today is the voting deadline and we have enough to close the vote.

Voting status
==
+1: 3 binding votes
* Dave Barnes (PMC member)
* Donal Evans  (PMC member)
* Alexander Murmann (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.12.8.RC1 has passed the vote and we will finalize the release 
shortly.

Thanks everyone for the great work!

-Dick Cavender

[VOTE] Apache Geode 1.12.8.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.12.8.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 Thu, January 13 2022.

Please note that we are voting upon the source tag:
rel/v1.12.8.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.8

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.12.8.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1124

GitHub:
https://github.com/apache/geode/tree/rel/v1.12.8.RC1
https://github.com/apache/geode-examples/tree/rel/v1.12.8.RC1
https://github.com/apache/geode-native/tree/rel/v1.12.8.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.12.8.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.12.8.RC1 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1124
 build runAll

Regards
Dick Cavender

RE: [DISCUSS] batch patch release voting

[Dick Cavender]

+1 for batching them. 

Is it implied with a +1 vote that all the releases have been checked or can you 
only vote on a single release if that's all you checked? We can define this 
when we send out the vote email. 

-Original Message-
From: Robert Houghton  
Sent: Thursday, December 2, 2021 11:26 AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] batch patch release voting

In the case where its one change being backported all over, I say batch up the 
vote.

From: Owen Nichols 
Date: Wednesday, December 1, 2021 at 11:46 AM
To: dev@geode.apache.org 
Subject: [DISCUSS] batch patch release voting Geode's N-2 support policy can 
lead to "waves" of patch releases.  For example, 1.12.6, 1.13.5 and 1.14.1 are 
all likely this month, with many of the same fixes in each.

Some open source projects group waves of patch releases into a single 
announcement.  It might be nice to do this for Geode.

For voting, does anyone have any preference whether to still hold three 
separate votes, or would it be ok to vote on a batch of patch releases at once? 
 If so, would 3 days still be enough time for the voting deadline?

[ANNOUNCE] Apache Geode 1.12.5

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.12.5.

Apache Geode is a data management platform that provides a
database-like consistency model, reliable transaction processing and a
shared-nothing architecture to maintain very low latency performance
with high concurrency processing.

This patch release includes a few bug fixes.
For the full list of changes please review the release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.5

The release artifacts can be downloaded from the project website:
https://geode.apache.org/releases/

The release documentation is available at:
https://geode.apache.org/docs/guide/112/about_geode.html

We would like to thank all the contributors that made the release possible.

Regards,
Dick Cavender on behalf of the Apache Geode team

Apache Geode 1.12.5 RELEASE

[Dick Cavender]

Today is the voting deadline and we have enough to close the vote.

Voting status
==
+1: 4 binding votes
* Dave Barnes (PMC member)
* Dan Smith (PMC member)
* Nabarun Nag (PMC member)
* Donal Evans  (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.12.5.RC4 has passed the vote and we will finalize the release 
shortly.

Thanks everyone for the great work!

-Dick Cavender

[VOTE] Apache Geode 1.12.5.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.12.5.RC4. 
Earlier RC1, RC2 and RC3 had issues. 
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 Mon, October 25 2021.

Please note that we are voting upon the source tag:
rel/v1.12.5.RC4

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.5

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.12.5.RC4/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1113

GitHub:
https://github.com/apache/geode/tree/rel/v1.12.5.RC4
https://github.com/apache/geode-examples/tree/rel/v1.12.5.RC4
https://github.com/apache/geode-native/tree/rel/v1.12.5.RC4
https://github.com/apache/geode-benchmarks/tree/rel/v1.12.5.RC4

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.12.5.RC4 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1113
 build runAll

Regards
Dick Cavender

[ANNOUNCE] Apache Geode 1.13.4

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.13.4 .

Apache Geode is a data management platform that provides a
database-like consistency model, reliable transaction processing and a
shared-nothing architecture to maintain very low latency performance
with high concurrency processing.

This patch release includes a few bug fixes.
For the full list of changes please review the release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.4

The release artifacts can be downloaded from the project website:
https://geode.apache.org/releases/

The release documentation is available at:
https://geode.apache.org/docs/guide/113/about_geode.html

We would like to thank all the contributors that made the release possible.

Regards,
Dick Cavender on behalf of the Apache Geode team

Apache Geode 1.13.4 RELEASE

[Dick Cavender]

It's past the announced deadline and we have enough votes to close the vote.

Voting status
==
+1: 3 binding votes
* Donal Evans  (PMC member)
* Dave Barnes (PMC member)
* Nabarun Nag (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1
votes and has the required majority of +1 votes.

Apache Geode 1.13.4.RC1 has passed the vote and we will finalize the
release shortly.

Thanks everyone for the great work!

-Dick Cavender

[VOTE] Apache Geode 1.13.4.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.13.4.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 Fri, July 30 2021
*NOTE: THIS IS AN  ABBREVIATED 2 DAY VOTE *

Please note that we are voting upon the source tag:
rel/v1.13.4.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.4

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.13.4.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1087

GitHub:
https://github.com/apache/geode/tree/rel/v1.13.4.RC1
https://github.com/apache/geode-examples/tree/rel/v1.13.4.RC1
https://github.com/apache/geode-native/tree/rel/v1.13.4.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.13.4.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew -PgeodeReleaseUrl=
https://dist.apache.org/repos/dist/dev/geode/1.13.4.RC1
-PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1087
build runAll

Regards
Dick Cavender

[ANNOUNCE] Apache Geode 1.12.4

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.12.4 .

Apache Geode is a data management platform that provides a
database-like consistency model, reliable transaction processing and a
shared-nothing architecture to maintain very low latency performance
with high concurrency processing.

While 1.13.X is currently the latest release of Apache Geode, Geode
1.12.4 brings a subset of bug fixes.

For the full list of changes please review the release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.4

The release artifacts can be downloaded from the project website:
https://geode.apache.org/releases/

The release documentation is available at:
https://geode.apache.org/docs/guide/112/about_geode.html

We would like to thank all the contributors that made the release possible.

Regards,
Dick Cavender on behalf of the Apache Geode team

[VOTE] Apache Geode 1.12.4.RC1

[Dick Cavender]

It's past the announced deadline and we have enough votes to close the vote.

Voting status
==
+1: 3 binding votes
* Donal Evans  (PMC member)
* Dan Smith (PMC member)
* Jens Deppe (PMC member)

+0: zero votes
  * Dave Barnes (PMC member)

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes
and has the required majority of +1 votes.

Apache Geode 1.12.4.RC1 has passed the vote and we will finalize the
release shortly.

Thanks everyone for the great work!

-Dick Cavender

[VOTE] Apache Geode 1.12.4.RC1

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.12.4.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 Mon, July 26 2021*

Please note that we are voting upon the source tag:
rel/v1.12.4.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.12.4

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.12.4.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1092

GitHub:
https://github.com/apache/geode/tree/rel/v1.12.4.RC1
https://github.com/apache/geode-examples/tree/rel/v1.12.4.RC1
https://github.com/apache/geode-native/tree/rel/v1.12.4.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.12.4.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew -PgeodeReleaseUrl=
https://dist.apache.org/repos/dist/dev/geode/1.12.4.RC1
-PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1092
build runAll

Regards
Dick Cavender

RE: [VOTE] Apache Geode 1.12.3.RC3

[Dick Cavender]

+1, built sources, reviewed gfsh version and NOTICE file. 

-Original Message-
From: Owen Nichols  
Sent: Friday, June 25, 2021 1:16 PM
To: dev@geode.apache.org
Subject: [VOTE] Apache Geode 1.12.3.RC3

Hello Geode Dev Community,

I'd like to propose a 1.12 patch release.

This is a release candidate for Apache Geode version 1.12.3.RC3.
Note: This is the first vote email due to a build issue with the first two RCs.
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 PDT Wed, June 30 2021.

Please note that we are voting upon the source tag:
rel/v1.12.3.RC3

Release notes:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FRelease%2BNotes%23ReleaseNotes-1.12.3data=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=COC6qmgWv5j2wbNa2S9RqYUAa%2FrDlgg2RGTJKAjSz1o%3Dreserved=0

Source and binary distributions:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2F1.12.3.RC3%2Fdata=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=XgAHS3QYH3C9DWd2dm5sNUvCvjM0rzzKQKbB5GTBNUk%3Dreserved=0

Maven staging repo:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1084data=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=TsGak5c0khVoce%2FpWTEIGGdLLkXPEzsBNHQ2mnDsL64%3Dreserved=0

GitHub:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Ftree%2Frel%2Fv1.12.3.RC3data=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=WJ6p%2FpT3DI4QcAIevOT42hqgQiUiXHpL1WDckRJtxUM%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-examples%2Ftree%2Frel%2Fv1.12.3.RC3data=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=%2B8bqK0BxCZpzOFyWuIR0C1smQC5QO%2BHXmjivWlbOXRA%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Ftree%2Frel%2Fv1.12.3.RC3data=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=Njso9ur87TRET5s4CF74VU%2FL9G8vxn2WkJkDpAAe1B8%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-benchmarks%2Ftree%2Frel%2Fv1.12.3.RC3data=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=zXKb8I1PEK1qV0FEcmkvpWSjV9fTTpQwJTqDJzZnNhA%3Dreserved=0

Pipelines:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-12-maindata=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=bfmJEqdxEGG2jXwWyf%2FedDq%2BvQZKFFdoVPuttz%2FhhrU%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-12-rcdata=04%7C01%7Cdickc%40vmware.com%7C046623914b164a75dc5c08d9381607ca%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637602489538121076%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=4KYYQ1royNCN1GFf2TN8txRln6OH4chU9RFc47hyX7M%3Dreserved=0

Geode's KEYS file containing PGP keys we use to sign the release:

RE: [VOTE] Apache Geode 1.13.3.RC2

[Dick Cavender]

+1 Built source distribution and reviewed LICENSE and NOTICE. 

-Original Message-
From: Owen Nichols  
Sent: Wednesday, June 23, 2021 11:56 AM
To: dev@geode.apache.org
Subject: [VOTE] Apache Geode 1.13.3.RC2

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.13.3.RC2.
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.

Expedited voting deadline:
3PM PST Thu, June 24 2021.

Please note that we are voting upon the source tag:
rel/v1.13.3.RC2

Release notes:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FRelease%2BNotes%23ReleaseNotes-1.13.3data=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618219677%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=MYV4CD%2BdOK%2B4jQsHf3LSRSXdiwOpqqOlpaIFLn8srI4%3Dreserved=0

Source and binary distributions:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2F1.13.3.RC2%2Fdata=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618219677%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=ZyX2oVKaTFRZTX7%2Bo2rfSlnk34v55rqtCudiHEHeDwg%3Dreserved=0

Maven staging repo:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1086data=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618229676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=CP9VwUEcNVn9Q9g88Z4bEBPE1IIdOpJxEzpmApOO0pc%3Dreserved=0

GitHub:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Ftree%2Frel%2Fv1.13.3.RC2data=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618229676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=2Xgciy7bBJtTJQg22IFLliB91LRIGl%2FNWZnnom%2F1K%2FU%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-examples%2Ftree%2Frel%2Fv1.13.3.RC2data=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618229676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=r4%2FuKeTGIQSzQnPUTaSlMBSxCyEWFur%2Fn7ODEmeU0so%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Ftree%2Frel%2Fv1.13.3.RC2data=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618229676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=htIU51k7pzTwviWFnI%2Bw4TFDZ2%2BYvi1ZdlJtn%2B%2Fh86Q%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-benchmarks%2Ftree%2Frel%2Fv1.13.3.RC2data=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618229676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=qksTwcNbloW4tBGminnDC8IqS6yblMHgUjSORAoltkw%3Dreserved=0

Pipelines:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-13-maindata=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618229676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=yDNO2DgtdG2rRcAfixL8FO5tbNelhOPmMYh98NGVeX0%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-13-rcdata=04%7C01%7Cdickc%40vmware.com%7C0e151145b43244624d4b08d936788a00%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637600713618229676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=jQo1GsLDugeAt2Ljd0gWpqRuUZ3QbneOUsiTcZ3%2BcN0%3Dreserved=0

Geode's KEYS file containing PGP keys we use to sign the release:

[ANNOUNCE] Apache Geode 1.13.2

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.13.2.

Apache Geode is a data management platform that provides a database-like
consistency model, reliable transaction processing and a shared-nothing
architecture to maintain very low latency performance with high concurrency
processing.

Geode 1.13.2 contains a number of improvements and bug fixes. This patch
release includes critical fixes if upgrading from an earlier version of
Geode. It also provides the ability to configure Geode appenders in
log4j2.xml. Localizes dates in Pulse queries. Improvements to
startup/shutdown. Performance improvements. Change apachegeode dockerhub
image to be based on BellSoft's Liberica JDK. Users are encouraged to
upgrade to this latest release.

For the full list of changes please review the release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.2

The release artifacts can be downloaded from the project website:
http://geode.apache.org/releases/

The release documentation is available at:
https://geode.apache.org/docs/guide/113/about_geode.html

Thanks to all the contributors that made the release possible.

Regards,

Dick Cavender on behalf of the Apache Geode team

Apache Geode 1.13.2 Release

[Dick Cavender]

The issue holding the Geode 1.13.2 release has been responsibly vetted and 
we're clear to close the voting!

Voting status
==
+1: 5 binding votes, 0 non-binding votes
* Donal Evans (NEW PMC member)
* Dave Barnes (PMC member)
* Mark Hansen (PMC member)
* Dan Smith (PMC member)
* Nabarun Nag (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.13.2 passes the vote so we'll work to finalize the release early 
next week.

Thanks everyone for the great work!

Dick Cavender

RE: [VOTE] Apache Geode 1.13.2.RC1

[Dick Cavender]

Thanks Donal- Holding 1.13.2 release until there is more information. 

-Original Message-
From: Donal Evans  
Sent: Monday, March 22, 2021 2:41 PM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.13.2.RC1

I'm okay with waiting until we know what the situation is with this register 
interest issue before releasing or scrapping this RC. Making a decision before 
we fully understand the consequences seems unwise.

From: Alexander Murmann 
Sent: Monday, March 22, 2021 1:59 PM
To: dev@geode.apache.org 
Subject: Re: [VOTE] Apache Geode 1.13.2.RC1

Sorry, everyone! We still haven't gotten to the bottom of the very slow 
registerInterest. More details should be coming in a ticket as we get closer to 
the root cause. Right now, we are seeing messages about delayed 
FetchBulkEntries and registerInterest taking over 5 minutes. That's resulting 
in the HARegionQueue filling up and eventually falling over.

I am not sure what's formally the best way forward with this vote. The best 
solution to me seems to put the release on hold till this issue is resolved. 
There is still a chance that this will turn out to be a case that has been in 
Geode for a while now. In that case we could ship this RC after all. If we find 
that we need to make changes to address this issue, we of course should have a 
new vote.

Do we need a vote to pause the release or can we just informally agree that 
waiting for this is the best course of action till someone voices concern about 
the downsides of this delay?

From: Dick Cavender 
Sent: Thursday, March 18, 2021 13:52
To: dev@geode.apache.org 
Subject: RE: [VOTE] Apache Geode 1.13.2.RC1

Update: Apache Geode 1.13.2.RC1 voting deadline is now: 3PM PST Monday, March 
22, 2021

-Original Message-
From: Alexander Murmann 
Sent: Thursday, March 18, 2021 1:23 PM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.13.2.RC1

I am sorry, can we get another 24 hours to analyze the long registerInterest 
calls, please? Thank you!

From: Dick Cavender 
Sent: Tuesday, March 16, 2021 13:56
To: dev@geode.apache.org 
Subject: RE: [VOTE] Apache Geode 1.13.2.RC1

Certainly! The new Apache Geode 1.13.2.RC1 voting deadline is now: 3PM PST 
Thurs, March 18, 2021

-Original Message-
From: Alexander Murmann 
Sent: Tuesday, March 16, 2021 1:46 PM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.13.2.RC1

 Can we please extend the vote for another 48 hours? We are investigating a 
potential issue in which registerInterest is taking over 5 minutes. It's still 
unclear what exactly is causing that, but some more time to investigate would 
be better than potentially shipping a bug like this.

From: Dick Cavender 
Sent: Thursday, March 11, 2021 13:34
To: dev@geode.apache.org 
Subject: [VOTE] Apache Geode 1.13.2.RC1

Hello Geode Dev Community,

It's been 4 months since the Apache Geode 1.13.1 release and there are a total 
48 important fixes on support/1.13 that the community would benefit from. The 
recently released v1.12.1 has 33 
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520GEODE%2520AND%2520fixVersion%2520%253D%25201.12.1%2520and%2520fixVersion%2520%253D%25201.13.2data=04%7C01%7Cdickc%40vmware.com%7C465cb7bfe3ef48f3ba2408d8ed7b2bd1%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637520460563321660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=phASixN3XVf1BvA7bgBP5FC73xyTw3zttfqaxOCtk5E%3Dreserved=0>
 fixes that are not released in 1.13. Based on this I propose release of an 
Apache Geode 1.13.2 based on the current support/1.13 branch. I'll volunteer to 
be the release manager for 1.13.2 and what follows is a release candidate for 
Apache Geode version 1.13.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 Tues, March 16, 2021

Please note that we are voting upon the source tag:
rel/v1.13.2.RC1

Release notes:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FRelease%2BNotes%23ReleaseNotes-1.13.2data=04%7C01%7Cdickc%40vmware.com%7C465cb7bfe3ef48f3ba2408d8ed7b2bd1%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637520460563321660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=%2Bzv9kTqSKyEssFT%2FEPtivSqn2WvCNLJydz7Q44QsD5c%3Dreserved=0

Source and binary distributions:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2F1.13.2.RC1%2Fdata=04%7C01%7Cdickc%40vmware.com%7C465cb7bfe3ef48f3ba2408d8ed7b2bd1%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637520460563321660%7CU

RE: [VOTE] Apache Geode 1.13.2.RC1

[Dick Cavender]

Update: Apache Geode 1.13.2.RC1 voting deadline is now: 3PM PST Monday, March 
22, 2021

-Original Message-
From: Alexander Murmann  
Sent: Thursday, March 18, 2021 1:23 PM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.13.2.RC1

I am sorry, can we get another 24 hours to analyze the long registerInterest 
calls, please? Thank you!

From: Dick Cavender 
Sent: Tuesday, March 16, 2021 13:56
To: dev@geode.apache.org 
Subject: RE: [VOTE] Apache Geode 1.13.2.RC1

Certainly! The new Apache Geode 1.13.2.RC1 voting deadline is now: 3PM PST 
Thurs, March 18, 2021

-Original Message-
From: Alexander Murmann 
Sent: Tuesday, March 16, 2021 1:46 PM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.13.2.RC1

 Can we please extend the vote for another 48 hours? We are investigating a 
potential issue in which registerInterest is taking over 5 minutes. It's still 
unclear what exactly is causing that, but some more time to investigate would 
be better than potentially shipping a bug like this.

From: Dick Cavender 
Sent: Thursday, March 11, 2021 13:34
To: dev@geode.apache.org 
Subject: [VOTE] Apache Geode 1.13.2.RC1

Hello Geode Dev Community,

It's been 4 months since the Apache Geode 1.13.1 release and there are a total 
48 important fixes on support/1.13 that the community would benefit from. The 
recently released v1.12.1 has 33 
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520GEODE%2520AND%2520fixVersion%2520%253D%25201.12.1%2520and%2520fixVersion%2520%253D%25201.13.2data=04%7C01%7Cdickc%40vmware.com%7C1f3f9f6af4d042d9f71708d8ea4ba9f3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637516957987317040%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=W1giTO8hlo2i3cA46teTAq1MAE4bOjIUKagnrxu2KnA%3Dreserved=0>
 fixes that are not released in 1.13. Based on this I propose release of an 
Apache Geode 1.13.2 based on the current support/1.13 branch. I'll volunteer to 
be the release manager for 1.13.2 and what follows is a release candidate for 
Apache Geode version 1.13.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 Tues, March 16, 2021

Please note that we are voting upon the source tag:
rel/v1.13.2.RC1

Release notes:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FRelease%2BNotes%23ReleaseNotes-1.13.2data=04%7C01%7Cdickc%40vmware.com%7C1f3f9f6af4d042d9f71708d8ea4ba9f3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637516957987327034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=izi7ybIS%2B9DX30ZCfzKjNr1D8hLXgTh6RB3%2BRkaWXyY%3Dreserved=0

Source and binary distributions:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2F1.13.2.RC1%2Fdata=04%7C01%7Cdickc%40vmware.com%7C1f3f9f6af4d042d9f71708d8ea4ba9f3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637516957987327034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=NwF6N%2B%2FMs%2B9gpxvkJEN2pdKUTabcYUtsmor%2Fs19mdOU%3Dreserved=0

Maven staging repo:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1079data=04%7C01%7Cdickc%40vmware.com%7C1f3f9f6af4d042d9f71708d8ea4ba9f3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637516957987327034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=VNVLazNa0QWDAAkfwQ8WWzoGJZK26hiXvwLWvQhmusw%3Dreserved=0

GitHub:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Ftree%2Frel%2Fv1.13.2.RC1data=04%7C01%7Cdickc%40vmware.com%7C1f3f9f6af4d042d9f71708d8ea4ba9f3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637516957987327034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=hK06qrI1kt%2BOvMb3o0uqVKFLhoKr9v5BYaw2mcbONoY%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-examples%2Ftree%2Frel%2Fv1.13.2.RC1data=04%7C01%7Cdickc%40vmware.com%7C1f3f9f6af4d042d9f71708d8ea4ba9f3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637516957987327034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=2qCa9rjAK9Ga21H6S%2FYoUCmQYoLga7TmnEx8CKMNxlU%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Ftree%2Frel%2Fv1.13.2.RC1data=04%7C01%7Cdickc%40vmware.com%7C1f3f9f6af4d042d9f71708d8ea4ba9f3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637516957987

RE: [VOTE] Apache Geode 1.13.2.RC1

[Dick Cavender]

Certainly! The new Apache Geode 1.13.2.RC1 voting deadline is now: 3PM PST 
Thurs, March 18, 2021

-Original Message-
From: Alexander Murmann  
Sent: Tuesday, March 16, 2021 1:46 PM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.13.2.RC1

 Can we please extend the vote for another 48 hours? We are investigating a 
potential issue in which registerInterest is taking over 5 minutes. It's still 
unclear what exactly is causing that, but some more time to investigate would 
be better than potentially shipping a bug like this.

From: Dick Cavender 
Sent: Thursday, March 11, 2021 13:34
To: dev@geode.apache.org 
Subject: [VOTE] Apache Geode 1.13.2.RC1

Hello Geode Dev Community,

It's been 4 months since the Apache Geode 1.13.1 release and there are a total 
48 important fixes on support/1.13 that the community would benefit from. The 
recently released v1.12.1 has 33 
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520GEODE%2520AND%2520fixVersion%2520%253D%25201.12.1%2520and%2520fixVersion%2520%253D%25201.13.2data=04%7C01%7Cdickc%40vmware.com%7C8711545d5210489e49cc08d8e8bc7f7d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637515243583180694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=2%2FBJupIvx6uobALMR%2Bx%2F8oH%2BVCcXwDJklfexocTS6uo%3Dreserved=0>
 fixes that are not released in 1.13. Based on this I propose release of an 
Apache Geode 1.13.2 based on the current support/1.13 branch. I'll volunteer to 
be the release manager for 1.13.2 and what follows is a release candidate for 
Apache Geode version 1.13.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 Tues, March 16, 2021

Please note that we are voting upon the source tag:
rel/v1.13.2.RC1

Release notes:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FRelease%2BNotes%23ReleaseNotes-1.13.2data=04%7C01%7Cdickc%40vmware.com%7C8711545d5210489e49cc08d8e8bc7f7d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637515243583180694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=q0u157E6wxp7sBETKldM0NJdLzQuK6QYVMP4mosL%2F7k%3Dreserved=0

Source and binary distributions:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2F1.13.2.RC1%2Fdata=04%7C01%7Cdickc%40vmware.com%7C8711545d5210489e49cc08d8e8bc7f7d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637515243583180694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=UY9y2gxfyt6btzQcitcgirKWlY4xyaAkJ86EyJR3mM4%3Dreserved=0

Maven staging repo:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1079data=04%7C01%7Cdickc%40vmware.com%7C8711545d5210489e49cc08d8e8bc7f7d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637515243583180694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=W9%2FmGgYNvWhHRsffReSsMRdMH47g44NRtzqG8w8j%2FaI%3Dreserved=0

GitHub:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Ftree%2Frel%2Fv1.13.2.RC1data=04%7C01%7Cdickc%40vmware.com%7C8711545d5210489e49cc08d8e8bc7f7d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637515243583180694%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=ekO2bzxn2SExGrBr38ufAJ1CsIyV6L9Wo7keuMdN1NY%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-examples%2Ftree%2Frel%2Fv1.13.2.RC1data=04%7C01%7Cdickc%40vmware.com%7C8711545d5210489e49cc08d8e8bc7f7d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637515243583190687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=tnJacGNq%2F%2FjVoTO58LF0QuPkbZ750rna8JDkpg1FXsc%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Ftree%2Frel%2Fv1.13.2.RC1data=04%7C01%7Cdickc%40vmware.com%7C8711545d5210489e49cc08d8e8bc7f7d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637515243583190687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=sowLtYTb3yF6WoGUzbOv2yCZ%2Bjpxlo29EhXe48rn7gI%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-benchmarks%2Ftree%2Frel%2Fv1.13.2.RC1data=04%7C01%7Cdickc%40vmware.com%7C8711545d5210489e49cc08d8e8bc7f7d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637515243583190687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6

RE: [VOTE] Apache Geode 1.13.2.RC1

[Dick Cavender]

Please vote by 3pm today for 1.13.2. At this time we don't have enough votes to 
release although there are no -1s.

From: Dick Cavender
Sent: Thursday, March 11, 2021 1:34 PM
To: dev@geode.apache.org
Subject: [VOTE] Apache Geode 1.13.2.RC1

Hello Geode Dev Community,

It's been 4 months since the Apache Geode 1.13.1 release and there are a total 
48 important fixes on support/1.13 that the community would benefit from. The 
recently released v1.12.1 has 33 
<https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.12.1%20and%20fixVersion%20%3D%201.13.2>
 fixes that are not released in 1.13. Based on this I propose release of an 
Apache Geode 1.13.2 based on the current support/1.13 branch. I'll volunteer to 
be the release manager for 1.13.2 and what follows is a release candidate for 
Apache Geode version 1.13.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 Tues, March 16, 2021

Please note that we are voting upon the source tag:
rel/v1.13.2.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.2

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.13.2.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1079

GitHub:
https://github.com/apache/geode/tree/rel/v1.13.2.RC1
https://github.com/apache/geode-examples/tree/rel/v1.13.2.RC1
https://github.com/apache/geode-native/tree/rel/v1.13.2.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.13.2.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.13.2.RC1 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1079
 build runAll

Regards
Dick Cavender

[VOTE] Apache Geode 1.13.2.RC1

[Dick Cavender]

Hello Geode Dev Community,

It's been 4 months since the Apache Geode 1.13.1 release and there are a total 
48 important fixes on support/1.13 that the community would benefit from. The 
recently released v1.12.1 has 33 
<https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.12.1%20and%20fixVersion%20%3D%201.13.2>
 fixes that are not released in 1.13. Based on this I propose release of an 
Apache Geode 1.13.2 based on the current support/1.13 branch. I'll volunteer to 
be the release manager for 1.13.2 and what follows is a release candidate for 
Apache Geode version 1.13.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 Tues, March 16, 2021

Please note that we are voting upon the source tag:
rel/v1.13.2.RC1

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.2

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.13.2.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1079

GitHub:
https://github.com/apache/geode/tree/rel/v1.13.2.RC1
https://github.com/apache/geode-examples/tree/rel/v1.13.2.RC1
https://github.com/apache/geode-native/tree/rel/v1.13.2.RC1
https://github.com/apache/geode-benchmarks/tree/rel/v1.13.2.RC1

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.13.2.RC1 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1079
 build runAll

Regards
Dick Cavender

RE: [VOTE] Apache Geode 1.12.1.RC4

[Dick Cavender]

+1 

Built source and examples, reviewed NOTICE and LICENSE and tgz distribution. 

-Original Message-
From: Owen Nichols  
Sent: Sunday, February 21, 2021 12:08 PM
To: dev@geode.apache.org
Subject: [VOTE] Apache Geode 1.12.1.RC4

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.12.1.RC4.
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 Thu, February 25 2021.

Please note that we are voting upon the source tag:
rel/v1.12.1.RC4

Release notes:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FRelease%2BNotes%23ReleaseNotes-1.12.1data=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873343112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=zstDLzCjSsJWsvI2En1J%2BTbkDONEE7Q8if8QWtHheXY%3Dreserved=0

Source and binary distributions:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2F1.12.1.RC4%2Fdata=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873343112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=EIv4oxXhDuY2BN6EGl23qXgOt4wp9yy21h2v%2FApevTM%3Dreserved=0

Maven staging repo:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1075data=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873343112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=W31KY5OS1SMrs83ec7rk2UJFs08dwIVL5lNXbOqsc20%3Dreserved=0

GitHub:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Ftree%2Frel%2Fv1.12.1.RC4data=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873343112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=dDr66Iik2pgjvjOH6Z5cDO58YB2cV0WKkvqszuH1CWU%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-examples%2Ftree%2Frel%2Fv1.12.1.RC4data=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873343112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=6Z%2B7LhBzBA1kILMnArIYIoHrvNUF4tXe%2FfJjkpKoVSY%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Ftree%2Frel%2Fv1.12.1.RC4data=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873343112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=%2FFUO0EU99eicVh4TX%2Fvl1LwcL%2BSbav6nFT4aynpSQjs%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-benchmarks%2Ftree%2Frel%2Fv1.12.1.RC4data=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873343112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=BvtfjbSjAn7tfT2qcAFqJ0bMC2VIWGcG6LDRUFjH3ME%3Dreserved=0

Pipelines:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-12-maindata=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873343112%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=2nwp15HZNYMBufAm3aJ8QelcTRgl6Dr5Ax5zVfJ3Z%2Bg%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-12-rcdata=04%7C01%7Cdickc%40vmware.com%7Cafaf662cc2334f04beb808d8d6a4661a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637495348873353103%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=LxyjI8K8Scny%2BsmofNNb4Fvd724WJ7AHoswwlTLph9g%3Dreserved=0

Geode's KEYS file containing PGP keys we use to sign the release:

[ANNOUNCE] Apache Geode 1.13.1

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.13.1.



Apache Geode is a data management platform that provides a
database-like consistency
model, reliable transaction processing and a shared-nothing architecture to
maintain very low latency performance with high concurrency processing.



Geode {version} contains a number of improvements and bug fixes. It
includes performance improvements in OQL order-by and distinct queries in
client/server when security is enabled. New GFSH commands were added to
get/set cluster config and to destroy gateway receivers. A new post
processor was added to the new client protocol. Pulse now supports legacy
SSL options. Auto-reconnecting members no more reuse old addresses and IDs.
Duplicated or member-specific receivers are removed from cluster config
during rolling upgrades. Users are encouraged to upgrade to the latest
release.



For the full list of changes please review the release notes:

https://cwiki.apache.org/confluence/display/GEODE/
Release+Notes#ReleaseNotes-1.13.1



The release artifacts can be downloaded from the project website:



The release documentation is available at:

http://geode.apache.org/docs/guide/113/about_geode.html



We would like to thank all the contributors that made the release possible.


Regards,

Dick Cavender on behalf of the Apache Geode team

Apache Geode 1.13.1 Release

[Dick Cavender]

It's now past the deadline and we have enough votes to close the voting.

Voting status
==
+1: 5 binding votes, 0 non-binding votes
* Dan Smith (PMC member)
* Jason Huynh (PMC member)
* Joris Melchior (PMC member)
* Nabarun Nag (PMC member)
* Dave Barnes (PMC member)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and 
has the required majority of +1 votes.

Apache Geode 1.13.1 passes the vote so I will finalize the release shortly.

Thanks to everyone for the great work!

Dick Cavender

[VOTE] Apache Geode 1.13.1.RC2

[Dick Cavender]

Hello Geode Dev Community,

This is a release candidate for Apache Geode version 1.13.1.RC2.
Issues with creation of RC1 forced moving to RC2.
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 Tue, November 17 2020.

Please note that we are voting upon the source tag:
rel/v1.13.1.RC2

Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.13.1

Source and binary distributions:
https://dist.apache.org/repos/dist/dev/geode/1.13.1.RC2/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1071

GitHub:
https://github.com/apache/geode/tree/rel/v1.13.1.RC2
https://github.com/apache/geode-examples/tree/rel/v1.13.1.RC2
https://github.com/apache/geode-native/tree/rel/v1.13.1.RC2
https://github.com/apache/geode-benchmarks/tree/rel/v1.13.1.RC2

Pipelines:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-rc

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

Command to run geode-examples:
./gradlew 
-PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.13.1.RC2 
-PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1071
 build runAll

Regards
Dick Cavender

Apache Geode 1.13.1 patch proposal

[Dick Cavender]

It's been two months since the 1.13.0 release and there have been 28 important 
fixes on support/1.13 that the community would benefit from. Based on this I'd 
like to propose release of Apache Geode 1.13.1 based on the current 
support/1.13 branch. I'll volunteer to be the release manager for 1.13.1 so 
look forward to an RC1 soon.

-Dick

RE: [PROPOSAL] Backport GEODE-6008 to support 1.12

[Dick Cavender]

+1

-Original Message-
From: Xiaojian Zhou  
Sent: Tuesday, September 29, 2020 3:09 PM
To: dev@geode.apache.org
Subject: [PROPOSAL] Backport GEODE-6008 to support 1.12

Hi,

GEODE-6008 changed “java.lang.IllegalStateException: NioSslEngine has been 
closed” to IOException, which enabled DirectChannel to handle it and retry the 
connection in the case that the connection is closed.

This fix is important and no risk to backport to support/1.12. Please vote for 
it.

Regards
Xiaojian Zhou

RE: [PROPOSAL] Backport GEODE-8475 to 1.13

[Dick Cavender]

+1

-Original Message-
From: Anilkumar Gingade  
Sent: Wednesday, September 2, 2020 11:05 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] Backport GEODE-8475 to 1.13

+1 As it address a potential hang. 

-Anil.


On 9/2/20, 10:38 AM, "Xiaojian Zhou"  wrote:

Hi, All:

I want to backport my fix in GEODE-8475 to 1.13. It fixed a hang caused by 
a potential deadlock.

This fix is quite safe, I have verified it by running all queue related 
regression.

Regards
Gester

RE: [Proposal] Backport GEODE-8422 to support/1.13

[Dick Cavender]

+1

-Original Message-
From: Mark Hanson  
Sent: Thursday, August 13, 2020 4:46 PM
To: dev@geode.apache.org
Subject: Re: [Proposal] Backport GEODE-8422 to support/1.13

Hi All, 

I can't remember for sure, but I think we need 3 approvals?

Thanks,
Mark

On 8/13/20, 4:22 PM, "Owen Nichols"  wrote:

+1 from me.  Pipeline and all other testing I've seen suggests this fix is 
good

On 8/12/20, 4:52 PM, "Jianxia Chen"  wrote:

+1

On Wed, Aug 12, 2020 at 4:41 PM Mark Hanson  wrote:

> Hi All,
>
> We have found a case where tombstones were being cleared when the 
region
> was not initialized. This was causing some test failures and potential
> field failures. We would like to put this into support/1.13.
>
> Thanks,
> Mark
>

RE: [PROPOSAL] port GEODE-8323 changes to support/1.13 branch.

[Dick Cavender]

+1

-Original Message-
From: Eric Shu  
Sent: Tuesday, July 28, 2020 4:22 PM
To: dev@geode.apache.org
Subject: [PROPOSAL] port GEODE-8323 changes to support/1.13 branch.

This is to address HARegionQueue GII events not properly removed issue, which 
could potentially resurrect a strayed event in client cache.

Regards,
Eric

RE: [Proposal] Back-port doc fixes to support/1.13

[Dick Cavender]

+1

-Original Message-
From: Owen Nichols  
Sent: Wednesday, July 22, 2020 4:59 PM
To: dev@geode.apache.org
Subject: Re: [Proposal] Back-port doc fixes to support/1.13




+1

On July 22, 2020 at 3:43:16 PM PDT, Jinmei Liao  wrote:
+1

On Jul 22, 2020 3:39 PM, Dave Barnes  wrote:
I propose back-porting the following doc updates to Geode support/1.13 (and 
1.12, while we're at it):


- GEODE-2113: User Guide - p2p.HANDSHAKE_POOL_SIZE is obsolete, remove from 
docs (code fixed in 1.9.0, docs fixed in 1.14.0)

- GEODE-7628: Block jmx mbean creation when no security manager is configured 
(docs) (code fixed in 1.12.0, docs fixed in 1.14.0)

- GEODE-8308: Some formatting text visible in the docs (docs only, fixed in
1.14.0)

- GEODE-8363: Label Micrometer docs as experimental (docs only, fixed in
1.14.0)

- GEODE-8377: User Guide: GFSH GC command should be documented to use only in 
non-production environments (docs only, fixed in 1.14.0)

RE: [PROPOSAL] Cherry pic GEODE-8331 to support branches

[Dick Cavender]

+1

-Original Message-
From: Anilkumar Gingade  
Sent: Wednesday, July 22, 2020 2:44 PM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] Cherry pic GEODE-8331 to support branches

+1 
This will provide a consistent experience our end user from 1.10 release 
version.

On 7/22/20, 2:23 PM, "Jinmei Liao"  wrote:

I would like to propose to cherry pick GEODE-8331: allow GFSH to connect to 
other versions of cluster (#5375) to support branches up to 1.10. This would 
allow gfsh to connect to other versions of cluster and provide better error 
messages when command is not support by the connected cluster.

Jinmei

RE: [VOTE] change Default branch for geode-examples to 'develop'

[Dick Cavender]

+1

-Original Message-
From: Owen Nichols  
Sent: Thursday, July 9, 2020 9:39 PM
To: dev@geode.apache.org
Subject: [VOTE] change Default branch for geode-examples to 'develop'

A fresh checkout of geode and all but one geode- repos checks 
out develop as the Default branch.

The lone exception is geode-examples.  Please vote +1 if you are in favor of 
changing its Default branch to develop for consistency with the other repos and 
other reasons as per recent discussion[1].

[1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fx%2Fthread.html%2Frfec15c0a7d5d6d57beed90868dbb53e3bfcaabca67589b28585556ee%40%253Cdev.geode.apache.org%253Edata=02%7C01%7Cdickc%40vmware.com%7C1a703cc22f784158523008d8248b4188%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637299527805384154sdata=9BABTC6ROp6h3hD7lsOkezesyc%2BuJFAFQB08BFL7O%2FE%3Dreserved=0

RE: [PROPOSAL]: Backport GEODE-8029 to support/1.12 and support/1.13

[Dick Cavender]

+1

-Original Message-
From: Joris Melchior  
Sent: Friday, July 3, 2020 9:09 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL]: Backport GEODE-8029 to support/1.12 and support/1.13

+1

On 2020-07-03, 9:06 AM, "Ju@N"  wrote:

Hello devs,

I'd like to propose bringing GEODE-8029 [1] to the support/1.12 and
support/1.13 branches.
No, you're not having deja vú (neither this is an error within the Matrix):
a couple of weeks ago I've backported another fix for the same ticket to
the mentioned branches and sent the proposal to the list with exactly the
same subject, but it has proven to be problematic and introduced some
regressions... sorry about that.
The new fix uses a different approach, solves the original issue and
doesn't introduce any new problems (feel free to have a look at the ticket
for further details); it has been merged into develop already through
commit fdc4401 [2]. As a side note, I've also created a new ticket
(GEODE-8325 [3]) to improve the internal behavior and implement a long term
solution to avoid the proliferation of unused drf files.
Best regards.

[1]: 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8029data=02%7C01%7Cdickc%40vmware.com%7C1eda36ff648b4814d5ae08d81f6b5d74%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637293893277285211sdata=4tamZzomlNfaLufOzWXTT1SYvZmp9s7pGHXPUcV4lsY%3Dreserved=0
[2]:

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fcommit%2Ffdc440131f0d562d97f2340d2e7ba5aacf935d62data=02%7C01%7Cdickc%40vmware.com%7C1eda36ff648b4814d5ae08d81f6b5d74%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637293893277285211sdata=oAC9uDq4%2FlB%2FLV%2BzZnECyu4kZdc9c8enf%2BFzOxKgqCs%3Dreserved=0
[3]: 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8325data=02%7C01%7Cdickc%40vmware.com%7C1eda36ff648b4814d5ae08d81f6b5d74%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637293893277295208sdata=tLOcaPQVmWQSaOqWLN%2Fx5WkqcRSUriLd5ilo5Bmc4xg%3Dreserved=0


-- 
Ju@N

RE: Back-Port GEODE-8240 to 1.12, 1.13

[Dick Cavender]

+1

-Original Message-
From: Bruce Schuchardt  
Sent: Wednesday, July 1, 2020 9:49 AM
To: dev@geode.apache.org
Subject: Re: Back-Port GEODE-8240 to 1.12, 1.13

+1

On 7/1/20, 9:43 AM, "Bill Burcham"  wrote:

I'd like permission to back-port the fix for rolling upgrade bug GEODE-8240
to support/1.12 and support/1.13

-Bill

RE: Proposal to bring GEODE-8315 (shiro upgrade) to support branches

[Dick Cavender]

+1

-Original Message-
From: Ju@N  
Sent: Tuesday, June 30, 2020 9:12 AM
To: dev@geode.apache.org
Subject: Re: Proposal to bring GEODE-8315 (shiro upgrade) to support branches

+1

On Tue, 30 Jun 2020 at 17:03, Owen Nichols  wrote:

> Recently shiro-1.5.2.jar is getting flagged for critical security 
> vulnerability CVE-2020-11989.
>
> Analysis shows that Geode does not use Shiro in a manner that would 
> expose this vulnerability.
>
> The risk of bringing GEODE-8315 is very low (difference between Shiro
> 1.5.2 and 1.5.3 is bugfix only).  GEODE-8315 has been on develop for 2 
> days and passed the pipeline.
>
> This fix is critical to avoid false positives in automated 
> vulnerability scans, so it would be nice to bring before 1.13.0 release.
>


--
Ju@N

RE: [PROPOSAL] Add windows jobs to PR checks

[Dick Cavender]

+1

-Original Message-
From: Owen Nichols  
Sent: Thursday, June 25, 2020 9:38 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] Add windows jobs to PR checks

+1 for adding all JDK11 Windows tests to PR pipeline.

On 6/25/20, 9:29 AM, "Kirk Lund"  wrote:

I merged some new AcceptanceTests to develop after having my PR go GREEN.
But now these tests are failing in Windows.

I'd like to propose that we add the Windows jobs to our PR checks if we
plan to keep testing on Windows in CI.

Please vote or discuss.

Thanks,
Kirk

RE: [PROPOSAL] backport GEODE-8277 to support/1.13

[Dick Cavender]

+1

-Original Message-
From: Ernie Burghardt  
Sent: Thursday, June 18, 2020 10:49 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] backport GEODE-8277 to support/1.13

+100 

On 6/18/20, 10:46 AM, "Bruce Schuchardt"  wrote:

Several keystores used by a test have expired, which will cause acceptance 
tests to fail in support/1.13.  I’d like to cherry-pick the new keystores into 
that branch.  The new keystores have a 5/2120 expiration date.

RE: [PROPOSAL] backport PR #5250 to support/1.13

[Dick Cavender]

+1

-Original Message-
From: Bruce Schuchardt  
Sent: Tuesday, June 16, 2020 3:24 PM
To: dev@geode.apache.org
Subject: [PROPOSAL] backport PR #5250 to support/1.13

This PR has been merged to develop.  It fixes a problem with the previous 
commit for GEODE-8144 that caused performance degradation when TLS is enabled 
between servers.  I have run perf tests and verified that it fixes the problem.

It’s a small change that makes a big difference…
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F5250data=02%7C01%7Cdickc%40vmware.com%7C3c5cb9fbd9274b032b8508d8124403ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637279430617900387sdata=eT22ksaNTZIFI%2F14NrTkauiiDclGug37g0SEX7Uklek%3Dreserved=0

RE: [PROPOSAL] backport GEODE-8238 to support/1.13

[Dick Cavender]

+1

-Original Message-
From: Eric Shu  
Sent: Thursday, June 11, 2020 11:33 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] backport GEODE-8238 to support/1.13

+1

From: Owen Nichols 
Sent: Thursday, June 11, 2020 10:58 AM
To: dev@geode.apache.org 
Subject: Re: [PROPOSAL] backport GEODE-8238 to support/1.13

+1


---
Sent from Workspace ONE 
Boxer

On June 11, 2020 at 10:52:19 AM PDT, Bruce Schuchardt  wrote:
This ticket concerns loss of a message and a subsequent hang during shutdown.  
The problem is also in support/1.13 and I'd like to backport to that branch.

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8238data=02%7C01%7Cdickc%40vmware.com%7C449d3bc3f7fa465b8d7b08d80e36d985%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637274976024080508sdata=cG2rc2X1YAmsqGZVumT%2F4JLUYIH5hjm8Y%2Fw8ADIa6oQ%3Dreserved=0

It's a small change to fix a problem introduced in changes for GEODE-7727.
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-7727data=02%7C01%7Cdickc%40vmware.com%7C449d3bc3f7fa465b8d7b08d80e36d985%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637274976024085498sdata=xaYlc41o44RmSdwvko%2FuhBW6VtNvRgFXGAsRbU%2FY2YQ%3Dreserved=0

RE: [PROPOSAL]: BackPort GEODE-8029 to support/1.12 and support/1.13

[Dick Cavender]

+1

-Original Message-
From: Udo Kohlmeyer  
Sent: Wednesday, June 10, 2020 9:14 AM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL]: BackPort GEODE-8029 to support/1.12 and support/1.13

+1
On Jun 10, 2020, 3:18 AM -0700, Ju@N , wrote:
Hello devs,

I'd like to propose bringing GEODE-8029 [1] to the *support/1.12* and
*support/1.13* branches.
The fix has been merged into develop through commit
bc0090dc93643fd4d09c79a4b0c29d883172b546 [2], and it's basically to make sure 
we delete unused drfs upon initialization to prevent the proliferation of 
unused records and files within the file system, which could cause members to 
fail during startup while recovering disk-stores.
Best regards.

[1]: 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8029data=02%7C01%7Cdickc%40vmware.com%7Cac95fdc8b67c45d3931a08d80d5a2434%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637274028089007755sdata=zM3nWf6uqoQFBkmV6vmnH3Fr4hFhGh3blSxCmH%2ByCwU%3Dreserved=0
[2:]
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fcommit%2Fbc0090dc93643fd4d09c79a4b0c29d883172b546data=02%7C01%7Cdickc%40vmware.com%7Cac95fdc8b67c45d3931a08d80d5a2434%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637274028089007755sdata=wT5C1SM7LpCu7pIo8xjwUM9VtFN7DHuxTeob20r61BE%3Dreserved=0

--
Ju@N

RE: [PROPOSAL] backport GEODE-8174 to 1.13 and 1.12

[Dick Cavender]

+1

-Original Message-
From: Owen Nichols  
Sent: Tuesday, May 26, 2020 4:09 PM
To: dev@geode.apache.org
Subject: Re: [PROPOSAL] backport GEODE-8174 to 1.13 and 1.12

+1

On 5/26/20, 4:04 PM, "Eric Shu"  wrote:

+1


From: Udo Kohlmeyer 
Sent: Tuesday, May 26, 2020 2:12 PM
To: geode 
Subject: [PROPOSAL] backport GEODE-8174 to 1.13 and 1.12

Hi there Geode Dev,

I would like to request a back port of a critical issue in the 
JCAConnectionManager. This issue manifests itself as a 
ConcurrentModificationException when trying to close a connection.

SHA: bef07b34131abddb8c0f04e0ab6a48f1daac991d

—Udo

Re: Proposal to backport GEODE-8167

[Dick Cavender]

+1

On Thu, May 21, 2020 at 8:57 AM Ju@N  wrote:

> +1
>
> On Thu, 21 May 2020 at 16:53, Anthony Baker  wrote:
>
> > +1
> >
> > > On May 21, 2020, at 8:51 AM, Owen Nichols  wrote:
> > >
> > > Some automated scans have flagged Geode Pulse as potentially containing
> > “high" security vulnerability CVE-2020-5407.
> > >
> > > Analysis shows that this saml vulnerability is not applicable to Geode
> > Pulse.
> > >
> > > It is low risk to bump the spring-security dependency to the latest
> > version to avoid false positives in automated scans.  This change is
> > already on develop and all tests have passed.  It would be nice to
> include
> > this in 1.13.
> > >
> > > -Owen
> >
> >
>
> --
> Ju@N
>

Re: Proposal to bring GEODE-8016 to support branches

[Dick Cavender]

+1

On Sat, May 9, 2020 at 6:42 PM Owen Nichols  wrote:

> Last week develop was successfully migrated from publishing -SNAPSHOT to
> publishing -build.nnn, as discussed on the dev list.
>
> I propose that we bring the same change to support/1.13 and support/1.12
> for consistency.  This will allow downstream projects to change over the
> new model “everywhere" rather than having to maintain support for both ways
> and constantly try to remember which branches do it which way.
>
> The specific changes to be cherry-picked from develop are a4c8b <
> https://github.com/apache/geode/commit/a4c8b9ed8bbea584f798164fa5308d236e9b6048>
> and 39c52 <
> https://github.com/apache/geode/commit/39c522e340196cb30d55d81d93c63028938cd782>.
> I have prepared PR #5089  for
> support/1.13 and PR #5090  for
> support/1.12 due to the version number differences on each branch.

Re: Discussion - Change Public API Before Initial Release

[Dick Cavender]

+1

On Fri, May 8, 2020 at 7:59 PM Owen Nichols  wrote:

> +1
>
> > On May 8, 2020, at 7:57 PM, Robert Houghton 
> wrote:
> >
> > +1
> >
> > On Fri, May 8, 2020, 18:26 Jacob Barrett  wrote:
> >
> >> Hey Ya’ll,
> >>
> >> We have a new API going into 1.13 that has an inconsistency I want to
> >> address before we are stuck with it. The class SniSocketFactory should
> be
> >> renamed SniProxySocketFactory. The class in question produces objects of
> >> type SniProxySocket. An "SNI socket" isn’t a thing but an SNI proxy is a
> >> thing. The factory class that produces proxy socket factories (yes a
> meta
> >> factory) ProxySocketFactories uses the “ProxySocket” name as well. It
> fells
> >> very inconsistent with all the other classes that make up with API for
> >> SniSocketFactory to not have a proxy in it and be called
> >> SniProxySocketFactory.
> >>
> >> To be very clear, this API has not made it out of development yet but is
> >> in the 1.13 release branch. Can I get a few thumbs up to open an ticket
> and
> >> pick it into the 1.13 release branch before it goes out?
> >>
> >> Thanks,
> >> Jake
> >>
> >>
>
>

Re: Proposal to bring GEODE-8068 to support/1.13

[Dick Cavender]

+1

On Fri, May 8, 2020 at 2:52 PM Owen Nichols  wrote:

> +1
>
> Redis work is still marked @Experimental, but since this was reverted on
> develop just after the branch cut, it makes sense to revert from
> support/1.13 as well.
>
> > On May 8, 2020, at 2:40 PM, Patrick Johnson  wrote:
> >
> > I’d like to bring GEODE-8068 to support/1.13. This commit reverts two
> prior commits (GEODE-8033 and GEODE-8044). GEODE-8033 and GEODE-8044
> introduced an experimental feature that is useless in its current state and
> has already been redesigned, so there is no reason for it to go out with
> 1.13.
> >
> > Regards,
> > Patrick
>
>

Re: [PROPOSAL]: GEODE-8071 to support/1.12 and support/1.13

[Dick Cavender]

+1

On Thu, May 7, 2020 at 7:47 AM Ju@N  wrote:

> Hello devs,
>
> I'd like to propose bringing GEODE-8071 [1] to the *support/1.12* and
> *support/1.13* branches.
> The bug was introduced in Geode 1.8.0 and, long story short, prevents
> locators from gracefully shutting down whenever a rebalance operation is
> launched from gfsh (doesn't matter whether the rebalance is successful or
> not).
> The fix has been merged into develop through commit
> d8e86cb720c054b154a16cc88fee88e73db709f3 [2].
> Best regards.
>
> [1]: https://issues.apache.org/jira/browse/GEODE-8071
> [2:]
>
> https://github.com/apache/geode/commit/d8e86cb720c054b154a16cc88fee88e73db709f3
>
> --
> Ju@N
>

Re: [PROPOSAL] include GEODE-8055 in support/1.13

[Dick Cavender]

+1

On Mon, May 4, 2020 at 8:28 PM Owen Nichols  wrote:

> Hi Jinmei, it looks like your commit came in just minutes after the
> support/1.13 branch was cut, but before the email announcing the branch cut
> was sent.  +1 from me to go ahead and bring to support/1.13 on that basis.
>
> > On May 4, 2020, at 7:43 PM, Jinmei Liao  wrote:
> >
> > Yes, there is a user request to reinstate this feature.
> >
> > On Mon, May 4, 2020 at 4:41 PM Anilkumar Gingade 
> > wrote:
> >
> >> Since this issue is introduced from 1.7; meaning its present from 1.7
> time,
> >> can it be added in the next release, is there any strong user/customer
> >> requirement to get this in 1.13.
> >>
> >> -Anil.
> >>
> >>
> >> On Mon, May 4, 2020 at 11:55 AM Jinmei Liao  wrote:
> >>
> >>> I would like to include the fix for GEODE-8055 in the 1.13 branch. This
> >>> would allow users to use gfsh to create an index on sub regions.
> >>>
> >>> --
> >>> Cheers
> >>>
> >>> Jinmei
> >>>
> >>
> >
> >
> > --
> > Cheers
> >
> > Jinmei
>
>

Re: Proposal to bring GEODE-7970 to support/1.12

[Dick Cavender]

+1

On Fri, Apr 10, 2020 at 11:16 AM Owen Nichols  wrote:

> Recently it’s been noticed that spring-core-5.2.1.RELEASE.jar is getting
> flagged for “high" security vulnerability CVE-2020-5398.
>
> Analysis shows that Geode does not use Spring in a manner that would
> expose this vulnerability (none of our REST apis or pulse set a
> Content-Disposition header derived from user-supplied input).
>
> The risk of bringing GEODE-7970 is low.  This patch update from 5.2.1 to
> 5.2.5 brings bug fixes only.  This exact version was on develop from Apr 8
> - Apr 10 & passed all tests.
>
> This fix is critical to avoid false positives in automated vulnerability
> scans.
>
> -Owen

Re: Proposal to bring GEODE-7969 to support/1.12

[Dick Cavender]

+1

On Wed, Apr 8, 2020 at 10:08 AM Joris Melchior  wrote:

> +1
>
> On Wed, Apr 8, 2020 at 12:21 PM Owen Nichols  wrote:
>
> > Recently it’s been noticed that netty-all-4.1.42.Final.jar is getting
> > flagged for “high" security vulnerability CVE-2019-20444 and
> CVE-2019-20445.
> >
> > Analysis shows that Geode does not use Netty in a manner that would
> expose
> > this vulnerability.
> >
> > The risk of bringing GEODE-7969 is very low.  Netty is only imported for
> > some I/O libraries in geode-redis, not used as a server.  GEODE-7969 has
> > passed all PR checks on support/1.12, and the same version bump to
> > 4.1.45.Final has been on develop since February via GEODE-7798.
> >
> > This fix is critical to avoid false positives in automated vulnerability
> > scans.
> >
> > -Owen
>
>
>
> --
> *Joris Melchior *
> CF Engineering
> Pivotal Toronto
> 416 877 5427
>
> “Programs must be written for people to read, and only incidentally for
> machines to execute.” – *Hal Abelson*
> 
>

Re: [PROPOSAL] Include fix for GEODE-7763 into release 1.12.0

[Dick Cavender]

+1

On Wed, Mar 18, 2020 at 11:43 AM Nabarun Nag  wrote:

> +1
>
> On Wed, Mar 18, 2020 at 11:41 AM Jason Huynh  wrote:
>
> > Hello Dev list,
> >
> > I'd like to include a fix for GEODE-7763 in release 1.12.0.
> > The change removes the call to exportValue, preventing a serialization,
> > when no clients are waiting for the specific event.
> > The reason why I think it should be in the release is that we noticed a
> > negative effect on performance for a specific use case, in 1.12 from a
> > change that made us more "consistent" in that use case.  This change
> > doesn't modify the fix much, but does bring performance back inline (if
> not
> > better) than before.
> >
> > The sha is b4c3e9413f0008635b0a0c9116c96147d1e4ceec
> >
> > Thanks,
> > -Jason
> >
>

Re: [DISCUSS] RFC: Shipping Geode patch releases

[Dick Cavender]

+1 to the proposal and the plan outlined above for the transition period.


On Mon, Mar 2, 2020 at 4:33 PM Owen Nichols  wrote:

> My interpretation is that we would cut support/1.13 from develop on the
> next scheduled cut date (May 4), and make 1.13.0 and all following 1.13.x
> patch releases directly from this branch.  Otherwise it becomes a two-step
> process if all patches have to be cherry-picked from develop -> support/x.y
> -> release/x.y.z.  Assuming patch-worthy fixes will already be vetted by
> the community as critical in order to bring them to support/x.y, it doesn’t
> seem like we’d gain anything but unnecessary complexity to require a second
> round of sifting.
>
> support/1.12 will have to be cut from release/1.12.0 as a one-time special
> case, but the end result should be indistinguishable.
>
> > On Mar 2, 2020, at 4:24 PM, Dan Smith  wrote:
> >
> > +1 to the proposal as written.
> >
> > The proposal does talk about support branches, but doesn't describe when
> > they are created. Is the idea that we create a support/1.X branch as soon
> > as we release geode 1.X, and then create release branches off of that as
> > needed?
> >
> > -Dan
>
>

Re: [PROPOSAL] include GEODE-7796 in Release 1.12.0

[Dick Cavender]

+1

On Tue, Feb 18, 2020 at 1:16 PM Robert Houghton 
wrote:

> +1
>
> On Tue, Feb 18, 2020, 12:49 Bruce Schuchardt 
> wrote:
>
> > This fix addresses the inability of a Locator to properly reconnect to
> the
> > cluster after being kicked out.  Instead of rejoining or shutting down
> the
> > Locator gets into a state where it no longer tries to reboot location
> > services and hangs.
> >
> >
>

Re: Include GEODE-7776 in release 1.12

[Dick Cavender]

Ernie- Can you please cherry-pick GEODE-7776 to release/1.12.0?


On Tue, Feb 11, 2020 at 11:45 AM Jinmei Liao  wrote:

> +1
>
> On Tue, Feb 11, 2020, 11:39 AM Udo Kohlmeyer  wrote:
>
> > +1
> >
> > On 2/11/20 11:23 AM, Dick Cavender wrote:
> > > This regression was introduced when the geode-gfsh subproject was
> > recently
> > > added. While not obvious this created a critical build / runtime cycle
> > > between geode-core and geode-gfsh that causes some tools/IDEs, that
> don't
> > > cope well with circular dependencies, to fail. Additionally no previous
> > > Geode releases have shipped with known circular dependencies.
> > >
> > > commit 7ab2713d6c9d2d09a986513aaa18b333951fe61e
> > > Author: Robert Houghton 
> > > Date:   Mon Feb 10 13:18:34 2020 -0800
> > >
> > >  GEODE-7776 - Proposed changes to remove build cycle (#4679)
> > >
> > >  * Proposed changes to remove build cycle
> > >
> > >  * Fix expected pom, and delete commented dependency
> > >
> >
>

Include GEODE-7776 in release 1.12

[Dick Cavender]

This regression was introduced when the geode-gfsh subproject was recently
added. While not obvious this created a critical build / runtime cycle
between geode-core and geode-gfsh that causes some tools/IDEs, that don't
cope well with circular dependencies, to fail. Additionally no previous
Geode releases have shipped with known circular dependencies.

commit 7ab2713d6c9d2d09a986513aaa18b333951fe61e
Author: Robert Houghton 
Date:   Mon Feb 10 13:18:34 2020 -0800

GEODE-7776 - Proposed changes to remove build cycle (#4679)

* Proposed changes to remove build cycle

* Fix expected pom, and delete commented dependency

Re: Proposal to including GEODE-7593 in release/1.11.0

[Dick Cavender]

+1

On Thu, Dec 19, 2019 at 11:27 AM Udo Kohlmeyer  wrote:

> +1
>
> On 12/19/19 10:05 AM, Owen Nichols wrote:
> > GEODE-7593 fixes a memory leak where indexes could retain references to
> pdx values when eviction should have released that memory.
> >
> > This is not a new issue, but is critical because system stability is
> threatened when eviction does not release memory as expected.
> >
> > The SHA is 1beec9e3930a071031b960f045874fb337e72e7c.
>

Re: [VOTE] Inclusion of GEODE-7531 into 1.11

[Dick Cavender]

+1

On Tue, Dec 17, 2019 at 3:03 PM Patrick Johnson  wrote:

> +1
>
> > On Dec 17, 2019, at 3:01 PM, Owen Nichols  wrote:
> >
> > +1
> >
> >> On Dec 17, 2019, at 2:57 PM, Udo Kohlmeyer  wrote:
> >>
> >> Hi there Apache Devs.
> >>
> >> I can we please vote on the inclusion of GEODE-7531. This issue is to
> fix an bug which assumes that all `Pool` objects are of type `PoolImpl` and
> immediately casts Pool -> PoolImpl.
> >>
> >> In the case of testing with Mocks, the type casts fail, because the
> Pool-mocks are not of type PoolImpl. The simplest fix (for now) was to type
> check before the cast.
> >>
> >>
> >> Regards
> >>
> >> Udo
> >>
> >
>
>

Re: [VOTE] Inclusion of GEODE-7159 into 1.11

[Dick Cavender]

+1

On Tue, Dec 17, 2019 at 3:01 PM Patrick Johnson  wrote:

> +1
>
> > On Dec 17, 2019, at 2:59 PM, Owen Nichols  wrote:
> >
> > +1
> >
> >> On Dec 17, 2019, at 2:58 PM, Udo Kohlmeyer  wrote:
> >>
> >> Hi there Apache Devs.
> >>
> >> I can we please vote on the inclusion of GEODE-7159. This issue is to
> fix an bug which assumes that all `Pool` objects are of type `PoolImpl` and
> immediately casts Pool -> PoolImpl. This issue is related to GEODE-7531,
> and is specific to the emergencyClose method.
> >>
> >> In the case of testing with Mocks, the type casts fail, because the
> Pool-mocks are not of type PoolImpl. The simplest fix (for now) was to type
> check before the cast.
> >>
> >>
> >> Regards
> >>
> >> Udo
> >>
> >
>
>

Re: [DISCUSS/VOTE] Proposal to bring GEODE-7465 to release/1.11.0

[Dick Cavender]

+1

On Tue, Nov 26, 2019 at 11:27 AM Owen Nichols  wrote:

> I would like to propose bringing “GEODE-7465: Set eventProcessor to null
> in serial AEQ when it is stopped” into the 1.11 release (necessitating an
> RC4).
>
> Without the fix, a sequence of ordinary gfsh commands will leave the WAN
> gateway in an unrecoverable hung state:
> stop gateway-sender
> start gateway-sender
> The only recourse is to restart the server.
>
> This fix is critical because the distributed system fails to sync data
> between WAN sites as the user would expect.
> This issue did exist in previous releases, but recent enhancements to
> WAN/AEQ such as AEQ-pause are increasing user interaction with WAN-related
> gfsh commands.
>
> The fix is simple, low risk, tested, and has been on develop for 5 days:
>
> https://github.com/apache/geode/commit/e148cef9cb63eba283cf86bc490eb280023567ce

Re: Quick turnaround needed, feedback on this DRAFT Nov board report

[Dick Cavender]

+1

On Wed, Nov 13, 2019 at 9:52 AM Dave Barnes  wrote:

> +1 LGTM
>
> On Wed, Nov 13, 2019 at 9:49 AM Karen Miller  wrote:
>
> > Draft board report for November 2019.  Submitting in 2 hours!  Quick
> > feedback, please!
> >
> > ## Description:
> > The mission of Apache Geode is the creation and maintenance of software
> > related
> > to a data management platform that provides real-time, consistent access
> to
> > data-intensive applications throughout widely distributed cloud
> > architectures.
> >
> > ## Issues:
> > There are no issues requiring board attention at this time.
> >
> > ## Membership Data:
> > Apache Geode was founded 2016-11-15 (3 years ago)
> > There are currently 104 committers and 52 PMC members in this project.
> > The Committer-to-PMC ratio is 2:1.
> >
> > Community changes, past quarter:
> > - Bill Burcham was added to the PMC on 2019-09-08
> > - Mario Ivanac was added to the PMC on 2019-09-08
> > - Bill Burcham was added as committer on 2019-09-09
> > - Mario Ivanac was added as committer on 2019-09-09
> >
> > ## Project Activity:
> > - Released Apache Geode 1.10.0 on 2019-09-26.
> > - Released Apache Geode 1.9.1 on 2019-09-06.
> >
> >
> > ## Community Health:
> > The community is actively contributing to the Apache Geode code base. In
> > the
> > past quarter:
> > - 61 code contributors
> > - 347 issues opened in JIRA
> > - 275 issues closed in JIRA
> > - 434 PRs opened on GitHub
> > - 426 PRs closed on GitHub
> >
> > Enjoyed great attendance at the Apache Geode Summit held October 7, 2019,
> > in
> > Austin, Texas.
> >
>

Re: Update geode-native-build image as part of release process

[Dick Cavender]

+1

On Thu, Nov 7, 2019 at 8:38 AM Owen Nichols  wrote:

> +1
>
> On Thu, Nov 7, 2019 at 6:46 AM Alberto Bustamante Reyes
>  wrote:
>
> > Hi all,
> >
> > Some time ago I opened GEODE-7056 to update the Dockerfile of the
> > "geode-native-build", because I saw that it was using 1.6.0 although
> 1.9.0
> > was available. After this change, other ticket was needed to build and
> > update the image in Dockerhub.
> >
> > I think this task (update file, build image and update image) should be
> > part of the release process. Otherwise, the image will be outdated once
> > there is a new release. And now that 1.11.0 is closer, I think its a good
> > moment to do it.
> >
> > What do you think?
> >
> > BR/
> >
> > Alberto B.
> >
>

Re: [DISCUSS] Add GEODE-7261 and GEODE-7241 to release/1.9.2

[Dick Cavender]

+1 for both fixes and the original list


On Mon, Oct 7, 2019 at 5:00 PM Owen Nichols  wrote:

> Sounds like a big win for convenience, and clearly a regression relative
> to the last release of Geode that SBDG picked up (1.6).  Thanks for
> clarifying what is at stake.
>
> +1 for including both fixes
>
> > On Oct 7, 2019, at 4:50 PM, Udo Kohlmeyer  wrote:
> >
> > Hi there Owen,
> >
> > I apologize if it is not clear.
> >
> > GEODE-7241 is a regression where the published artifact "geode-web" and
> "geode-web-api" were published as jars and not wars.
> >
> > NOW, why is it critical for 1.9.x... Well, the answer is fairly short.
> In Spring Data Geode, there is an ability to start/bootstrap a server using
> Spring Data Geode(SDG) only. This feature can be used for testing as well
> as starting a Server using SDG. In order to start the server using SDG, all
> that is required is to add the geode-web + geode-web-api artifacts onto the
> classpath as a maven/gradle dependency. There is no more requirement to
> download the project and reference libs or using GFSH to start the server.
> >
> > WHEN the extension went from war -> jar, this functionality was broken.
> The latest version of SDG (2.2.x) will be based on Geode 1.9. and not 1.10+
> which means that SDG will not gain that functionality. SDG would have to
> wait for its next release 2.3.x, which is still quite some way off.
> >
> > Usually this is not a big thing, but given Spring's prescribed manner of
> handling versions of dependent libraries, the version of Geode cannot be
> changed and only patch versions are allowed. So, in order to address the
> regression, a patch to 1.9.x is requested.
> >
> > Hope that this explains it a little better.
> >
> > --Udo
> >
> > On 10/7/19 3:50 PM, Owen Nichols wrote:
> >> I don’t yet have a clear understanding of what makes these critical,
> >> especially GEODE-7241. Can you elaborate, including:
> >> * Are these fixes already in 1.10?  If not, would a 1.10.1 patch be
> >> required as well?
> >> * What is the impact of not including each of these fixes?  Is there a
> >> workaround?
> >>
> >> On Fri, Oct 4, 2019 at 10:44 AM Jens Deppe  wrote:
> >>
> >>> I'd like to propose adding these two fixes to release/1.9.2
> >>>
> >>> GEODE-7261 ensures that the Admin REST service can start when Spring
> Boot
> >>> Data Geode is used to launch a server.
> >>>
> >>> GEODE-7241 publishes our various war artifacts to maven. This ensures
> that,
> >>> in the context of starting a SBDG server, the necessary REST wars can
> be
> >>> made available in order to start the required REST services.
> >>>
> >>> Thanks
> >>>
> >>> --Jens
> >>>
>
>

Lingering Geode 1.10.0 release issues

[Dick Cavender]

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 the "add 1.10.0 to old versions" post
release change because it was causing tests to fail. Until new JIRA
GEODE-7250 is fixed we will not be testing 1.10.0 as an old version. This
JIRA needs to be prioritized and the PR with the fix needs to include the
revert changes to get 1.10.0 back in the old versions.

Let me know if anyone has questions on these.

-Dick

[DISCUSS] Geode 1.11.0 dependency update

[Dick Cavender]

With the release of Geode 1.10.0 the window opens to apply Nick's Geode
dependency update process with time to shake it out before the 1.11.0
release.

His proposal can be found here:
https://cwiki.apache.org/confluence/display/GEODE/%5BDiscussion%5D+Geode+dependency+update+process


Additionally the original email discuss thread can be found searching for
subject: "[DISCUSS] Geode dependency update process (review by 8/28/2019)"

His proposal suggests that the dependency update task be something that the
Geode Release Manager would do post release. While it may be that a RM can
eventually do this until the actual update process, verification and
documenting is defined it seems like this should be a geode community
effort the first time around.

Nick has generously offered to head up the initial process and to use the
Geode 1.10.0 release as an opportunity to kickoff his proposal. Thanks Nick!

[ANNOUNCE] Apache Geode 1.10.0

[Dick Cavender]

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.10.0.

Apache Geode is a data management platform that provides a database-like
consistency model, reliable transaction processing and a shared-nothing
architecture to maintain very low latency performance with high concurrency
processing.

This Geode 1.10.0 quarterly release contains a number of improvements
and bug fixes.

Users are encouraged to upgrade to the latest release.

For the full list of changes please review the release notes:

https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.10.0


The release artifacts can be downloaded from the project
website:http://geode.apache.org/releases/

The release documentation is available at:

https://geode.apache.org/docs/guide/110/about_geode.html


We would like to thank all the contributors that made the release possible.

Regards,

Dick Cavender on behalf of the Apache Geode team

dockerhub mojo

[Dick Cavender]

Can someone with the ability give my docker hub account (docdixie)
permissions to upload the new geode 1.10.0 docker image?

Thanks!

[VOTE] Apache Geode 1.10.0.RC2

[Dick Cavender]

It's past the announced deadline and we have enough votes to close the
voting.

Voting status
==
+1: 7 binding votes, 2 non-binding votes
* Dave Barnes (PMC member)
* Anthony Baker (PMC Member)
* Jinmei Liao (PMC member)
* Jacob Barrett  (PMC member)
* Dan Smith (PMC member)
* Udo Kohlmeyer (PMC member)
* Kirk Lund (PMC member)
* Owen Nichols (Non-binding)
* Aaron Lindsey (Non-binding)

+0: zero votes

-0: zero votes

-1: zero votes

The voting meets the requirements of at least 3 PMC members with +1 votes and
has the required majority of +1 votes.

Apache Geode 1.10.0 passes the vote so I will finalize the release shortly.

Thanks everyone for the great work!

Dick Cavender

[VOTE] Apache Geode 1.10.0.RC2

[Dick Cavender]

Hello Geode dev community,

This is a release candidate for Apache Geode, version 1.10.0.RC2.
Thanks to all the community members for their contributions to this release!

Please do a review and give your feedback including the checks performed.
The voting deadline is *3PM PST Wed, September 25 2019*.

This candidate has passed RC Qualification checks (NEW) which can be found
at:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-10-0-rc

Release notes can be found at:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.10.0

Please note that we are voting upon the source tags: *rel/v1.10.0.RC2*

Apache Geode:
https://github.com/apache/geode/tree/rel/v1.10.0.RC2
Apache Geode examples:
https://github.com/apache/geode-examples/tree/rel/v1.10.0.RC2
Apache Geode native:
https://github.com/apache/geode-native/tree/rel/v1.10.0.RC2

Source and binary files:
https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC2/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1059

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=
https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC2
-PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1059
build runAll

Regards
Dick Cavender

Re: [VOTE] Adding a lucene specific fix to release/1.10.0

[Dick Cavender]

This problem has happened before, and will probably happen in the future.
Recently we adjusted the Geode release process to dictate that the Geode
release manager will handle the merging of approved changes to a release
branch while also allowing the community time for input and discussion on
those. In this case, neither happened. The change was merged by the
committer as soon as there were three votes and I as the release manager
failed to communicate the intended process to them before that happened.

This process needs to be an on-going discussion for us as a community.
What, when and how changes come into a release branch after creation and
until its release. It's enough to scare off future Release Manager
volunteers if not solved.

The GEODE-7208 change is already moving through the 1.10.0 pipeline and is
(at the moment) the final change for 1.10.0.RC2 moving us closer to
release.

Udo- would you consider making your vote a +0 and then being part of the
future work towards improving this part of the process rather than having
to revert the change due to your minus one?


On Thu, Sep 19, 2019 at 1:17 PM Udo Kohlmeyer  wrote:

> -1
>
> I must agree with Owen's analysis.
>
> It's a known problem, and it will not cause the system to stop working.
> Yes, it is a bug and will cause issues with results, BUT it will NOT
> affect the stability of the system. Which is one of the only reasons we
> should be adding fixes to an already cut release branch.
>
> --Udo
>
> On 9/19/19 11:48 AM, Owen Nichols wrote:
> > Thank you for providing some context for what is being voted here.
> Based on this information, I will give my vote as “+0” (imho it may not
> meet the definition of a “critical fix”, but seems like the risk is low and
> the community wants it, so I have no real objection).
> >
> >
> >> On Sep 19, 2019, at 11:38 AM, Xiaojian Zhou  wrote:
> >>
> >> Owen:
> >> Here are the answers:
> >>
> >> - Is this fixing an issue of Data loss? Performance degradation?
> >> Backward-compatibility issue? Availability impacts?  Resource exhaustion
> >> (threads, disk, cpu, memory, sockets, etc)?
> >>
> >> Without the fix, fields in the inherited attributes cannot be indexed,
> if
> >> it's user object. For example, I have a Customer class, which contains
> >> phoneBook. I have a subclass LocalCustomer to inherit Customer class,
> then
> >> I cannot index on phoneBook.
> >>
> >> - Did this issue exist in the previous release?
> >> Yes.
> >>
> >> - What is the impact of not fixing it?
> >> Customer will see it and they have seen it.
> >>
> >> - What are the risks of introducing this change so close to shipping?
> >> No risk. It's standalone fix. Not to impact any where else. And it will
> be
> >> backported in future if we did not do it now.
> >>
> >> - How extensively has the fix been tested on develop?
> >> We introduced several dunit and junit tests.
> >>
> >> - How “sensitive” is the area of code it touches?
> >> Not sensitive.
> >>
> >> - What new tests have been added?
> >> New dunit tests and junit tests.
> >>
> >> Regards
> >> Gester
> >>
> >> On Thu, Sep 19, 2019 at 11:21 AM Owen Nichols 
> wrote:
> >>
>  On Sep 19, 2019, at 11:15 AM, Xiaojian Zhou  wrote:
> 
>  Owen:
> 
>  The reason is: it's already cherry-picked to 1.9.
> >>>
> >>> Can you kindly point me to the specific SHA where this was fixed in
> 1.9?
> >>> I am not able to find it...
> >>>
>  Gester
> 
>  On Thu, Sep 19, 2019 at 11:13 AM Owen Nichols 
> >>> wrote:
> > It looks like this has already passed the vote, but I don’t see an
> > explanation anywhere in this thread for what makes this a "critical
> >>> fix".
> > As I recall release/1.10.0 was branched at the beginning of August,
> so
> >>> it
> > seems appropriate to apply a very high level of scrutiny to any
> >>> continuing
> > proposals to further delay the release of 1.10.0.
> >
> > - Is this fixing an issue of Data loss? Performance degradation?
> > Backward-compatibility issue? Availability impacts?  Resource
> exhaustion
> > (threads, disk, cpu, memory, sockets, etc)?
> > - Did this issue exist in the previous release?
> > - What is the impact of not fixing it?
> > - What are the risks of introducing this change so close to shipping?
> > - How extensively has the fix been tested on develop?
> > - How “sensitive” is the area of code it touches?
> > - What new tests have been added?
> >
> >
> >> On Sep 19, 2019, at 11:08 AM, Anilkumar Gingade <
> aging...@pivotal.io>
> > wrote:
> >> +1
> >>
> >> On Thu, Sep 19, 2019 at 11:02 AM Eric Shu  wrote:
> >>
> >>> +1
> >>>
> >>>
> >>> On Thu, Sep 19, 2019 at 10:59 AM Benjamin Ross 
> > wrote:
>  +1
> 
>  On Thu, Sep 19, 2019 at 10:50 AM Nabarun Nag 
> >>> wrote:
> > +1
> >
> > On Thu, Sep 19, 2019 at 10:49 AM Xiaojian Zhou  >
> >>> wrote:
> >> I want to 

Re: [VOTE] Adding new AEQ feature to release/1.10.0

[Dick Cavender]

Naba-

Do you have this PR ready to merge to release/1.10.0 since we seem to have
the votes for this to happen?



On Mon, Sep 16, 2019 at 7:08 AM Jens Deppe  wrote:

> +1
>
> On Mon, Sep 16, 2019 at 3:08 AM Juan José Ramos  wrote:
>
> > +1
> >
> > On Fri, Sep 13, 2019 at 11:59 PM Ryan McMahon 
> > wrote:
> >
> > > +1
> > >
> > > On Fri, Sep 13, 2019 at 3:58 PM Donal Evans 
> wrote:
> > >
> > > > +1
> > > >
> > > > On Fri, Sep 13, 2019 at 3:37 PM Benjamin Ross 
> > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Fri, Sep 13, 2019 at 3:25 PM Anilkumar Gingade <
> > aging...@pivotal.io
> > > >
> > > > > wrote:
> > > > >
> > > > > > +1. This is needed for spring data-geode; whose upcoming release
> is
> > > > based
> > > > > > on older geode version.
> > > > > >
> > > > > > -Anil.
> > > > > >
> > > > > >
> > > > > > On Fri, Sep 13, 2019 at 3:23 PM Nabarun Nag 
> > wrote:
> > > > > >
> > > > > > > Hi Geode Community ,
> > > > > > >
> > > > > > > [GEODE-7121]
> > > > > > >
> > > > > > > I would like to include the new feature of creating AEQs with a
> > > > paused
> > > > > > > event processor to the release 1.10 branch. This also includes
> > the
> > > > > > feature
> > > > > > > to resume the AEQ at a later point in time.
> > > > > > > This feature includes addition of new/modified APIs and gfsh
> > > > commands.
> > > > > > >
> > > > > > > [All details about this feature has been discussed in a
> previous
> > > > > discuss
> > > > > > > thread]
> > > > > > >
> > > > > > > These are the commits that needs to be in release 1.10.0
> branch.
> > > > > > > f6e11084daa30791f7bbf9a8187f6d1bc9c4b91a
> > > > > > > 615d3399d24810126a6d57b5163f7afcd06366f7
> > > > > > > 1440a95e266e671679a623f93865c5e7e683244f
> > > > > > > 42e07dc9054794657acb40c292f3af74b79a1ea6
> > > > > > > e1f200e2f9e77e986d250fde3848dc004b26a7c2
> > > > > > > 5f70160fba08a06c7e1fc48c7099e63dd1a0502b
> > > > > > > 0645446ec626bc351a2c881e4df6a4ae2e75fbfc
> > > > > > > 575c6bac115112df1e84455b052566c75764b0be
> > > > > > > 3d9627ff16443f4aa513a67bcc284e68953aff8a
> > > > > > > ea22e72916f8e34455800d347690e483727f9bf5
> > > > > > > 8d26d595f5fb94ff703116eb91bb747e9ba7f536
> > > > > > >
> > > > > > > Will create a PR ASAP.
> > > > > > >
> > > > > > > Regards
> > > > > > > Nabarun Nag
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> > Juan José Ramos Cassella
> > Senior Software Engineer
> > Email: jra...@pivotal.io
> >
>

Re: Propose including GEODE-7178 in 1.10

[Dick Cavender]

This has been merged to release/1.10.0.



On Fri, Sep 13, 2019 at 11:14 AM Dick Cavender  wrote:

> We have 3 plus one votes so we'll merge this as soon as the PR checks
> complete.
>
> -Dick
>
>
> On Fri, Sep 13, 2019 at 10:25 AM Blake Bender  wrote:
>
>> +1, IMO this really needs to go in.
>>
>> Thanks,
>>
>> Blake
>>
>>
>> On Thu, Sep 12, 2019 at 3:30 PM Anthony Baker  wrote:
>>
>> > My understanding is that this portion of the protocol is determined by
>> > instanceof checks, not the ordinal version.  The messages from the java
>> > client went through a different code path than messages from the native
>> > client.  So java clients using ordinal 45 still work (that’s why our
>> > backwards compatibility tests don’t fail).
>> >
>> > Anthony
>> >
>> >
>> > > On Sep 12, 2019, at 2:34 PM, Dan Smith  wrote:
>> > >
>> > > +1 for getting this in 1.10.
>> > >
>> > > I am curious though - is the native client behaving like an older
>> > versions
>> > > of the java client, or is this totally unique behavior for the native
>> > > client? Is there some integration test that we are missing here?
>> > >
>> > > -Dan
>> > >
>> > > On Thu, Sep 12, 2019 at 11:52 AM Michael Oleske 
>> > wrote:
>> > >
>> > >> Here is the Pull Request for the cherry pick as requested
>> > >> https://github.com/apache/geode/pull/4049
>> > >>
>> > >> -michael
>> > >>
>> > >> On Thu, Sep 12, 2019 at 10:28 AM Dick Cavender > >
>> > >> wrote:
>> > >>
>> > >>> Hi Michael, thank you for bringing your concern and fixing this
>> issue.
>> > >>>
>> > >>> Geode's release process dictates a time-based schedule <
>> > >>> https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule>
>> to
>> > >> cut
>> > >>> release branches.  The “critical fixes” rule does allow critical
>> fixes
>> > to
>> > >>> be brought to the release branch by proposal on the dev list, as you
>> > have
>> > >>> done here.
>> > >>>
>> > >>> If there is consensus from the Geode community that your proposed
>> > change
>> > >>> satisfies the “critical fixes” rule, I will be happy to bring it to
>> the
>> > >>> 1.10.0 release branch.
>> > >>>
>> > >>> Due to the complexity of this change, could please open a PR against
>> > >>> release/1.10.0 containing the exact changes you want to merge?
>> > >>>
>> > >>> Regards
>> > >>>
>> > >>> -Dick
>> > >>>
>> > >>>
>> > >>> On Thu, Sep 12, 2019 at 10:23 AM Anthony Baker 
>> > >> wrote:
>> > >>>
>> > >>>> +1 yes please!
>> > >>>>
>> > >>>>> On Sep 12, 2019, at 10:11 AM, Michael Oleske 
>> > >>> wrote:
>> > >>>>>
>> > >>>>> Hi Geode Devs!
>> > >>>>>
>> > >>>>> I'd like to propose including the fix for GEODE-7178.  This
>> resolves
>> > >> an
>> > >>>>> issue that Ivan (https://markmail.org/message/dwwac42xmpo4xb2e)
>> ran
>> > >>>> into in
>> > >>>>> 1.10 RC1.
>> > >>>>>
>> > >>>>> SHA: 91176d61df64bf1390cdba7b1cdc2b40cdfaba3a
>> > >>>>> Link to GitHub:
>> > >>>>>
>> > >>>>
>> > >>>
>> > >>
>> >
>> https://github.com/apache/geode/commit/91176d61df64bf1390cdba7b1cdc2b40cdfaba3a
>> > >>>>>
>> > >>>>> Thanks!
>> > >>>>> -michael
>> > >>>>
>> > >>>>
>> > >>>
>> > >>
>> >
>> >
>>
>

Re: Propose including GEODE-7178 in 1.10

[Dick Cavender]

We have 3 plus one votes so we'll merge this as soon as the PR checks
complete.

-Dick


On Fri, Sep 13, 2019 at 10:25 AM Blake Bender  wrote:

> +1, IMO this really needs to go in.
>
> Thanks,
>
> Blake
>
>
> On Thu, Sep 12, 2019 at 3:30 PM Anthony Baker  wrote:
>
> > My understanding is that this portion of the protocol is determined by
> > instanceof checks, not the ordinal version.  The messages from the java
> > client went through a different code path than messages from the native
> > client.  So java clients using ordinal 45 still work (that’s why our
> > backwards compatibility tests don’t fail).
> >
> > Anthony
> >
> >
> > > On Sep 12, 2019, at 2:34 PM, Dan Smith  wrote:
> > >
> > > +1 for getting this in 1.10.
> > >
> > > I am curious though - is the native client behaving like an older
> > versions
> > > of the java client, or is this totally unique behavior for the native
> > > client? Is there some integration test that we are missing here?
> > >
> > > -Dan
> > >
> > > On Thu, Sep 12, 2019 at 11:52 AM Michael Oleske 
> > wrote:
> > >
> > >> Here is the Pull Request for the cherry pick as requested
> > >> https://github.com/apache/geode/pull/4049
> > >>
> > >> -michael
> > >>
> > >> On Thu, Sep 12, 2019 at 10:28 AM Dick Cavender 
> > >> wrote:
> > >>
> > >>> Hi Michael, thank you for bringing your concern and fixing this
> issue.
> > >>>
> > >>> Geode's release process dictates a time-based schedule <
> > >>> https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule>
> to
> > >> cut
> > >>> release branches.  The “critical fixes” rule does allow critical
> fixes
> > to
> > >>> be brought to the release branch by proposal on the dev list, as you
> > have
> > >>> done here.
> > >>>
> > >>> If there is consensus from the Geode community that your proposed
> > change
> > >>> satisfies the “critical fixes” rule, I will be happy to bring it to
> the
> > >>> 1.10.0 release branch.
> > >>>
> > >>> Due to the complexity of this change, could please open a PR against
> > >>> release/1.10.0 containing the exact changes you want to merge?
> > >>>
> > >>> Regards
> > >>>
> > >>> -Dick
> > >>>
> > >>>
> > >>> On Thu, Sep 12, 2019 at 10:23 AM Anthony Baker 
> > >> wrote:
> > >>>
> > >>>> +1 yes please!
> > >>>>
> > >>>>> On Sep 12, 2019, at 10:11 AM, Michael Oleske 
> > >>> wrote:
> > >>>>>
> > >>>>> Hi Geode Devs!
> > >>>>>
> > >>>>> I'd like to propose including the fix for GEODE-7178.  This
> resolves
> > >> an
> > >>>>> issue that Ivan (https://markmail.org/message/dwwac42xmpo4xb2e)
> ran
> > >>>> into in
> > >>>>> 1.10 RC1.
> > >>>>>
> > >>>>> SHA: 91176d61df64bf1390cdba7b1cdc2b40cdfaba3a
> > >>>>> Link to GitHub:
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://github.com/apache/geode/commit/91176d61df64bf1390cdba7b1cdc2b40cdfaba3a
> > >>>>>
> > >>>>> Thanks!
> > >>>>> -michael
> > >>>>
> > >>>>
> > >>>
> > >>
> >
> >
>

Re: Propose including GEODE-7178 in 1.10

[Dick Cavender]

Hi Michael, thank you for bringing your concern and fixing this issue.

Geode's release process dictates a time-based schedule <
https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule> to cut
release branches.  The “critical fixes” rule does allow critical fixes to
be brought to the release branch by proposal on the dev list, as you have
done here.

If there is consensus from the Geode community that your proposed change
satisfies the “critical fixes” rule, I will be happy to bring it to the
1.10.0 release branch.

Due to the complexity of this change, could please open a PR against
release/1.10.0 containing the exact changes you want to merge?

Regards

-Dick


On Thu, Sep 12, 2019 at 10:23 AM Anthony Baker  wrote:

> +1 yes please!
>
> > On Sep 12, 2019, at 10:11 AM, Michael Oleske  wrote:
> >
> > Hi Geode Devs!
> >
> > I'd like to propose including the fix for GEODE-7178.  This resolves an
> > issue that Ivan (https://markmail.org/message/dwwac42xmpo4xb2e) ran
> into in
> > 1.10 RC1.
> >
> > SHA: 91176d61df64bf1390cdba7b1cdc2b40cdfaba3a
> > Link to GitHub:
> >
> https://github.com/apache/geode/commit/91176d61df64bf1390cdba7b1cdc2b40cdfaba3a
> >
> > Thanks!
> > -michael
>
>

Re: [VOTE] Apache Geode 1.10.0.RC1

[Dick Cavender]

The 1.10.RC1 is being pulled for this change and we'll have an RC2 rolling
out later today.

-Dick


On Mon, Sep 9, 2019 at 9:02 AM Dan Smith  wrote:

> +1 to getting the source build fix into 1.10.
>
> -Dan
>
> On Fri, Sep 6, 2019 at 5:58 PM Owen Nichols  wrote:
>
> > +1 for catching the correct grgit exception so Geode can compile from
> > src.tgz distribution.  I might have gone further and just changed it to
> > catch Exception, but it looks like the GrGit project has been stable for
> > the last 2 years <
> >
> https://github.com/ajoberstar/grgit/blob/master/grgit-core/src/main/groovy/org/ajoberstar/grgit/operation/OpenOp.groovy
> >
> > on throwing IllegalStateException, so this fix should be solid.  I tested
> > locally and confirmed it solves the problem.
> >
> > > On Sep 6, 2019, at 2:24 PM, Robert Houghton 
> > wrote:
> > >
> > > +1  to bringing the build-from-source name to 1.10
> > > -1 to RC1 until then
> > >
> > > On Fri, Sep 6, 2019, 14:21 Owen Nichols  wrote:
> > >
> > >> Hi Anthony, thank you for bringing your concern.
> > >>
> > >> If there is consensus from the Geode community that your proposed fix
> > >> satisfies the “critical fixes” rule, I will be happy to bring it to
> the
> > >> release/1.10.0 release branch.
> > >>
> > >> Regards
> > >> Dick & Owen
> > >>
> > >>> On Sep 6, 2019, at 2:18 PM, Anthony Baker  wrote:
> > >>>
> > >>> Please pull aaa1378472ce0a8a05e0afabfdfc874e14fe13e6 into the release
> > >> branch to fix the build problem.
> > >>>
> > >>> Anthony
> > >>>
> > >>>
> > >>>> On Sep 6, 2019, at 11:29 AM, Dick Cavender 
> > >> wrote:
> > >>>>
> > >>>> The 1.10.0 voting has been extended until Monday, September 9th at
> > 3pm.
> > >>>>
> > >>>> To all- please update your 1.10.0 vote if/when your issue(s) have
> been
> > >>>> resolved. There are still no -1 votes at this time.
> > >>>>
> > >>>> On Fri, Sep 6, 2019 at 9:32 AM Nabarun Nag  wrote:
> > >>>>
> > >>>>> Hi Anthony,
> > >>>>>
> > >>>>> I had faced this issue in the current develop too. One way to get
> > >> around it
> > >>>>> is to run ./gradlew spotlessApply independently before the build.
> > >>>>>
> > >>>>> Regards
> > >>>>> Naba
> > >>>>>
> > >>>>>
> > >>>>> On Fri, Sep 6, 2019 at 8:53 AM Anthony Baker 
> > >> wrote:
> > >>>>>
> > >>>>>> This seems to be a simple change to catch IllegalStateException
> > >> instead
> > >>>>> of
> > >>>>>> IllegalArgumentException in build.gradle.
> > >>>>>>
> > >>>>>> But I’m also getting a ton of spotless errors like:
> > >>>>>>
> > >>>>>>> Task :geode-cq:spotlessJava FAILED
> > >>>>>> Step 'removeUnusedImports' found problem in
> > >>>>>>
> > >>>>>
> > >>
> >
> 'geode-cq/src/test/java/org/apache/geode/cache/query/internal/cq/CqServiceUnitTest.java':
> > >>>>>> null
> > >>>>>> java.lang.reflect.InvocationTargetException
> > >>>>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> > >>>>>>  at
> > >>>>>>
> > >>>>>
> > >>
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > >>>>>>  at
> > >>>>>>
> > >>>>>
> > >>
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > >>>>>>  at java.lang.reflect.Method.invoke(Method.java:498)
> > >>>>>>  at
> > >>>>>>
> > >>>>>
> > >>
> >
> com.diffplug.spotless.java.GoogleJavaFormatStep$State.lambda$createRemoveUnusedImportsOnly$1(GoogleJavaFormatStep.java:153)
> > >>>>>>  at
> > >>>>> com.diffplug.spotless.FormatterFunc.apply(FormatterFunc.j

Re: [VOTE] Apache Geode 1.10.0.RC1

[Dick Cavender]

ceptorImpl.java:666)
> > >>>
> > >>> at
> >
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> > >>>
> > >>> at java.lang.Thread.run(Thread.java:748)
> > >>>
> > >>> ) happened at remote server.
> > >>>
> > >>>
> > >>> On Thu, Sep 5, 2019 at 9:00 PM Nabarun Nag  wrote:
> > >>>
> > >>>> Thank you Dan for the explanation.
> > >>>>
> > >>>> Regards
> > >>>> Naba
> > >>>>
> > >>>>
> > >>>> On Thu, Sep 5, 2019 at 4:34 PM Dan Smith  wrote:
> > >>>>
> > >>>>> Hi Naba,
> > >>>>>
> > >>>>> This sanctioned-serializable stuff is not an issue.
> > >>>>>
> > >>>>> When you removed those files from
> > sanctioned-geode-core-serializables,
> > >>>> they
> > >>>>> get rejected by the serialization filter. Look at the error message
> > you
> > >>>> see
> > >>>>> when you remove them - it is failing to serialize a class that has
> a
> > >>>>> *nested* EvictionAttributes.
> > >>>>>
> > >>>>> Those classes need to be in the sanctioned file, if they are
> > embedded in
> > >>>>> another serialized object. They are probably not showing up in the
> > >>>>> actualSerializables file because they are DataSerializable.
> > >>>>>
> > >>>>> -Dan
> > >>>>>
> > >>>>> On Thu, Sep 5, 2019 at 3:49 PM Kirk Lund  wrote:
> > >>>>>
> > >>>>>> Ah, ok. I think I see what you're asking about. I don't have an
> > answer,
> > >>>>> but
> > >>>>>> someone else such as Bruce could explain it.
> > >>>>>>
> > >>>>>> /Users/klund/dev/geode3 [610]$ diff
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> >
> geode-core/src/main/resources/org/apache/geode/internal/sanctioned-geode-core-serializables.txt
> > >>>>>> geode-core/build/integrationTest/actualSerializables.dat
> > >>>>>> 69d68
> > >>>>>> < org/apache/geode/cache/EvictionAttributes,false
> > >>>>>> 71d69
> > >>>>>> < org/apache/geode/cache/ExpirationAttributes,false
> > >>>>>> 79d76
> > >>>>>> < org/apache/geode/cache/MembershipAttributes,false
> > >>>>>> 99d95
> > >>>>>> < org/apache/geode/cache/SubscriptionAttributes,false
> > >>>>>> 262d257
> > >>>>>> < org/apache/geode/internal/cache/EvictionAttributesImpl,false
> > >>>>>> 276d270
> > >>>>>> < org/apache/geode/internal/cache/PartitionAttributesImpl,false
> > >>>>>> 517d510
> > >>>>>> <
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> >
> org/apache/geode/management/internal/cli/functions/CacheRealizationFunction,false
> > >>>>>>
> > >>>>>> On Thu, Sep 5, 2019 at 3:44 PM Nabarun Nag 
> wrote:
> > >>>>>>
> > >>>>>>> Hi Kirk,
> > >>>>>>>
> > >>>>>>> The test does not fail.
> > >>>>>>> When you run the test (testSerializable) it creates a list of
> > >>>>>> serializable
> > >>>>>>> classes and puts it in the actualSerializables.dat file and them
> > >>>>> compares
> > >>>>>>> if all the classes listed are present in the
> > >>>>>>> sanctioned-geode-core-serializables.txt.
> > >>>>>>> If we did not change any serializabale classes then these two
> files
> > >>>>>>> remain the same. However now in this release, there are classes
> in
> > >>>>>>> sanctioned-geode-core-serializables.txt which are not present in
> > >>>>>>> actualSerializables.dat.
> > >>>>>>>
> > >>&

Re: [VOTE] Apache Geode 1.10.0.RC1

[Dick Cavender]

We manually signed the apache-geode-1.10.0-src.tgz dist and uploaded the
asc file.

Unclear on why this is no longer automatically generated as part of the
build step as 1.9.1 it was generated correctly. We have worked around it in
the prepare_rc.sh adding a check for it going forward and generating it if
missing.


On Wed, Sep 4, 2019 at 3:32 PM Dan Smith  wrote:

> I don't see a .asc signature file for apache-geode-1.10.0-src.tgz. Did we
> miss that signature file somehow?
>
> -Dan
>
> On Wed, Sep 4, 2019 at 9:33 AM Dick Cavender  wrote:
>
> > The apache-geode-native-1.10.0-src.tar.gz dist has been fixed in RC1 and
> > can be found at:
> https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC1/
> > Please continue to review RC1 as a viable 1.10 RC. The voting deadline
> > remains 3PM PST Thursday Sept 5th.
> >
> > -Dick
> >
> >
> > On Tue, Sep 3, 2019 at 3:09 PM Dan Smith  wrote:
> >
> > > Everything but the missing native source looks good. If we can fix
> that,
> > > I'll +1 this RC.
> > >
> > > -Dan
> > >
> > > On Tue, Sep 3, 2019 at 2:26 PM Dan Smith  wrote:
> > >
> > > > -1 It looks like this RC is also missing the native source, just like
> > > > 1.9.1.RC3. The tar file is there, but it is empty.
> > > >
> > > > -Dan
> > > >
> > > > On Fri, Aug 30, 2019 at 2:06 PM Dick Cavender 
> > > > wrote:
> > > >
> > > >> Hello Geode dev community,
> > > >>
> > > >> This is a release candidate for Apache Geode, version 1.10.0.RC1.
> > > >> Thanks to all the community members for their contributions to this
> > > >> release!
> > > >>
> > > >> Please do a review and give your feedback. The deadline is 3PM PST
> > > >> Thursday
> > > >> Sept 5th.
> > > >> Release notes can be found at:
> > > >>
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.10.0
> > > >>
> > > >> Please note that we are voting upon the source tags: rel/v1.10.0.RC1
> > > >>
> > > >> Apache Geode:
> > > >> https://github.com/apache/geode/tree/rel/v1.10.0.RC1
> > > >> Apache Geode examples:
> > > >> https://github.com/apache/geode-examples/tree/rel/v1.10.0.RC1
> > > >> Apache Geode native:
> > > >> https://github.com/apache/geode-native/tree/rel/v1.10.0.RC1
> > > >>
> > > >> Source and binary files:
> > > >> https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC1/
> > > >>
> > > >> Maven staging repo:
> > > >>
> > https://repository.apache.org/content/repositories/orgapachegeode-1058
> > > >>
> > > >> Geode's KEYS file containing PGP keys we use to sign the release:
> > > >> https://github.com/apache/geode/blob/develop/KEYS
> > > >>
> > > >> PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=
> > > >> https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC1
> > > >> -PgeodeRepositoryUrl=
> > > >>
> > https://repository.apache.org/content/repositories/orgapachegeode-1058
> > > >> build runAll
> > > >>
> > > >> Regards
> > > >> Dick Cavender
> > > >>
> > > >
> > >
> >
>

Re: [VOTE] Apache Geode 1.10.0.RC1

[Dick Cavender]

The apache-geode-native-1.10.0-src.tar.gz dist has been fixed in RC1 and
can be found at: https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC1/
Please continue to review RC1 as a viable 1.10 RC. The voting deadline
remains 3PM PST Thursday Sept 5th.

-Dick


On Tue, Sep 3, 2019 at 3:09 PM Dan Smith  wrote:

> Everything but the missing native source looks good. If we can fix that,
> I'll +1 this RC.
>
> -Dan
>
> On Tue, Sep 3, 2019 at 2:26 PM Dan Smith  wrote:
>
> > -1 It looks like this RC is also missing the native source, just like
> > 1.9.1.RC3. The tar file is there, but it is empty.
> >
> > -Dan
> >
> > On Fri, Aug 30, 2019 at 2:06 PM Dick Cavender 
> > wrote:
> >
> >> Hello Geode dev community,
> >>
> >> This is a release candidate for Apache Geode, version 1.10.0.RC1.
> >> Thanks to all the community members for their contributions to this
> >> release!
> >>
> >> Please do a review and give your feedback. The deadline is 3PM PST
> >> Thursday
> >> Sept 5th.
> >> Release notes can be found at:
> >>
> >>
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.10.0
> >>
> >> Please note that we are voting upon the source tags: rel/v1.10.0.RC1
> >>
> >> Apache Geode:
> >> https://github.com/apache/geode/tree/rel/v1.10.0.RC1
> >> Apache Geode examples:
> >> https://github.com/apache/geode-examples/tree/rel/v1.10.0.RC1
> >> Apache Geode native:
> >> https://github.com/apache/geode-native/tree/rel/v1.10.0.RC1
> >>
> >> Source and binary files:
> >> https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC1/
> >>
> >> Maven staging repo:
> >> https://repository.apache.org/content/repositories/orgapachegeode-1058
> >>
> >> Geode's KEYS file containing PGP keys we use to sign the release:
> >> https://github.com/apache/geode/blob/develop/KEYS
> >>
> >> PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=
> >> https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC1
> >> -PgeodeRepositoryUrl=
> >> https://repository.apache.org/content/repositories/orgapachegeode-1058
> >> build runAll
> >>
> >> Regards
> >> Dick Cavender
> >>
> >
>

[VOTE] Apache Geode 1.10.0.RC1

[Dick Cavender]

Hello Geode dev community,

This is a release candidate for Apache Geode, version 1.10.0.RC1.
Thanks to all the community members for their contributions to this release!

Please do a review and give your feedback. The deadline is 3PM PST Thursday
Sept 5th.
Release notes can be found at:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.10.0

Please note that we are voting upon the source tags: rel/v1.10.0.RC1

Apache Geode:
https://github.com/apache/geode/tree/rel/v1.10.0.RC1
Apache Geode examples:
https://github.com/apache/geode-examples/tree/rel/v1.10.0.RC1
Apache Geode native:
https://github.com/apache/geode-native/tree/rel/v1.10.0.RC1

Source and binary files:
https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC1/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachegeode-1058

Geode's KEYS file containing PGP keys we use to sign the release:
https://github.com/apache/geode/blob/develop/KEYS

PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=
https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC1
-PgeodeRepositoryUrl=
https://repository.apache.org/content/repositories/orgapachegeode-1058
build runAll

Regards
Dick Cavender

Re: Propose fix for 1.10 release: Prevent NPE in getLocalSize()

[Dick Cavender]

Hi Aaron, thank you for bringing your request and concern.

Geode's release process dictates a time-based schedule to cut release
branches.  Once cut, the “critical fixes” rule does allow those to be
brought

to the release branch by proposal on the dev list.

If there is consensus from the Geode community that your proposed
change satisfies the “critical fixes” rule we can bring it to the
1.10.0

release branch. There are a number of issues that will likely bring in
other changes this week. Udo can still vote -1 and hope any future
Spring requests

won't be affected :^)


I'll be unavailable the rest of the week starting tomorrow so Dan will
assist with approved merges to 1.10 until Owen is back on Monday.

Regards

Dick Cavender


On Tue, Aug 13, 2019 at 5:32 PM Udo Kohlmeyer  wrote:

> @Aaron, is this an existing issue (i.e this was not introduced in a
> current refactor)?
>
> If the answer is anything other that "This will make the system stop
> working", I would vote: -1
>
> If this is an existing issue and has been around for a while, I think we
> hold off including this.
>
> I think the boat has sailed on the inclusion of issues into the 1.10
> release. Sorry...
>
> --Udo
>
> On 8/13/19 4:58 PM, Aaron Lindsey wrote:
> > I’d like to propose including
> https://github.com/apache/geode/pull/3913/commits/6f1814d1f719cc06b13769c40a9d6d01f99f927c
> <
> https://github.com/apache/geode/pull/3913/commits/6f1814d1f719cc06b13769c40a9d6d01f99f927c>
> in the Geode 1.10 release.
> >
> > This commit fixes an issue where a NullPointerException is thrown from
> PartitionedRegion.getLocalSize() when the statistics callback sampler is
> invoked before a PartitionedRegion is initialized.
> >
> > - Aaron
> >
> >
> >
>

New release branch for Apache Geode 1.10.0

[Dick Cavender]

Hello Geode Dev Community,

We have created a new release branch for Apache Geode 1.10.0 -
"release/1.10.0"

Please do review and raise any concern with the release branch. If no
concerns are raised, we will start with the voting for the release
candidate soon.

Regards

Dick Cavender
Apache Geode 1.10.0 Release Manager

Re: [DISCUSS] Time to cut Geode 1.10.0?

[Dick Cavender]

In preparation for cutting the release branch have we confirmed that
Geode's LICENSE and NOTICE file been confirmed to accurately reflect what
is being shipped for v1.10?

>From Apache: http://www.apache.org/dev/licensing-howto.html
*"*The LICENSE and NOTICE files must exactly represent the contents of the
distribution they reside in."

Ideally this is kept up to date during development as the dependencies
change or are added but this often is missed and needs to be reconciled on
develop before we cut a release branch.

-Dick





On Tue, Jul 30, 2019 at 6:04 PM Owen Nichols  wrote:

> From that email:
>
> To make this work, it's important to be strict
> about cutting the release branch on the set date and only allow critical
> fixes after the release has been cut. Once we start compromising on this,
> we go down a slippery slope that ultimately leads to not getting the
> predictability benefits described here.
>
> We are perilously close to the "slippery slope”:
> * Geode 1.8.0 was announced on Dec 12 — almost 8 months ago
> * Geode 1.9.0 was announced on Apr 25 — putting us about 5 weeks late
> already on cutting the 1.10 branch
>
> It seems like the community reaction to branching from the SHA initially
> proposed is “woah, not quite yet”.
>
> To get last-minute stuff in (or out) and get back on track, I propose
> setting a strict CUT date for the 1.10 branch at 3PM PDT Thursday August 1.
>
> -Owen
>
>
> > On Jul 30, 2019, at 5:31 PM, Alexander Murmann 
> wrote:
> >
> > Hi Karen,
> >
> > Here is the previous discussion that was very positively received:
> >
> https://lists.apache.org/thread.html/d36a63c3794d13506ecad3d52a2aca938dcf0f8509b61860bbbc50cd@%3Cdev.geode.apache.org%3E
> >
> > However, JIRA tells me that GEODE-7013 is already fixed. If we were to go
> > with a SHA from this week, for which Jake also chimed in with plenty of
> > reasons, this should be in the release.
> >
> > On Tue, Jul 30, 2019 at 5:10 PM Karen Miller  wrote:
> >
> >> Alexander, can you point me at the policy decision for the "critical
> issue"
> >> rule you mention? I always though it was up
> >> to the release manager.
> >>
> >> I want GEODE-7013 fixes in because it is the right thing to do.  Our
> gfsh
> >> help/hint wasn't working the way we say that it did.
> >> With the fix, it does.  I want either the documentation to match the
> code,
> >> or I want the code to match the documentation.
> >> The fix in GEODE-7013 changes the code to match the existing
> documentation,
> >> so we don't have to change the documentation
> >> (which would have needed to be cherry-picked into our 1.10 release
> branch).
> >>
> >>
> >> On Tue, Jul 30, 2019 at 11:47 AM Owen Nichols 
> wrote:
> >>
> >>> Our "critical issue” rule has the effect that the bar to commit to
> >> develop
> >>> is “low”, but the bar to cherry-pick to support branch is “very high”.
> >>>
> >>> Contributors could plan around this disparity more easily if any of the
> >>> following were true:
> >>> - releases were more frequent
> >>> - planned cut date of release branch was announced in advance (rather
> >> than
> >>> retroactively)
> >>> - a process existed for making exceptions to the “critical issue” rule
> >>>
> >>> I agree that the proposed SHA looks like a relatively stable
> branchpoint
> >>> (coming near the end of a nice period of solid green in the pipeline),
> >> and
> >>> I acknowledge that fair warning was given a week ago that a branch was
> >>> “coming soon”, but I wonder if there is anything we can do to make the
> >>> rules for what gets in a release and what doesn’t feel a little less
> >>> arbitrary?
> >>>
> >>> -Owen
> >>>
> >>>
> >>>> On Jul 30, 2019, at 11:16 AM, Alexander Murmann 
> >>> wrote:
> >>>>
> >>>> Dick, thank you for stepping up!
> >>>>
> >>>> I think it's great to cut the branch sooner rather than later. There
> >>>> already is GEODE-7012 which introduces a distributed deadlock during
> >>>> startup. That seems like a critical issue to fix. That should be able
> >> to
> >>>> happen after we cut the branch though.
> >>>>
> >>>> Karen, I wonder if that could be merged after the branch got cut, but
> >>> also
> >>>> wonder if that fits our "c

Re: [DISCUSS] Time to cut Geode 1.10.0?

[Dick Cavender]

I'll take on the Release Manager role for Geode 1.10 with the 1.9.0 release
manager's help (Owen:).

I'd like to propose cutting the release/1.10 branch off develop sha:
dc6890107a2651d8ba1450e8db8a1c39d712fdc7

aka: 1.10.0-SNAPSHOT.476

Please speak up and discuss. We'll then start taking considerations for
additional changes for 1.1.0 after we get the branch and pipeline in place.

-Dick




On Mon, Jul 29, 2019 at 4:08 PM Alexander Murmann 
wrote:

> Thanks for calling this out Ernie!
>
> It might be a good idea to cut the release and at the same time keep
> looking for urgent issues that need to be resolved and merged. Once the
> branch is cut, we release likelihood of new issues being introduced.
>
> Does anyone know of any other issues, we'd want to make sure get addressed
> before we ship?
>
> On Mon, Jul 29, 2019 at 3:36 PM Ernest Burghardt 
> wrote:
>
> > There is a PR #3844  up to
> > address GEODE-7012  I
> > think this should be in the next release...
> >
> > EB
> >
> > On Fri, Jul 26, 2019 at 4:07 PM Alexander Murmann 
> > wrote:
> >
> > > *Cutting the release*
> > > Do we have any volunteers to take over the release manager role?
> > >
> > > *Re: Udo's concerns*
> > > While I believe that iterations of this particular work have been
> > discussed
> > > on the mailing list as far back as March 2018, I do think that we
> should
> > > take Udo's response as an indicator that something with our larger
> > proposal
> > > process needs to be improved. We used to have synchronous Geode club
> > house
> > > sessions. For future discussions and for proposals in particular, I
> think
> > > it would be great to supplement our asynchronous mailing list
> > communication
> > > with a synchronous video chat discussions by the community.
> > >
> > > On Fri, Jul 26, 2019 at 4:02 PM Dan Smith  wrote:
> > >
> > > > +1 for cutting a 1.10.0 release branch.
> > > >
> > > >
> > > >
> > > > On Fri, Jul 26, 2019 at 3:55 PM Nabarun Nag  wrote:
> > > >
> > > > > Hi,
> > > > > I believe the original authors of the feature has done their due
> > > > diligence
> > > > > and followed all steps, we can get this feature in under the
> > > Experimental
> > > > > flag and let the community improve on it, if there is anything else
> > > that
> > > > > needs to be done.
> > > > >
> > > > > We have done this before for Lucene re-index feature, where we
> > involved
> > > > the
> > > > > entire community in its development, phase by phase. The wiki is up
> > and
> > > > > running, if someone has any concerns can raise it as a JIRA or
> > comment
> > > in
> > > > > the wiki and the community as a whole can decide if it is a valid
> > > > > concern or not and act upon it.
> > > > >
> > > > > Regards
> > > > > Nabarun Nag
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Jul 26, 2019 at 3:40 PM Udo Kohlmeyer 
> > wrote:
> > > > >
> > > > > > @Alexander + @Jared,
> > > > > >
> > > > > > So maybe that was my misunderstanding on the RFC (not being
> > optional
> > > on
> > > > > > new feature work). Given that this is a new feature, there is
> > > > > > significant risk to getting it "wrong".
> > > > > >
> > > > > > I was expecting more discussion around this. I have some
> objections
> > > to
> > > > > > the current approach/design. Given that my day job does not allow
> > me
> > > to
> > > > > > respond in a timely manner, I would have not been able to get all
> > my
> > > > > > concerns raised. In addition, throwing something onto the wiki,
> and
> > > > then
> > > > > > a few weeks before we'd like to cut a version raising a
> discussion
> > > > > > thread on work that has been going on for months already does not
> > > help
> > > > > > with the community being able to read, digest, think, reason and
> > > > respond
> > > > > > BEFORE it is released.
> > > > > >
> > > > > > I know `@Experimental` is non-binding on API's or usage, BUT I
> > prefer
> > > > > > some of the ground work to have been discussed, API's validated
> > > BEFORE
> > > > > > it is released into the wild. I mean this is a PUBLIC API, so
> we'd
> > > > > > prefer to get it more correct than the previous one.
> > > > > >
> > > > > > Maybe it is just me, taking it too serious... Where I prefer not
> > > > release
> > > > > > something as close to 95% correct (and discussed).
> > > > > >
> > > > > > Anyway.. If we want to cut 1.10... and we should... Let's do so..
> > but
> > > > > > I'd prefer that more on the correctness on the approach.
> > > > > >
> > > > > > --Udo
> > > > > >
> > > > > > On 7/25/19 11:08 AM, Alexander Murmann wrote:
> > > > > > >> I don't believe we should be including anything into the Geode
> > > > release
> > > > > > >> that has not gone through the correct process of feature
> > proposal.
> > > > > > >>
> > > > > > >> All work under the experimental cluster management service has
> > not
> > > > yet
> > > > > > >> been approved by the agreed upon RFC 

Re: [VOTE] Apache Geode 1.9.0 RC4

[Dick Cavender]

+1 Compiled source, reviewed distribution and NOTICE

On Wed, Apr 24, 2019 at 8:36 AM Ryan McMahon  wrote:

> +1 Verified signatures, compiled from source, and ran all examples.
>
> Ryan
>
> On Tue, Apr 23, 2019 at 3:44 PM Owen Nichols  wrote:
>
> > +1
> >
> > I used gpg --verify to check all signatures, compiled geode from source,
> > ran all examples, and set up a cluster with 2 locators, 3 servers, a
> simple
> > client and SSL enabled.
> >
> > -Owen
> >
> >
> > > On Apr 23, 2019, at 1:32 PM, Dan Smith  wrote:
> > >
> > > +1
> > >
> > > Looks good to me. I ran the geode-release-check against the repo.
> > >
> > > -Dan
> > >
> > > On Fri, Apr 19, 2019 at 5:00 PM Owen Nichols  > > wrote:
> > >
> > >> Hello, Geode dev community,
> > >>
> > >>
> > >> This is the fourth release candidate for Apache Geode, version 1.9.0.
> > >>
> > >> Thanks to all the community members for their contributions to this
> > >> release!
> > >>
> > >>
> > >> Please do a review and give your feedback. The deadline is before 3 PM
> > PST
> > >> Wed April 24th, 2019.
> > >>
> > >>
> > >> 1.9.0 resolves 296 issues on Apache Geode JIRA system. Release notes
> > >> can be found at:
> > >>
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.9.0
> > >> <
> > >>
> >
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.9.0
> > <
> >
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.9.0
> > >
> > >>>
> > >>
> > >>
> > >> Please note that we are voting upon the source tags: rel/v1.9.0.RC4
> > >>
> > >>
> > >> Apache Geode:
> > >>
> > >> https://github.com/apache/geode/tree/rel/v1.9.0.RC4 <
> > https://github.com/apache/geode/tree/rel/v1.9.0.RC4> <
> > >> https://github.com/apache/geode/tree/rel/v1.9.0.RC4 <
> > https://github.com/apache/geode/tree/rel/v1.9.0.RC4>>
> > >>
> > >> Apache Geode examples:
> > >>
> > >> https://github.com/apache/geode-examples/tree/rel/v1.9.0.RC4 <
> > https://github.com/apache/geode-examples/tree/rel/v1.9.0.RC4> <
> > >> https://github.com/apache/geode-examples/tree/rel/v1.9.0.RC4 <
> > https://github.com/apache/geode-examples/tree/rel/v1.9.0.RC4>>
> > >>
> > >> Apache Geode Native:
> > >>
> > >> https://github.com/apache/geode-native/tree/rel/v1.9.0.RC4 <
> > https://github.com/apache/geode-native/tree/rel/v1.9.0.RC4> <
> > >> https://github.com/apache/geode-native/tree/rel/v1.9.0.RC4 <
> > https://github.com/apache/geode-native/tree/rel/v1.9.0.RC4>>
> > >>
> > >>
> > >> Commit ID:
> > >>
> > >> Apache Geode: c0a73d1cb84986d432003bd12e70175520e63597
> > >>
> > >> Apache Geode Examples: b58b2720e9cb1fae9e2cbca7053bc9c748dab79d
> > >>
> > >> Apache Geode Native: add53da376c3044feb2fb22dc37a30989c271f19
> > >>
> > >>
> > >> Source and binary files:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/geode/1.9.0.RC4 <
> > https://dist.apache.org/repos/dist/dev/geode/1.9.0.RC4> <
> > >> https://dist.apache.org/repos/dist/dev/geode/1.9.0.RC4 <
> > https://dist.apache.org/repos/dist/dev/geode/1.9.0.RC4>>
> > >>
> > >> Maven staging repo:
> > >>
> > >>
> https://repository.apache.org/content/repositories/orgapachegeode-1054
> > 
> <
> > >>
> https://repository.apache.org/content/repositories/orgapachegeode-1054
> >  >>
> > >>
> > >> Geode's KEYS file containing PGP keys we use to sign the release:
> > >>
> > >> https://github.com/apache/geode/blob/develop/KEYS <
> > https://github.com/apache/geode/blob/develop/KEYS> <
> > >> https://github.com/apache/geode/blob/develop/KEYS <
> > https://github.com/apache/geode/blob/develop/KEYS>>
> > >>
> > >>
> > >> Signed the release with GPG fingerprint:
> > >>
> > >> DB5476815A475574577D442B468A4800EAFB2498
> > >>
> > >> PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=
> > >> https://dist.apache.org/repos/dist/dev/geode/1.9.0.RC4 <
> > https://dist.apache.org/repos/dist/dev/geode/1.9.0.RC4> <
> > >> https://dist.apache.org/repos/dist/dev/geode/1.9.0.RC4 <
> > https://dist.apache.org/repos/dist/dev/geode/1.9.0.RC4>>
> > >> -PgeodeRepositoryUrl=
> > >>
> https://repository.apache.org/content/repositories/orgapachegeode-1054
> > 
> <
> > >>
> https://repository.apache.org/content/repositories/orgapachegeode-1054
> >  >>
> > >> build
> > >> runAll
> > >>
> > >>
> > >> Regards,
> > >> - Owen & Dan
> >
> >
>

Re: [DISCUSS] Proposal to re-cut Geode 1.9.0 release branch

[Dick Cavender]

+1 to re-cutting the 1.9 release branch off a more stable develop sha
within the last couple days.

On Tue, Mar 19, 2019 at 1:14 PM Bruce Schuchardt 
wrote:

> If we recut the release branch we need to update JIRA tickets marked
> fixed in 1.10
>
> On 3/19/19 12:48 PM, Sai Boorlagadda wrote:
> > > It was known at the time that develop was not as stable as desired,
> > so we planned to cherry-pick fixes from develop until the release
> > branch was stable enough to ship.
> > I want to clarify that we decided to cut the release branch not that
> > develop was not stable. But really that it is desirable to cut the
> > branch sooner to avoid any regression risk that can be introduced by
> > on-going work on develop.
> >
> > Nevertheless looks like develop is more stable than release branch due
> > to some test fixes that were not cherry-picked into the release branch.
> > I think its a good idea to re-cut the branch as our current position
> > to stabilize release branch before releasing.
> >
> > +1 to re-cut.
> >
> > Sai
> >
> > On Tue, Mar 19, 2019 at 12:19 PM Owen Nichols  > > wrote:
> >
> > The Geode 1.9.0 release branch was originally cut 4 weeks ago on
> > Feb 19.  It was known at the time that develop was not as stable
> > as desired, so we planned to cherry-pick fixes from develop until
> > the release branch was stable enough to ship.  While this is a
> > good strategy when starting from a fairly good baseline, it seems
> > in this case it has only added complexity without leading to
> > stability.
> >
> > Looking at the pipelines over the last week (see attached
> > metrics), it appears we have been far more successful at
> > stabilizing /develop/ than /release/1.9.0/. Rather than trying to
> > cherry-pick more and more fixes to the release branch, I propose
> > we RE-CUT the 1.9.0 release branch later this week in order to
> > start from a much more stable baseline.
> >
> > -Owen
> >
> >
> >
>

Re: [VOTE] Apache Geode release - 1.4.0 RC2

[Dick Cavender]

+1

- Download src and binary dists
- Confirmed all dists extract
- Confirmed src builds
- Confirmed version and gfsh commands
- Reviewed LICENSE and NOTICE contents
- Reviewed maven distribution but didn't consume

-Dick


On Mon, Jan 29, 2018 at 4:08 PM, Swapnil Bawaskar 
wrote:

> After fixing the security concerns in the first release candidate, this is
> the second release candidate for Apache Geode, version 1.4.0.
> Thanks to all the community members for their contributions to this
> release!
>
> *** Please download, test and vote by Thursday, Feb 1, 1400 hrs
> US Pacific. ***
>
> It fixes 277 issues. release notes can be found at:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318420=12341842
>
> Note that we are voting upon the source tags: rel/v1.4.0.RC2
> https://github.com/apache/geode/tree/rel/v1.4.0.RC2
> https://github.com/apache/geode-examples/tree/rel/v1.4.0.RC2
>
> Commit ID:
> 2a70679608120042fa7cbee67f4dd21a085d9588 (geode)
> ced35f88173b04ac8e104b9cae10cc38289675fa (geode-examples)
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/geode/1.4.0.RC2
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachegeode-1037
>
>
> Geode's KEYS file containing PGP keys we use to sign the release:
> https://github.com/apache/geode/blob/develop/KEYS
>
> Release Signed with Key: pub 4096R/18F902DB 2016-04-07
> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
>

Re: Concourse ci access

[Dick Cavender]

For the geode pipeline you should be able to use your github creds instead
of the regular login. See if those work for you.

-Dick


On Sun, Jan 14, 2018 at 12:59 AM, Swapnil Bawaskar 
wrote:

> Hi,
> Can I please get access to concourse so as to kick off builds?
>
> Thanks!
>