Apache Geode PMC quarterly report: DRAFT for your review

Please respond by noon tomorrow. Pretty complete, as far as I know, except for public events and presentations. Thanks, Dave Description: Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency perform

Re: Apache Geode PMC quarterly report: DRAFT for your review

rmance > - Explored the use of micrometer for exposing metrics of cache operations > > Anthony > > > > On Feb 12, 2019, at 3:34 PM, Dave Barnes wrote: > > > > Please respond by noon tomorrow. > > Pretty complete, as far as I know, except for public events and &

Re: Geode 1.9 Release Manager

Sai, The Geode 1.8 release included (for the first time) a source snapshot of the geode-native repo. As far as I know, the same treatment would be in order for v1.9. On Fri, Feb 15, 2019 at 9:01 AM Bruce Schuchardt wrote: > I would like to get GEODE-6369 into the next release but that can be >

Re: Geode 1.9 Release Manager

think as a place holder I can go ahead still >> create a release branch for Geode Native? >> >> Sai >> >> >> On Fri, Feb 15, 2019 at 9:51 AM Dave Barnes wrote: >> >>> Sai, >>> The Geode 1.8 release included (for the first time) a source sna

Re: [DISCUSS] Proposal to re-cut Geode 1.9.0 release branch

The Geode 1.9.0 release includes a source-only release of the geode-native repo. There's a pull-request in process to update version numbers and the doc build environment in that repo; should be ready to merge tomorrow morning. On Tue, Mar 19, 2019 at 5:20 PM Dale Emery wrote: > The Micrometer A

Re: [DISCUSS] Proposal to re-cut Geode 1.9.0 release branch

this release? > > On Tue, Mar 19, 2019 at 5:29 PM Dave Barnes wrote: > > > The Geode 1.9.0 release includes a source-only release of the > geode-native > > repo. There's a pull-request in process to update version numbers and the > > doc build environment in t

Re: [DISCUSS] Proposal to re-cut Geode 1.9.0 release branch

geode-native is ready to into the 1.9 release candidate build. On Wed, Mar 20, 2019 at 10:42 AM Dave Barnes wrote: > The geode-native PR will be ready to check in momentarily. Just waiting > for Travis to do its diligence. > > On Wed, Mar 20, 2019 at 9:47 AM Alexander Murm

Re: release/1.9.0 - are we ready?

The geode-native repo is up to date and ready for the 1.9 release. On Mon, Apr 8, 2019 at 9:27 AM Sai Boorlagadda wrote: > Hello, > > It looks like we have fixed required licensing and bom related issues and > the pipeline is looking much stable with other issues that have been fixed > in last c

Re: [VOTE] Apache Geode 1.9.0 RC1

