ght need to work on
> the testing approach.
>
> BR/
> Mario.
>
> From: Jacob Barrett
> Sent: Monday, February 1, 2021 4:34 PM
> To: dev@geode.apache.org
> Subject: Re: [Proposal] Geode Native Library Versioning
>
>
> On Jan 29, 2021, at
of virtual methods we might need to work on the testing
approach.
BR/
Mario.
From: Jacob Barrett
Sent: Monday, February 1, 2021 4:34 PM
To: dev@geode.apache.org
Subject: Re: [Proposal] Geode Native Library Versioning
On Jan 29, 2021, at 3:47 PM, Dan Smith
m
On Jan 29, 2021, at 3:47 PM, Dan Smith
mailto:dasm...@vmware.com>> wrote:
I do think at least implementing some automated checking for whatever
compatibility we intend to provide is a good idea.
I have a branch with a test using Abigail [1]. This branch depends on merging
of a CI branch. It w
From: Jacob Barrett
Sent: Friday, January 29, 2021 12:00 PM
To: dev@geode.apache.org
Subject: Re: [Proposal] Geode Native Library Versioning
** sorry for the trashed formatting originally **
I would appreciate some feedback on this proposal by the end of day Friday,
February 5th, 2021.
TLDR
** sorry for the trashed formatting originally **
I would appreciate some feedback on this proposal by the end of day Friday,
February 5th, 2021.
TLDR; The proposal is to formalize what has been effectively the status quo for
Geode Native release in the current source form and any future binar
I would appreciate some feedback on this proposal by the end of day Friday,
February 5th, 2021.
TLDR; The proposal is to formalize what has been effectively the status quo for
Geode Native release in the current source form and any future binary form.
The Problem
Geode Native, specifically th
