Re: [DISCUSS] - Move gfsh into its own submodule

+1 On Fri, Nov 22, 2019 at 9:17 AM Kirk Lund wrote: > +1 yes! > > On Fri, Nov 22, 2019 at 9:15 AM Donal Evans wrote: > > > +1 > > > > Especially with the new management functionality on the way, this seems > > like a good idea. > > > > On Fri, Nov 22, 2019 at 8:45 AM Jinmei Liao wrote: > > >

Re: Request for addition to 1.11 RC: GEODE-7454: Docs for Cluster Management Service

. (The corresponding change has already been incorporated on the 'develop' branch.) On Tue, Dec 3, 2019 at 2:49 PM Mark Hanson wrote: > Done. > > > On Dec 3, 2019, at 9:24 AM, Dave Barnes wrote: > > > > Docs for a feature that's already implemented - no code changes.

Request for addition to 1.11 RC: GEODE-7454: Docs for Cluster Management Service

Docs for a feature that's already implemented - no code changes. Can be cherry-picked from the develop branch as-is with no modifications. https://github.com/apache/geode/commit/e48f34048c574440ed7e0640f42e9c82d789becb

Re: [VOLUNTEER] I am volunteering to handle the 1.11 Apache Geode release.

Mark - I'll help out with docs -- updating the website, etc. On Mon, Oct 28, 2019 at 2:00 PM Mark Hanson wrote: > Hi All, > > Since we need a release manager for 1.11 and no one has volunteered, yet. > I thought I would volunteer. > > Thanks, > Mark

Re: [VOTE] Apache Geode 1.9.2.RC1

+1 Downloaded, successfully built Geode and Geode-Native docs form source. On Tue, Oct 22, 2019 at 2:17 AM Ju@N wrote: > +1, > > Downloaded and built from source, created two clusters with multiple > members and verified WAN replication (along with some gateway related > commands) work

Re: [DISCUSS]: Commit Message Format too Short?

The Template Checklist is a great reference for the committer who builds and submits the PR, but I find it of little value as a posted comment for reviewers of the PR - just takes up a lot of space. As a frequent reviewer, I like to see: - A clear and concise title beginning with the ticket number

Re: [DISCUSS] RFC: Shipping Geode patch releases

The proposal mentions "semi-permanent community release managers". Assuming that a patch release is simpler than a full release, these patch releases might serve well as training opportunities for first-time release managers. +1 if that's the case. On Tue, Feb 25, 2020 at 9:29 AM Anthony Baker

Re: enable-time-statistics

Sounds like the caveat could be dropped from the user guide. If we have consensus on that (am I understanding correctly?), I'll initiate a JIRA ticket. On Fri, Jan 10, 2020 at 1:47 PM Jacob Barrett wrote: > The biggest impact was in recording all the additional stats in the old > blocking stats

Re: disable statistic archival

I'm getting the impression that the user guide could be clearer with regard to the interactions between - enable-statistics - statistic-sampling-enabled - statistic-archive-file On Wed, Jan 22, 2020 at 9:30 AM Kirk Lund wrote: > Try setting STATISTIC_SAMPLING_ENABLED to false to

Request for Confluence edit permissions

