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

2022-01-19 Thread Kirk Lund
+1 same as Naba On Wed, Jan 19, 2022 at 4:26 PM Nabarun Nag wrote: > +1 based on the results of the pipeline tests. > > Regards > Nabarun Nag > > > From: Dick Cavender > Sent: Monday, January 17, 2022 11:20 AM > To: dev@geode.apache.org > Subject: [Suspected Sp

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

2022-01-19 Thread Nabarun Nag
+1 based on the results of the pipeline tests. Regards Nabarun Nag From: Dick Cavender Sent: Monday, January 17, 2022 11:20 AM To: dev@geode.apache.org Subject: [Suspected Spam] [VOTE] Apache Geode 1.13.7.RC1 Hello Geode Dev Community, This is a release candid

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

2022-01-19 Thread Donal Evans
+1 Tested that performance across a variety of workloads is on par with previous released versions and no performance degradations have been introduced. From: Dick Cavender Sent: Monday, January 17, 2022 11:20 AM To: dev@geode.apache.org Subject: [Suspected Spam

Re: Changes to Public API Return Only Interfaces

2022-01-19 Thread Dan Smith
> When a public API interfaces has no use case where 3rd parties would > implement, such as return types or factory allocated implementations, there > should not be a compile time breaking change. In the case of IndexStatistics > there is no use case where a 3rd party could implement and provide

Changes to Public API Return Only Interfaces

2022-01-19 Thread Jacob Barrett
Devs, First off, this is a very forward looking discussion around something that will affect upcoming major releases when deprecating public APIs. One of the issues I am finding when investigating a few deprecated APIs for removal is that the deprecation hasn’t cascaded through to all the depen