-1 The file geode-book/redirects.rb contains an incorrect version path component: "110". Should be "19". Two occurrences. Customers will not be able to build the user guide from sources without this change. Should be: ``` rewrite '/', '/docs/guide/19/about_geode.html' rewrite '/index.html', '/do

Re: [VOTE] Apache Geode 1.9.0 RC4

+1 Checked the user guide builds and API docs for geode and geode-native. LGTM. On Tue, Apr 23, 2019 at 1:33 PM Dan Smith wrote: > +1 > > Looks good to me. I ran the geode-release-check against the repo. > > -Dan > > On Fri, Apr 19, 2019 at 5:00 PM Owen Nichols wrote: > > > Hello, Geode dev com

Re: [DISCUSS] require reviews before merging a PR

As a writer, I'm a big user of Lazy Consensus: If no one objects, I'm merging my change. Requiring multiple reviews discourages minor improvements. In the doc realm, I'm inclined to check in typo fixes and grammar corrections without even bothering with the PR process, but I do it for the community

Re: Is the documentation wrong here?

@liyuj Congratulations on finding a Geode doc bug. To get the problem on the official "to do" list, you are hereby encouraged to open a JIRA ticket in the Geode project, citing the 'docs' component. Your original email with Jared's response would serve well as the bug description. If you'd like to

Re: Is the documentation wrong here?

@liyuj Do you have a login for the Apache JIRA system? Here's where you go to create a new ticket: https://issues.apache.org/jira/projects/GEODE/issues/GEODE-6803?filter=allopenissues On Tue, Jun 4, 2019 at 10:27 AM Dave Barnes wrote: > @liyuj Congratulations on finding a Geode doc bug

Draft of Apache Geode Quarterly Report (Aug 2019) for your review

Please review by Noon PDT, Tuesday, Aug 13. Thanks! ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architect

Re: Draft of Apache Geode Quarterly Report (Aug 2019) for your review

Apache Geode code base: - 62 code contributors in the past quarter - 344 PRs opened on GitHub in the past quarter - 356 PRs closed on GitHub in the past quarter On Mon, Aug 12, 2019 at 2:10 PM Dave Barnes wrote: > Please review by Noon PDT, Tuesday, Aug 13. Thanks! > > ## De

Re: Draft of Apache Geode Quarterly Report (Aug 2019) for your review

Thanks, Aaron - good catch. On Mon, Aug 12, 2019 at 4:09 PM Aaron Lindsey wrote: > Kind of a small thing, but the Committer-to-PMC ratio seems more like 2:1 > based on the numbers of committers and PMC members below. > > - Aaron > > > On Aug 12, 2019, at 2:22 P

Re: Draft of Apache Geode Quarterly Report (Aug 2019) for your review

ou could call out a number of interesting discussions that > happened on the dev list: > > - CFP process > - Criteria for being a committer > - etc > > Anthony > > > > On Aug 12, 2019, at 4:26 PM, Dave Barnes wrote: > > > > Thanks, Aaron - good catch.

Re: [DISCUSS] Release Geode 1.9.1 with logging improvements

I'll update the docs: - Geode user guide - Geode API docs - Native client user guide - Native client API docs - Apache Geode website On Mon, Aug 19, 2019 at 9:26 AM Owen Nichols wrote: > I will pair with you on a 1.9.1 release. > > > On Aug 19, 2019, at 9:23 AM, Kirk Lund wrote: > > > > I

Re: [VOTE] Apache Geode 1.9.1 RC1 (new vote)

What's the deadline this time? Can't be Aug 27... On Thu, Aug 29, 2019 at 10:04 AM Udo Kohlmeyer wrote: > +1 > > On 8/29/19 9:51 AM, John Blum wrote: > > +1 > > > > On Thu, Aug 29, 2019 at 9:41 AM Kirk Lund wrote: > > > >> +1 (just in case my vote counts) > >> > >> On Thu, Aug 29, 2019 at 9:02

Re: [VOTE] Apache Geode 1.9.1.RC3

+1 Checked the docs: Successfully built viewed the Geode User Guide and the Javadocs. On Fri, Aug 30, 2019 at 11:11 AM Owen Nichols wrote: > Hello Geode dev community, > > This is a release candidate for Apache Geode, version 1.9.1.RC3. > Thanks to all the community members for their contributio

Re: [VOTE] Apache Geode 1.10.0.RC1

+1 Checked the docs: Successfully built AND viewed the Geode User Guide and the Javadocs. On Fri, Aug 30, 2019 at 2:32 PM Jinmei Liao wrote: > + 1 verified the management v2 api is available by default and list of rest > end points. > > On Fri, Aug 30, 2019 at 2:06 PM Dick Cavender > wrote: > >

Re: [VOTE] Apache Geode 1.9.1.RC3

gt; On Tue, Sep 3, 2019 at 10:45 AM John Blum wrote: > > > > > > > 1 more thing... > > > > > > > > I would additionally advise rewording the sentence... > > > > > > > > *> Please add log4j-core to the classpath.* > > >

Re: [VOTE] Apache Geode 1.10.0.RC2

+1 I downloaded the 1.10.0 RC2 Apache Geode release candidate, and also the Geode Native Client source bundle. Successfully built the user guides and API docs in both repos and spot-checked the contents for correct version strings and paths. On Fri, Sep 20, 2019 at 9:26 AM Dick Cavender wrote: >

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: [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 properly.

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: Quick turnaround needed, feedback on this DRAFT Nov board report

+1 LGTM On Wed, Nov 13, 2019 at 9:49 AM Karen Miller wrote: > Draft board report for November 2019. Submitting in 2 hours! Quick > feedback, please! > > ## Description: > The mission of Apache Geode is the creation and maintenance of software > related > to a data management platform that prov

Re: Website Banner Graphic

Found an image in the Pivotal Branding folder that had a better-looking TM. Pushed it to the site - all fixed now. On Thu, Nov 14, 2019 at 1:28 PM Joey McAllister wrote: > Nick: I think the pertinent info on the trademarks page is this: > > "The Apache Software Foundation considers the names of

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: > > > >

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: 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

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 to

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

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

Request for Docker Hub permissions

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

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 disa

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 wr

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 wr

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: 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

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

Re: [VOTE] Using Github issues and wiki for geode-kafka-connector project

+1 I like the look of the samples. I also want to echo Anthony and Blake: Accessibility is huge, not only because it smooths the way for adding content, but for pruning outdated material. On 4/24/20, 7:18 AM, "Blake Bender" wrote: +1 - Wow, research - nice work, Naba, this is great! J

[DISCUSS] Geode 1.13 support branch planning

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

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

[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 develo

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

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

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 i

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 mi

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 wro

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, co

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 In

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 GEOD

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, May

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: [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] Merge PR 5103 (GEODE-8083) to support/1.13

t; > > > 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-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 Mel

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 informat

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

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

tation 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: > > >

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 up

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 Nichol

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 1

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: 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 Eva

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 al

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 > pe

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 support/1.12

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: 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: Refactor to Restore Redundancy Command for 1.13?

t; Mark > > 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 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] 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: dev@geode.apache.o

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 wrote:

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 > > > -Origin

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 gene

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 support/1.13

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

[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

ct: Re: [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@

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 Evan

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: dev@geode.ap

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 > &

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] 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 encountered

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 A

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 GEODE-8

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] - 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 Ev

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 bu

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 suppor

[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 co

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 Gu

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 support

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 > > > --- > Sen

  1   2   3   4   5   >