Re: [PROPOSAL] Postpone Geode 1.14

+1 On 7/29/20, 1:35 PM, "Mark Bretl" wrote: +1 Should we need to drop a line to user@geode or is communicating on this list enough once decided? --Mark On Wed, Jul 29, 2020 at 7:05 AM Joris Melchior wrote: > +1 > > On 2020-07-28, 7:34 PM, "Alexander

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

+1 --Mark On Thu, Jul 30, 2020 at 1:30 PM Robert Houghton wrote: > Highwater isn't used by benchmarks? > > On Jul 30, 2020 12:02, Dave Barnes wrote: > +1 > > On Thu, Jul 30, 2020 at 8:45 AM Owen Nichols wrote: > > > Hi Donal, I can confirm that develop/highwater hasn't been updated in a > >

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

Highwater isn't used by benchmarks? On Jul 30, 2020 12:02, Dave Barnes wrote: +1 On Thu, Jul 30, 2020 at 8:45 AM Owen Nichols wrote: > Hi Donal, I can confirm that develop/highwater hasn't been updated in a > year and is no longer in use by any pipelines (all pipelines use the last > release

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

+1 On Thu, Jul 30, 2020 at 8:45 AM Owen Nichols wrote: > Hi Donal, I can confirm that develop/highwater hasn't been updated in a > year and is no longer in use by any pipelines (all pipelines use the last > release tag as the benchmark baseline now). > > On 7/30/20, 5:48 AM, "Donal Evans"

Re: [PROPOSAL] Postpone Geode 1.14

+1 From: Alexander Murmann Sent: Tuesday, July 28, 2020 4:34 PM To: dev@geode.apache.org Subject: [PROPOSAL] Postpone Geode 1.14 Hi all, As mentioned on the previous discuss thread, I propose to hold off cutting 1.14 until we have shipped 1.13. Once we have

Re: [PROPOSAL] Postpone Geode 1.14

Mark, that's a great point! I'll give everyone till tomorrow to contribute their opinion on this thread and then inform the user list. Thanks! On Wed, Jul 29, 2020 at 1:35 PM Mark Bretl wrote: > +1 > > Should we need to drop a line to user@geode or is communicating on this > list enough once

Re: Review needed for c++ client ticket

The PR needs tests. > On Jul 30, 2020, at 7:38 AM, Blake Bender wrote: > > Hi Alberto, > > I've reached out to Jake to approve his review, then I'll merge this for you. > Sorry for the delay. > > Thanks, > > Blake > > > On 7/23/20, 3:08 AM, "Alberto Bustamante Reyes" > wrote: > >

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

Hi Donal, I can confirm that develop/highwater hasn't been updated in a year and is no longer in use by any pipelines (all pipelines use the last release tag as the benchmark baseline now). On 7/30/20, 5:48 AM, "Donal Evans" wrote: I may be mistaken, but I think the develop/highwater tag

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

FWIW, Geode Native works around this by not keeping a separate examples repo at all. To build our examples, you *must* build your own Geode Native "installation," which includes the examples tree, or download the desired tarball/zip file from our GitHub releases. I’m pretty much agnostic as

Re: Review needed for c++ client ticket

Hi Alberto, I've reached out to Jake to approve his review, then I'll merge this for you. Sorry for the delay. Thanks, Blake On 7/23/20, 3:08 AM, "Alberto Bustamante Reyes" wrote: Hi, Could someone please take a look at this c++ client PR?

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

I may be mistaken, but I think the develop/highwater tag was used by the geode-benchmarks project. Can we get confirmation that it's no longer in use? +1 conditional on that Get Outlook for Android From: Ju@N Sent: Thursday, July 30,

Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

+1 On Thu 30 Jul 2020 at 08:21, Owen Nichols wrote: > Tags in the rel/ namespace should be created by the Geode release manager > as part of an official Geode release only, yet we seem to have some extra > ones somehow. > Further, I don't see any value in keeping RC tags forever long after the

[PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

Tags in the rel/ namespace should be created by the Geode release manager as part of an official Geode release only, yet we seem to have some extra ones somehow. Further, I don't see any value in keeping RC tags forever long after the release is final. Please vote +1 in favor of trimming the