This is a request for permission to edit the Apache Geode Wiki on Confluence using my Apache credentials: Username: dbarnes Email: dbar...@apache.com I've been using another login to access confluence, but I'd like to be able to do it with my Apache identity. Thanks, Dave Barnes (committer

Request for Docker Hub permissions

Please grant me permission to upload Apache Geode artifats to Docker hub using my ID: dbarnes97. Thanks!

Re: [VOTE] Apache Geode 1.11.0.RC4

+1 Checked geode-native - Windows build succeeded - docs builds succeeded On Thu, Dec 26, 2019 at 2:00 PM Anthony Baker wrote: > +1 > > Checked: > > - Signatures are good > - SHA’s are good > - geode, geode-native builds from source > - reviewed dependency changes > > Fix for next release:

Re: [DISCUSS] abandon branch protection rules

@Jacob Barrett @Robert Houghton I have an interest in expediting docs-only PRs and would be interested in participating in a break-out discussion (or at least reviewing the conclusions). On Mon, Dec 30, 2019 at 9:15 AM Robert Houghton wrote: > @Jacob Barrett I have some ideas on this. Want

Re: Website refresh (was Re: [DISCUSS] Adding Google Analytics to our website)

@alberto A great idea - others feel the same: https://issues.apache.org/jira/browse/GEODE-2942 On 4/9/20, 2:31 AM, "Alberto Bustamante Reyes" wrote: It would be great if the new webpage could include a search button for the user guide. BR/ Alberto B.

Re: Reconfiguring our notifications and more

+1 On 4/21/20, 9:09 AM, "Joris Melchior" wrote: +1 From: Anthony Baker Sent: April 21, 2020 11:54 AM To: dev@geode.apache.org Subject: Reconfiguring our notifications and more I’d like a quick round of feedback so we can stop the

Re: [VOTE] Apache Geode 1.12.0.RC4

+1 Successfully built User Guide with the provided Docker-based toolset. Successfully built javadocs. On Fri, Mar 27, 2020 at 2:56 PM Dan Smith wrote: > +1 > > Ran my release check > https://github.com/upthewaterspout/geode-release-check > > -Dan > > On Fri, Mar 27, 2020 at 1:33 PM John Blum

Re: Switching default branch in .net core repo

+1 Dave On 4/23/20, 8:29 AM, "Karen Miller" wrote: +1 Karen On Thu, Apr 23, 2020 at 8:14 AM Dan Smith wrote: > +1 > > -Dan > > On Thu, Apr 23, 2020, 8:05 AM Anthony Baker wrote: > > > Please do, this will match our default approach to development

[ANNOUNCE] Geode 1.13 support branch coming soon

The project's time-based schedule targets the first Monday after May 1 for cutting the support branch. So, we're planning to cut the Geode 1.13 support branch on Monday, May 4, 2020. Only critical fixes will be allowed once the support branch has been created, so do what you can to make the

Docker Hub access request

This is a request for access to upload Apache Geode artifacts to Docker Hub. My Docker Hub ID is 'dbarnes97'. Thanks, Dave Barnes dbar...@apache.org

Request for Apache Geode release management permissions

This is a request for bulk modification permissions and admin permissions on the Geode project. Thanks, Dave Barnes dbar...@apache.org <mailto:dbar...@apache.org>

Request for Concourse permissions

This is a request for permissions to log in and create pipelines for Apache Geode (https://concourse.apachegeode-ci.info/ <https://concourse.apachegeode-ci.info/>). Thanks, Dave Barnes dbar...@apache.com <mailto:dbar...@apache.com> Github acct ID: davebarnes97

Geode support/1.13 created

We have created a new support branch for Apache Geode 1.13.0 - support/1.13. We hope to make a final release in about a month. Please focus your acceptance testing on this branch and raise any concerns in the next few weeks. After some quiet period, we will package a release candidate and present

[DISCUSS] Geode 1.13 support branch planning

to the community on this [DISCUSS] thread. Thanks, Dave Barnes Geode 1.13 Release Manager

Re: [DISCUSS] preparing for Geode 1.13.0 release

I'm willing. On 4/22/20, 11:43 AM, "Owen Nichols" wrote: Geode is scheduled to cut support/1.13 on May 4, as per the quarterly release schedule approved [1] in 2018 and affirmed in last month’s “Shipping patch releases” RFC [2]. Please volunteer if you are interested in serving as

Re: [PROPOSAL] bring GEODE-8091 to support branches

..and 1.12. On Mon, May 11, 2020 at 6:09 PM Dave Barnes wrote: > OK, Jinmei. Three of those plus-ones is the magic minimum. > Please add your change to 1.13. > Dave > > > On Mon, May 11, 2020 at 4:20 PM Donal Evans wrote: > >> +1 >> >> On Mon, Ma

Re: [PROPOSAL] include GEODE-8073 in Geode 1.13 support branch

OK, Eric, looks like you have the 3 votes needed - go ahead and add the fix to support/1.13. Dave On Wed, May 6, 2020 at 11:43 AM Xiaojian Zhou wrote: > +1 > This bug reproduced again in today's regression. It's better to backport to > 1.13. > > On Wed, May 6, 2020 at 11:42 AM Jinmei Liao

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

+1 Go ahead, Jinmei, and cherry-pick the GEODE-8055 fix to the Geode support/1.13 branch. Dave Geode 1.13 release manager On Mon, May 4, 2020 at 10:12 PM Dick Cavender wrote: > +1 > > On Mon, May 4, 2020 at 8:28 PM Owen Nichols wrote: > > > Hi Jinmei, it looks like your commit came in just

Re: [PROPOSAL] Merge PR 5103 (GEODE-8083) to support/1.13

This is a squash of GEODE-8083 and 8087, to bring the Java API > comparison > > jobs from Gradle and Concourse to the support branch. Currently runs > > cleanly from my terminal, and has been green on develop for a week or so. > > > > @Dave Barnes , as release manager, what say you? > >

Re: [PROPOSAL] bring GEODE-8091 to support branches

OK, Jinmei. Three of those plus-ones is the magic minimum. Please add your change to 1.13. Dave On Mon, May 11, 2020 at 4:20 PM Donal Evans wrote: > +1 > > On Mon, May 11, 2020 at 4:11 PM Anilkumar Gingade > wrote: > > > +1 > > > > On Mon, May 11, 2020 at 4:10 PM Jinmei Liao wrote: > > > > >

Re: Discussion - Change Public API Before Initial Release

Plenty of votes, go ahead, Jake, and add this to the support/1.13 branch. On Mon, May 11, 2020 at 8:36 AM Joris Melchior wrote: > +1 > > From: Jacob Barrett > Sent: May 8, 2020 21:26 > To: dev@geode.apache.org > Subject: Discussion - Change Public API Before

Re: Proposal to bring GEODE-8016 to support branches

Looks good, Owen. Go ahead and add this to 1.13. On Mon, May 11, 2020 at 9:49 AM Robert Houghton wrote: > Yes please! +1 > > On Mon, May 11, 2020 at 2:46 AM Darrel Schneider > wrote: > > > +1 > > > > On Sun, May 10, 2020 at 10:05 PM Dick Cavender > > wrote: > > > > > +1 > > > > > > On Sat,

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

Go ahead, Patrick, and add this to 1.13. On Mon, May 11, 2020 at 8:36 AM Joris Melchior wrote: > +1 > > From: Patrick Johnson > Sent: May 8, 2020 17:40 > To: dev@geode.apache.org > Subject: Proposal to bring GEODE-8068 to support/1.13 > > I’d like to bring

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

Looks like you have the votes, Juan. Go ahead and contribute this fix to support/1.13 and support/1.12. Thanks, Dave Geode 1.13 release manager On Thu, May 7, 2020 at 10:44 AM Eric Shu wrote: > +1 > > > On Thu, May 7, 2020 at 10:22 AM Jianxia Chen wrote: > > > +1 > > > > On Thu, May 7, 2020 at

Apache Geode board report (DRAFT FOR YOUR REVIEW)

Please respond with changes & additions by COB Friday, May 8. See the "bragging points" at the bottom. Publish and Prevail, y'all! Thanks, Dave ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time,

Re: [PROPOSAL] Bring GEODE-8100 to support branches

+ 0.5 Good material! I'm in favor of incoporating this doc update in the 1.13 support branch, but would like an opportunity to edit for a few proof-readerish items that caught my eye. Will submit a PR today for your review, Jinmei. Thanks for your contribution! On 2020/05/20 14:09:05, Joris

Re: [PROPOSAL] bring GEODE-8131 PR to support branches

We have a quorum, Bruce, so go ahead and add this fix to 1.13 and other support branches, as appropriate. Thanks, Dave On 2020/05/19 15:53:28, Bruce Schuchardt wrote: > While investigating a distributed hang we discovered that the alerting system > was blocking the logging of critical

Re: [PROPOSAL] Bring GEODE-8100 to support branches

ion in the 1.13 release > > > On Wed, May 20, 2020 at 2:31 PM Dave Barnes wrote: > > > Edit completed, reviewed, and committed. > > > > +1 for including this in the 1.13 support branch. > > > > On 2020/05/20 16:54:09, Dave Barnes wrote: > > > + 0.5 >

Re: [PROPOSAL] Bring GEODE-8100 to support branches

Edit completed, reviewed, and committed. +1 for including this in the 1.13 support branch. On 2020/05/20 16:54:09, Dave Barnes wrote: > + 0.5 > Good material! I'm in favor of incoporating this doc update in the 1.13 > support branch, but would like an opportunity to edit for a few

Geode 1.13: What is the status of "experimental" features?

Three features are listed as “Experimental” in Geode 1.12. Has their status changed for 1.13? - Cluster Management Service: https://geode.apache.org/docs/guide/112/configuring/running/cluster-management-service.html

Re: [PROPOSAL]: GEODE-8150 into support/1.13

Please proceed with the proposed merge, Juan. Thanks, Dave On 2020/05/21 16:15:59, Udo Kohlmeyer wrote: > +1.. > On May 21, 2020, 8:12 AM -0700, Ju@N , wrote: > Hello devs, > > I'd like to propose bringing *GEODE-8150 [1] *to the *support/1.13* branch. > The ticket is basically to revert the

Re: Proposal to backport GEODE-8167

Please add this change to support/1.13, Owen. Thanks, Dave On 2020/05/21 16:19:49, Dick Cavender wrote: > +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

[DISCUSS] Someone to update 3rd-party libraries used by Geode

have time to shake out issues before the next release. Regards, Dave Barnes on behalf of the Apache Geode Team

[ANNOUNCE] Apache Geode 1.13.0

We would like to thank all the contributors that made the release possible. Regards, Dave Barnes on behalf of the Apache Geode team

Re: Geode 1.13 RC1 accepted

Good advice, Bruce. Thanks for the +1. On Thu, Sep 10, 2020 at 9:53 AM Bruce Schuchardt wrote: > I missed the vote but am okay with it. Maybe not start a 3-day vote on a > holiday next time? > > On 9/9/20, 3:49 PM, "Dave Barnes" wrote: > > It's past the an

[VOTE] Apache Geode 1.13.0.RC1

/geode/blob/develop/KEYS Command to run geode-examples: ./gradlew -PgeodeReleaseUrl= https://dist.apache.org/repos/dist/dev/geode/1.13.0.RC1 -PgeodeRepositoryUrl= https://repository.apache.org/content/repositories/orgapachegeode-1069 build runAll Regards Dave Barnes

Geode 1.13 RC1 accepted

It's past the announced deadline and we have closed the vote with a successful result. Voting status == +1 10 votes (*=PMC member, 'binding' vote) Aaron Lindsey Dave Barnes* Jens Deppe* Jinmei Liao* John Blum* Mike Martell Nabarun Nag* Owen Nichols Patrick Johnson Sarah Abbey

Re: [PROPOSAL] Backport GEODE-8475 to 1.13

Yes, Gester - thanks. > On Sep 2, 2020, at 3:04 PM, Owen Nichols wrote: > > +1, looking forward to getting this backported as soon as possible today! > > On 9/2/20, 2:34 PM, "Eric Shu" wrote: > >+1 > > >From: Dick Cavender >Sent: Wednesday,

Re: [PROPOSAL] port GEODE-8467 to support/1.13

+1 GEODE-8467 addresses one of the few remaining 1.13 release blockers. I see it's been approved and merged into the develop branch. Assuming that it's passed applicable testing, let's do it. On Tue, Sep 1, 2020 at 7:37 AM Bruce Schuchardt wrote: > I’d like to cherry-pick this change into

Re: [PROPOSAL] port GEODE-8467 to support/1.13

> Assuming that it's passed applicable testing AND GETS AT LEAST 3 VOTES, let's do it. On Tue, Sep 1, 2020 at 10:24 AM Dave Barnes wrote: > +1 > GEODE-8467 addresses one of the few remaining 1.13 release blockers. > I see it's been approved and merged into the develop bran

Re: Proposal to bring GEODE-8456 (shiro upgrade) to support branches

Looks like more than enough approvals, Owen. Please port, as you proposed. Thanks, Dave On Tue, Sep 1, 2020 at 7:45 AM Alexander Murmann wrote: > +1 > > On Tue, Sep 1, 2020 at 6:19 AM Sarah Abbey wrote: > > > +1 > > > > From: Ju@N > > Sent: Tuesday, September

Re: [PROPOSAL] port GEODE-8467 to support/1.13

upport/1.13 > > +1 > ________ > From: Dave Barnes > Sent: Tuesday, September 1, 2020 10:25 AM > To: dev@geode.apache.org > Subject: Re: [PROPOSAL] port GEODE-8467 to support/1.13 > > > Assuming that it's passed applicable testing AND GETS AT

Re: [VOTE] Apache Geode 1.13.0.RC1

in Jira is accurate, and checked that the RC1 tag shows > as "Verified" in github. > > On 9/7/20, 8:23 PM, "Dave Barnes" wrote: > > Hello Geode Dev Community, > > > This is a release candidate for Apache Geode version 1.13.0.RC1. > >

Re: [PROPOSAL] Remove "Fix Version/s" and "Sprint" from Jira "Create Issue" dialogue and include "Affects Version/s"

+1 esp addition of "Affects Version/s". On Mon, Aug 17, 2020 at 3:07 PM Kirk Lund wrote: > +1 if it's possible > > On Mon, Aug 17, 2020 at 12:04 PM Donal Evans wrote: > > > Looking at the dialogue that opens when you attempt to create a new > ticket > > in the GEODE Jira[1], there are two

Re: [PROPOSAL] Backport GEODE-8432 to 1.13

Thanks for your contribution, Gester On Thu, Aug 20, 2020 at 12:37 PM Joris Melchior wrote: > +1 > > On 2020-08-20, 12:08 PM, "Xiaojian Zhou" wrote: > > It's using region path instead of getting the region. It should be no > risk. > > On 8/19/20, 10:25 AM, "Xiaojian Zhou" wrote: > >

Re: Clean C++ client metadata in timeouts

> happens. If we've failed the handshake, it's very unlikely things will > correct themselves without outside intervention, so this fix is probably > goodness. I'd go ahead and submit a PR when you think it's solid. > > Thanks, > > Blake > > > On 9/17/20, 9:36 AM

Re: Clean C++ client metadata in timeouts

Alberto, Are there cases in which one or two timeouts are followed by a successful retry? Or does one timeout *always* end with more timeouts and, ultimately, an IO error? If timeouts can sometimes be followed by successful retries, and re-trying is the current default behavior, then I agree that

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

Thanks, Udo - Go ahead with your proposed back-port. Dave On Wed, May 27, 2020 at 6:50 AM Jinmei Liao wrote: > +1 > > 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

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

Udo, please remember to update the JIRA ticket - it needs to be closed and the fix-versions specified. Thanks, Dave On Wed, May 27, 2020 at 7:24 AM Dave Barnes wrote: > Thanks, Udo - Go ahead with your proposed back-port. > Dave > > On Wed, May 27, 2020 at 6:50 AM Jinmei Liao wr

Re: [PROPOASAL] backport GEODE-8144

I'm going to spend a release-manager +1 to put this proposal over the top. Please merge this fix into support/1.13, Bruce. Thanks, Dave On Thu, May 28, 2020 at 7:52 AM Udo Kohlmeyer wrote: > +1 > On May 27, 2020, 1:35 PM -0700, Bruce Schuchardt , > wrote: > This ticket has two PRs. One passed

Re: No more hardcoded region separators!

Excellent, Donal! If you have not already done so, please consider documenting the practice you're advocating in a place where all community contributors have a chance of seeing it. Maybe https://cwiki.apache.org/confluence/display/GEODE/How+to+Contribute? On Thu, May 28, 2020 at 9:46 AM Donal

Re: PR process and etiquette

Here's a common use case that we should address: A single PR may require two reviews, one for code and another for docs, before it can be said to be fully reviewed and ready to merge. Points to consider: - Many PRs, especially those introducing new features or user-settable properties,

Re: Proposal to backport GEODE-8395 (gfsh help banner) to support branches

+1 On Sun, Aug 2, 2020 at 7:07 AM Donal Evans wrote: > +1 > > Nice catch! > > Get Outlook for Android > > > From: Jinmei Liao > Sent: Saturday, August 1, 2020 11:09:45 PM > To: dev@geode.apache.org > Subject: Re: Proposal to backport

Re: Proposal to backport GEODE-8395 (gfsh help banner) to support branches

Hard to believe this problem was still hanging around. Definitely back-port, the sooner, the better. On Mon, Aug 3, 2020 at 7:56 AM Dave Barnes wrote: > +1 > > > On Sun, Aug 2, 2020 at 7:07 AM Donal Evans wrote: > >> +1 >> >> Nice catch! >> >>

Re: [PROPOSAL] backport GEODE-6564 to support/1.13

Go ahead and back-port, Darrel. Thanks for your contribution. On Mon, Aug 3, 2020 at 4:51 PM Alexander Murmann wrote: > +1 > > On Mon, Aug 3, 2020 at 4:47 PM Jianxia Chen wrote: > > > +1 > > > > On Mon, Aug 3, 2020 at 4:13 PM Darrel Schneider > wrote: > > > > > GEODE-6564 is a memory leak

Re: [PROPOSAL] backport GEODE-8394 to support/1.13

Plenty of approvals. Go ahead and port, Anil. Thanks! On Fri, Aug 7, 2020 at 11:08 AM Owen Nichols wrote: > +1 and please bring to support/1.12 as well > > On 8/7/20, 10:49 AM, "Jianxia Chen" wrote: > > +1 > > On Fri, Aug 7, 2020 at 10:35 AM Anilkumar Gingade > > wrote: > > >

Re: [PROPOSAL] Backport GEODE-8423 to support/1.13

+1 On Wed, Aug 12, 2020 at 9:10 AM Darrel Schneider wrote: > +1 > > From: Sarah Abbey > Sent: Wednesday, August 12, 2020 8:59 AM > To: dev@geode.apache.org > Subject: [PROPOSAL] Backport GEODE-8423 to support/1.13 > > The documentation for the Redis API for

Re: [PROPOSAL] Backport GEODE-8423 to support/1.13

OK, Sarah, you have the requisite 3 votes -- go ahead and back-port. Thanks for your contribution! -Dave On Wed, Aug 12, 2020 at 9:24 AM Dan Smith wrote: > +1 > > -Dan > > On Aug 12, 2020, at 8:59 AM, Sarah Abbey sab...@vmware.com>> wrote: > > get > >

[PROPOSAL] back-port GEODE-8388 native client doc fixes to support/1.13

GEODE-8388: Geode Native Client user guide: delete unused sources Housekeeping: The geode-native docs directory contains unused sources from the pre-open-source days. The problem is that while they're not linked to the user guide's T of C, these out-of-date docs are still included in the manual

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

Has the version on the develop branch completed a test cycle? On Wed, Aug 12, 2020 at 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.

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

proval for priority of it once > it does pass. (Maybe I am being a little over zealous). > > Thanks, > Mark > > On 8/12/20, 5:52 PM, "Dave Barnes" wrote: > > Has the version on the develop branch completed a test cycle? > > On Wed, Aug 12, 2020

Re: [PROPOSAL] merge GEODE-8259 to support branches

OK, Gester, please merge. Thanks, Dave On Wed, Jul 1, 2020 at 8:33 AM Bruce Schuchardt wrote: > +1 > I reviewed this PR and, as Gester said, it's low risk. If it fixes a > problem someone is having let's backport it. > > On 6/30/20, 3:51 PM, "Xiaojian Zhou" wrote: > > Customer

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

Hey, Bill, you got the votes. Go ahead with the back-ports. Thanks, Dave On Wed, Jul 1, 2020 at 10:54 AM Kirk Lund wrote: > +1 > > On Wed, Jul 1, 2020 at 9:59 AM Dick Cavender wrote: > > > +1 > > > > -Original Message- > > From: Bruce Schuchardt > > Sent: Wednesday, July 1, 2020 9:49

Re: [PROPOSAL] backport fix for GEODE-8020 to support/1.13

Thanks, Bruce. On Thu, Jul 9, 2020 at 10:32 AM Bruce Schuchardt wrote: > Since I had 3 +1’s I merged the change to support/1.13 > > From: Bruce Schuchardt > Date: Thursday, July 9, 2020 at 8:00 AM > To: "dev@geode.apache.org" > Subject: [PROPOSAL] backport fix for GEODE-8020 to support/1.13 >

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

Sounds like an improvement, Juan, and you’ve got the votes. Go ahead and back port. Thanks, Dave > On Jul 3, 2020, at 9:08 AM, Joris Melchior wrote: > > +1 > > On 2020-07-03, 9:06 AM, "Ju@N" > wrote: > >Hello devs, > >I'd like to propose bringing

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

+1 > On Jul 9, 2020, at 10:04 PM, Dick Cavender wrote: > > +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

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

Thanks for taking care of that, Owen. On Tue, Jun 30, 2020 at 9:38 AM Owen Nichols wrote: > Backported to support/1.13 and support/1.12 > > On 6/30/20, 9:37 AM, "Robert Houghton" wrote: > > +1 > > From: Dick Cavender > Date: Tuesday, June 30, 2020 at 9:14 AM > To:

Re: [PROPOSAL] merge GEODE-8259 to support branches

...and there it is! On Tue, Jun 30, 2020 at 4:10 PM Dave Barnes wrote: > Strange -- I received the two votes 9 minutes before I got the original > message. > I'm heading out for the day, so Gester, if you get that third vote, go > ahead and merge. > Cheers, > Dave > > O

Re: [PROPOSAL] merge GEODE-8259 to support branches

Strange -- I received the two votes 9 minutes before I got the original message. I'm heading out for the day, so Gester, if you get that third vote, go ahead and merge. Cheers, Dave On Tue, Jun 30, 2020 at 3:58 PM Jinmei Liao wrote: > +1 > > From: Owen Nichols

Re: [Proposal] - RFC etiquette

+1 "Adding a section" (Udo's language) for Use Cases is a positive way of encouraging RFC authors to provide that material, without saying it's an iron-clad requirement. Exactly the right way to do it. Commenters can request more detail when they review it. On Thu, Jul 9, 2020 at 4:31 PM Donal

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

Looks good, Bruce. Please backport. On Tue, Jun 16, 2020 at 4:01 PM Owen Nichols wrote: > +1 > > On 6/16/20, 3:54 PM, "Jianxia Chen" wrote: > > +1 > > On Tue, Jun 16, 2020 at 3:24 PM Bruce Schuchardt > wrote: > > > This PR has been merged to develop. It fixes a problem with the

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

Looks good. Merge to 1.13 (if you haven't already). -Dave On Fri, Jun 26, 2020 at 10:05 AM Donal Evans wrote: > +1 > > From: Owen Nichols > Sent: Friday, June 26, 2020 9:59 AM > To: dev@geode.apache.org > Subject: Re: [PROPOSAL] merge GEODE-8195 to

Re: [Proposal] Add REST command for Restore Redundancy to 1.13 (GEODE-8095)

OK - you've got the votes, Mark, thanks for your contribution. I'm persuaded by the positive arguments and assurances of low risk. All: let's focus on getting to RC1. I'm not comfortable with "as this release has drug on for so long, it might be just about time to reset expectations". Let's clean

Re: Fate of master branch

+1 if we can override git’s ‘master’ default and establish ‘develop’ in its place. Otherwise renaming to ‘main’ would solve the problem with the negative connotations. NB: Mark, I think the 3-vote convention is just for back-ports to the release-branch. I don’t think of it as applying to a

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

e: [Proposal] Back-port doc fixes to support/1.13 > > +1 > > On 6/29/20, 10:32 AM, "Jinmei Liao" wrote: > > +1, yay to doc changes. > ____ > From: Dave Barnes > Sent: Monday, June 29, 2020 10:30 AM > To: dev@geode

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

These five doc changes correct doc bugs and format errors that have caused users pain. I propose that we back-port them to support/1.13: GEODE-8193: Broken link in statistics list GEODE-7956, GEODE-7519: Docs should mention dot as a valid region name character GEODE-8304: Better highlight steps

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

For completeness, GEODE-7519 was a typo, should have been GEODE-7518. On Mon, Jun 29, 2020 at 10:44 AM Dave Barnes wrote: > That was quick - thanks, all. I'll proceed with the back-port of these 5 > fixes. > > On Mon, Jun 29, 2020 at 10:36 AM Donal Evans wr

Re: Refactor to Restore Redundancy Command for 1.13?

If I understand correctly that the refactored version has already been checked in and tested on `develop`, then we have enough approvals to add this to 1.13. Go ahead, Mark. On Tue, Jun 16, 2020 at 8:45 AM Joris Melchior wrote: > Yes, +1 on this change. > > Joris >

Re: [PROPOSAL] back port fix for GEODE-8251 to support branches

OK to backport, Jinmei. Thanks for your contribution. -Dave (I saw a +1 vote from Owen in another email client, though it doesn’t seem to show up in this rendering of the thread. Thought I had successfully worked around the email issue. Hmmm…) > On Jun 19, 2020, at 8:47 AM, Jianxia Chen

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

Wow, +103! Sounds like an endorsement. On Thu, Jun 18, 2020 at 12:44 PM Owen Nichols wrote: > +1 > > On 6/18/20, 12:15 PM, "Dick Cavender" wrote: > > +1 > > -Original Message- > From: Ernie Burghardt > Sent: Thursday, June 18, 2020 10:49 AM > To:

Re: [VOTE] Backporting of GEODE-8261 to 1.13 release branch.

Thanks for taking care of this, Naba. > On Jun 19, 2020, at 12:27 PM, Nabarun Nag wrote: > > Thank you all for the votes needed for the backport. It has been backported > to support/1.13 branch > > GEODE-8261: Added a null check for the proxyID. (#5251) > > Regards > Naba > > >

Re: Refactor to Restore Redundancy Command for 1.13?

rk > > On 6/16/20, 2:07 PM, "Dave Barnes" wrote: > > If I understand correctly that the refactored version has already been > checked in and tested on `develop`, then we have enough approvals to > add > this to 1.13. > Go ahead, Mark. > >

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

Looks like the community approves, Ju@n. Go ahead and merge. Thanks, Dave On Wed, Jun 10, 2020 at 10:37 AM Joris Melchior wrote: > +1 > > From: Ju@N > Sent: June 10, 2020 6:18 > To: dev@geode.apache.org > Subject: [PROPOSAL]: BackPort GEODE-8029 to

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

OK, Bruce -- merge away. Thanks, Dave On Thu, Jun 11, 2020 at 12:47 PM Dick Cavender wrote: > +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 >

Re: [DISCUSSION] Stop using the Geode Repository for Feature/WIP Branches

Suppose I want to commit to another contributor's fork. How can they grant me permission to do so? (This is a common predicament for me when I'm reviewing doc PRs.) On Wed, Jun 3, 2020 at 2:04 PM Xiaojian Zhou wrote: > We have discussed that when in Common team. The current solution worked >

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

Please go ahead, Jinmei. Thanks for your contribution. On Wed, Jul 22, 2020 at 3:11 PM Dick Cavender wrote: > +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

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

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

Re: [PROPOSAL] Postpone Geode 1.14

+1 On Tue, Jul 28, 2020 at 5:05 PM Donal Evans wrote: > +1 > > From: Owen Nichols > Sent: Tuesday, July 28, 2020 4:38 PM > To: Alexander Murmann ; dev@geode.apache.org < > dev@geode.apache.org> > Subject: Re: [PROPOSAL] Postpone Geode 1.14 > > +1 > > > --- >

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

OK, Eric, go ahead. Thanks for your contribution! Dave On Tue, Jul 28, 2020 at 5:15 PM Donal Evans wrote: > +1 > > From: Dick Cavender > Sent: Tuesday, July 28, 2020 4:53 PM > To: dev@geode.apache.org > Subject: RE: [PROPOSAL] port GEODE-8323 changes to

Re: [PROPOSAL] port GEODE-8385 changes to support/1.13

+1 Thanks, Bruce. On Wed, Jul 29, 2020 at 8:22 AM Jianxia Chen wrote: > +1 > > On Wed, Jul 29, 2020 at 8:04 AM Bruce Schuchardt > wrote: > > > This concerns a hang during recovery from disk. The problem was > > introduced in 1.13. > > > > https://issues.apache.org/jira/browse/GEODE-8385 > > >

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

t; > +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 - p

<    1   2   3   4   >