Re: [Suspected Spam] [VOTE] Apache Geode 1.13.2.RC1

2021-03-11 Thread Dave Barnes 
+1 docs:
- Binary distribution contains javadocs with correctly-versioned header
(1.13.2).
- Source distribution contains user guide sources that build successfully
and are correctly versioned.
(did not test geode-native source)


On Thu, Mar 11, 2021 at 1:45 PM Donal Evans  wrote:

> +1
>
> Confirmed that performance across a broad range of workloads is comparable
> to that seen in the 1.13.1 release.
> 
> From: Dick Cavender 
> Sent: Thursday, March 11, 2021 1:34 PM
> To: dev@geode.apache.org 
> Subject: [Suspected Spam] [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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=H4bTz4M8EmkGGrFm7iy8zNaOxqnACXDrZ2h2ho3X46g%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=WXM3CGWfFZ4JJsIgGSZandkMpPFncY33mD4ELJyU7qc%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=vos%2B8SWMXWp4xHbLDKVTJbxXj%2Bobh89ET0oQhQzbOKY%3Dreserved=0
>
> Maven staging repo:
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1079data=04%7C01%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=a1DG6HNCXMskDmR1blZWcNZzsRKwgOP1zZCknYLysbA%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=bSf8cZY7Bkon%2BB2navQDAG1vh0OqcpbBgI4Gm8%2BSDUk%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675481174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=TSN%2FzxIfiCLq%2BzaWLYLgKJFeisywDMasb8PJZEUUJdM%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675481174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=tq%2BeYgMptmxM%2FZ4BMznA2dxqcARrLimcGAhFJmayQ1Q%3Dreserved=0
>
>

Re: [Suspected Spam] [VOTE] Apache Geode 1.13.2.RC1

2021-03-11 Thread Donal Evans 
+1

Confirmed that performance across a broad range of workloads is comparable to 
that seen in the 1.13.1 release.

From: Dick Cavender 
Sent: Thursday, March 11, 2021 1:34 PM
To: dev@geode.apache.org 
Subject: [Suspected Spam] [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 

 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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=WXM3CGWfFZ4JJsIgGSZandkMpPFncY33mD4ELJyU7qc%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=vos%2B8SWMXWp4xHbLDKVTJbxXj%2Bobh89ET0oQhQzbOKY%3Dreserved=0

Maven staging repo:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1079data=04%7C01%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=a1DG6HNCXMskDmR1blZWcNZzsRKwgOP1zZCknYLysbA%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675471182%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=bSf8cZY7Bkon%2BB2navQDAG1vh0OqcpbBgI4Gm8%2BSDUk%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675481174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=TSN%2FzxIfiCLq%2BzaWLYLgKJFeisywDMasb8PJZEUUJdM%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675481174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=tq%2BeYgMptmxM%2FZ4BMznA2dxqcARrLimcGAhFJmayQ1Q%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%7Cdoevans%40vmware.com%7C76efe2fb3abb4b07c72a08d8e4d571d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510952675481174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=VVWobTd7COd%2Bz7bVRL8UTwBqwb4XwXcHSisPwj0xSgY%3Dreserved=0

Pipelines:

[VOTE] Apache Geode 1.13.2.RC1

2021-03-11 Thread 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 

 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: [Proposal] Backport GEODE-9016 to 1.14, 1.13 and 1.12

2021-03-11 Thread Owen Nichols 
Sounds good, added to blocker board.

On 3/11/21, 12:02 PM, "Nabarun Nag"  wrote:

 +1

Get Outlook for 
iOS

From: Anilkumar Gingade 
Sent: Thursday, March 11, 2021 11:59:17 AM
To: dev@geode.apache.org 
Subject: Re: [Proposal] Backport GEODE-9016 to 1.14, 1.13 and 1.12

+1 to backport.

On 3/11/21, 11:38 AM, "Jianxia Chen"  wrote:

Hi,

I would like to backport the fix of GEODE-9016 to Geode 1.14, 1.13 and 
1.12
branches. This would help resolve the NPE for certain cases of PutAll 
with
CQ.

Thanks,
Jianxia

Re: [Proposal] Backport GEODE-9016 to 1.14, 1.13 and 1.12

2021-03-11 Thread Nabarun Nag 
 +1

Get Outlook for iOS

From: Anilkumar Gingade 
Sent: Thursday, March 11, 2021 11:59:17 AM
To: dev@geode.apache.org 
Subject: Re: [Proposal] Backport GEODE-9016 to 1.14, 1.13 and 1.12

+1 to backport.

On 3/11/21, 11:38 AM, "Jianxia Chen"  wrote:

Hi,

I would like to backport the fix of GEODE-9016 to Geode 1.14, 1.13 and 1.12
branches. This would help resolve the NPE for certain cases of PutAll with
CQ.

Thanks,
Jianxia

Re: [Proposal] Backport GEODE-9016 to 1.14, 1.13 and 1.12

2021-03-11 Thread Anilkumar Gingade 
+1 to backport. 

On 3/11/21, 11:38 AM, "Jianxia Chen"  wrote:

Hi,

I would like to backport the fix of GEODE-9016 to Geode 1.14, 1.13 and 1.12
branches. This would help resolve the NPE for certain cases of PutAll with
CQ.

Thanks,
Jianxia

[Proposal] Backport GEODE-9016 to 1.14, 1.13 and 1.12

2021-03-11 Thread Jianxia Chen 
Hi,

I would like to backport the fix of GEODE-9016 to Geode 1.14, 1.13 and 1.12
branches. This would help resolve the NPE for certain cases of PutAll with
CQ.

Thanks,
Jianxia

Re: [Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch

2021-03-11 Thread Owen Nichols 
Now is definitely the time to fix this.  Glad to have this added to blocker 
board.

On 3/11/21, 11:09 AM, "Jens Deppe"  wrote:

+1

On 3/11/21, 10:49 AM, "Nabarun Nag"  wrote:

Hi everyone,

Putting forward the proposal to backport GEODE-9091 (Serialization 
Improvements) to support/1.14 branch,

What does GEODE-9091 do?

  *   It adds serialVersionUID to the Serializable classes in 
geode-redis module
  *   It converts all DataSerializable classes to 
DataSerializableFixedID classes

Why do we need to backport these changes?

  *   These changes future-proofs the geode-redis data structures from 
being used in mixed version clusters.
  *   This will ensure that changes to serializable classes do not 
break backward compatibility.
  *   If these classes get changed in the future, the serialVersionUIDs 
will remain the same and can be used with older and newer versions.
  *   If we don't backport these changes to 1.14.0 then future releases 
of geode-redis will not be compatible with it.

Reference 
PR:[link]


Regards
Nabarun Nag

Re: [Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch

2021-03-11 Thread Jens Deppe 
+1

On 3/11/21, 10:49 AM, "Nabarun Nag"  wrote:

Hi everyone,

Putting forward the proposal to backport GEODE-9091 (Serialization 
Improvements) to support/1.14 branch,

What does GEODE-9091 do?

  *   It adds serialVersionUID to the Serializable classes in geode-redis 
module
  *   It converts all DataSerializable classes to DataSerializableFixedID 
classes

Why do we need to backport these changes?

  *   These changes future-proofs the geode-redis data structures from 
being used in mixed version clusters.
  *   This will ensure that changes to serializable classes do not break 
backward compatibility.
  *   If these classes get changed in the future, the serialVersionUIDs 
will remain the same and can be used with older and newer versions.
  *   If we don't backport these changes to 1.14.0 then future releases of 
geode-redis will not be compatible with it.

Reference 
PR:[link]


Regards
Nabarun Nag

Re: [Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch

2021-03-11 Thread Sarah Abbey 
+1

From: Nabarun Nag 
Sent: Thursday, March 11, 2021 1:48 PM
To: dev@geode.apache.org 
Subject: [Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch

Hi everyone,

Putting forward the proposal to backport GEODE-9091 (Serialization 
Improvements) to support/1.14 branch,

What does GEODE-9091 do?

  *   It adds serialVersionUID to the Serializable classes in geode-redis module
  *   It converts all DataSerializable classes to DataSerializableFixedID 
classes

Why do we need to backport these changes?

  *   These changes future-proofs the geode-redis data structures from being 
used in mixed version clusters.
  *   This will ensure that changes to serializable classes do not break 
backward compatibility.
  *   If these classes get changed in the future, the serialVersionUIDs will 
remain the same and can be used with older and newer versions.
  *   If we don't backport these changes to 1.14.0 then future releases of 
geode-redis will not be compatible with it.

Reference 
PR:[link]


Regards
Nabarun Nag

[Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch

2021-03-11 Thread Nabarun Nag 
Hi everyone,

Putting forward the proposal to backport GEODE-9091 (Serialization 
Improvements) to support/1.14 branch,

What does GEODE-9091 do?

  *   It adds serialVersionUID to the Serializable classes in geode-redis module
  *   It converts all DataSerializable classes to DataSerializableFixedID 
classes

Why do we need to backport these changes?

  *   These changes future-proofs the geode-redis data structures from being 
used in mixed version clusters.
  *   This will ensure that changes to serializable classes do not break 
backward compatibility.
  *   If these classes get changed in the future, the serialVersionUIDs will 
remain the same and can be used with older and newer versions.
  *   If we don't backport these changes to 1.14.0 then future releases of 
geode-redis will not be compatible with it.

Reference PR:[link]


Regards
Nabarun Nag