Re: Volunteer For Creating February Board Report

I'll volunteer for February. On Thu, Feb 2, 2017 at 10:50 AM, Mark Bretl wrote: > Hi, > > Its that time again for us to create a board report for the February, the > 15th, board meeting, are there any volunteers for creating a draft? > > Initial report should be submitted

Feb 2017 Board Report DRAFT FOR REVIEW (need your input on Tuesday 2/7 if possible)

Please review and comment by COB Tuesday, 2/7/2017, as the report is due on Wednesday. Thanks! ## Description: - Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high

Discrepancies in dev mailing list archives?

There are two archives for the dev@geode.apache.org mailing list. Has anyone else noticed that they differ? When I was searching for status report material, there were some messages that turned up only in one of the two archives. Apache archive: http://mail-archives.apache.org/mod_mbox/geode-dev/

Re: Feb 2017 Board Report DRAFT FOR REVIEW (need your input on Tuesday 2/7 if possible)

gt;> On Mon, Feb 6, 2017 at 5:38 PM, Dan Smith <dsm...@pivotal.io> wrote: >>> >>> Looks good! A couple of minor edits: >>>> >>>> "open dev list" => "dev list" >>>> "commmitters" => "commit

Geode February Project report, final

All, The report below includes all corrections I've received. I elected to keep the Markdown-style link to the release notes on the theory that it's readable as plain text, too. Mark, Please submit this report for me. I seem to lack credentials to put it in the specified posting sites (Apache

Re: The next release (v1.1.0)

The first two are doc tasks - should be no problem to get them done by 2/15. On Tue, Jan 24, 2017 at 1:14 PM, Mark Bretl wrote: > Do we think we can get these done and get a release before the next board > meeting (2/15)? I think it would be an excellent point on our report.

Re: The next release (v1.1.0)

Sorry, I was reading too quickly. The third one should be do-able, as well. On Tue, Jan 24, 2017 at 1:23 PM, Dave Barnes <dbar...@pivotal.io> wrote: > The first two are doc tasks - should be no problem to get them done by > 2/15. > > On Tue, Jan 24, 2017 at 1:14 PM, Mark Bretl

Re: for discussion: separate website into its own repo

The current mechanism for publishing the website is quite convoluted. As you point out, the software and the website are only loosely coupled. I see only good outcomes for allowing the repos to reflect that reality. On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller wrote: > I

Re: Review Request 56626: GEODE-2479 Remove docs reference to gemstone.com package

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56626/#review165415 --- Ship it! Ship It! - Dave Barnes On Feb. 14, 2017, 12:22 a.m

New committers added to Geode Site Community page

Ken Howe and Kevin Duling have been added to the website's Committers list. Welcome, Ken and Kevin!

Re: Review Request 53971: GEODE-2125 Add doc note to not use kill cmd on servers

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/53971/#review156533 --- Ship it! Ship It! - Dave Barnes On Nov. 22, 2016, 12:17 a.m

Re: Review Request 54000: GEODE-2135 Update schema location in the docs

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/54000/#review156663 --- Ship it! Ship It! - Dave Barnes On Nov. 22, 2016, 9:56 p.m

Re: Review Request 54723: GEODE-2208 Document transactions limitation with mixed region types.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/54723/#review159186 --- Ship it! Ship It! - Dave Barnes On Dec. 14, 2016, 4:33 p.m

Re: Review Request 54499: GEODE-2092 Update docs with security examples location

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/54499/#review158453 --- Ship it! Ship It! - Dave Barnes On Dec. 7, 2016, 8:59 p.m

Re: Hosted API docs update?

, Jan 13, 2017 at 10:25 AM, Dave Barnes <dbar...@pivotal.io> wrote: > Hi Sai, > I filed a JIRA ticket on this a couple of weeks ago: GEODE-2264. > First obstacle I encountered was that the Gradle builds that update > Javadocs do so component-by-component, so task number 1 wo

Re: Hosted API docs update?

@Anthony Thanks for the pointer, but I guess I need a little more detail. When I look at the javadocs in my Geode source repo, I find a set at geode-assembly/build/javadocs that's labeled 1.1.0-SNAPSHOT. I went to the Geode website Releases page to download the binary distribution

Re: Hosted API docs update?

Hi Sai, I filed a JIRA ticket on this a couple of weeks ago: GEODE-2264. First obstacle I encountered was that the Gradle builds that update Javadocs do so component-by-component, so task number 1 would be to create a single Geode-wide Javadoc tree. Once that's in place, it's just a matter of

Re: Hosted API docs update?

wrote: > Latest development javadocs built with the nightly build and are available > at > https://builds.apache.org/view/G/view/Geode/job/Geode- > nightly/lastSuccessfulBuild/artifact/geode-assembly/build/ > install/apache-geode/javadoc/ > > --Mark > > On Fri, Jan 13, 20

Re: Review Request 55351: GEODE-2285: fix some typos in GFSH code

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55351/#review161020 --- Ship it! Ship It! - Dave Barnes On Jan. 9, 2017, 7:18 p.m

Re: Review Request 54321: GEODE-2156 Remove incubating references

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/54321/#review158029 --- Ship it! Ship It! - Dave Barnes On Dec. 3, 2016, 4:33 p.m

Re: Review Request 54315: GEODE-2146 document new privileges req'd for deploy

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/54315/#review157805 --- Ship it! Ship It! - Dave Barnes On Dec. 2, 2016, 5:46 p.m

Re: Review Request 55059: GEODE-2252 Update docs on vSphere performance tuning

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55059/#review160252 --- Ship it! Ship It! - Dave Barnes On Dec. 27, 2016, 11:04 p.m

Re: The right way to remove a region's cache listener?

What gfsh command (if any) lists the cache-listeners available on a given region? Seems like if the intention is to support adding and deleting by name, there should be a way to list existing names. On Tue, Jan 3, 2017 at 11:29 AM, Jinmei Liao wrote: > +1 for remove by

Re: Matching Unix Committer List And Website Committer List

ebook instead of listing directly on the website. > > Since Whimsy requires credentials, I don't think that would be good > choice > > > > I am working on re-adding committers which are missing from the TLP > > transition. > > > > --Mark > > > >

Re: Review Request 58088: GEODE-2738: There are many typos throughout the codebase.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58088/#review170656 --- Ship it! Ship It! - Dave Barnes On March 30, 2017, 10:26

Re: A force push happened to geode-native develop!?!

> It also would seem prudent to block 'git push —delete’ on shared branches Isn't that how we clean up feature branches? On Wed, Mar 8, 2017 at 1:55 PM, Jared Stewart wrote: > +1 to blocking force pushes on shared branches. It also would seem > prudent to block 'git push

Re: Review Request 61417: GEODE-3328: adding ssl-truststore-type to the config

etc. KEYSTORE_TYPE is included for each group, but not TRUSTSTORE_TYPE. Is this correct? - Dave Barnes On Aug. 3, 2017, 9:15 p.m., Jinmei Liao wrote: > > --- > This is an automatically generated e-mail. To reply, visi

Review Request 60873: GEODE-2189 Docs: Update Swagger UI links Added link to OpenAPI specification.

connect as they should. Thanks, Dave Barnes

Review Request 60881: GEODE-3207 Swagger library updates: update user guide

/60881/diff/1/ Testing --- Compiled manual to verify formatting, executed examples to verify that they work as advertised. Thanks, Dave Barnes

Re: New Committer And PMC Member: Joey McAllister

Welcome, Joey, to our very exclusive club. You'll especially enjoy the monthly picnics! On Tue, Jul 25, 2017 at 11:58 AM, Michael William Dodge wrote: > Welcome, Joey! > > Sarge > > > On 25 Jul, 2017, at 11:58, Mark Bretl wrote: > > > > The Apache Geode

Re: Review Request 61417: GEODE-3328: adding ssl-truststore-type to the config

2017 at 12:15 PM, Jinmei Liao <jil...@pivotal.io> wrote: > > > > On Aug. 3, 2017, 11:36 p.m., Dave Barnes wrote: > > > 1. The help message for the property should state what it does and > whether it has a default. JKS was our assumption in the past, but with the &g

Re: Gitbox enables the full GitHub workflow

+1 I'm interested to see how it works for geode-site, which has a sorta quirky build/branch structure. On Tue, Aug 22, 2017 at 10:49 AM, Jared Stewart wrote: > +1 for moving the other repos to Gitbox > > On Aug 22, 2017 10:43 AM, "Anthony Baker" wrote: >

Re: [VOTE] Using Pull Requests over Review Board

+0 Proposal as written says "...for changes that would require peer review before committing...". If this means that minor changes (in my case, typo repairs are the common case) can be checked in without going through a PR process, I can go with the group decision. Still see no compelling need to

Re: release 1.2

I have staged a v1.2 doc update for the Apache Geode website, using RC 1 versions of the User Guide and the Javadocs. Later release candidates are unlikely to require doc changes, other than the Wiki-based relnotes, so I'm nearly certain this will be the final version. When we merge or rename this

Review Request 59562: GEODE-2941 Pulse documentation is outdated

user guide (with bookbinder) - no broken links. Selected sections reviewed by developers while in draft form. Thanks, Dave Barnes

Review Request 59653: GEODE-2420 Warn a user if they try to export too much data. Added gfsh ref docs for --file-size-limit option.

://reviews.apache.org/r/59653/diff/1/ Testing --- Thanks, Dave Barnes

Re: [DISCUSS] Using Pull Requests over Review Board

I've used both PRs and Review Boards for doc changes. The Review Board's targeted reviewer list, as Bruce points out, is a plus. It would be great if PRs could do that. On Thu, Jun 8, 2017 at 9:28 AM, John Blum wrote: > +1 to Bruce's comments. > > PRs are for contributors that

Review Request 59923: GEODE-3029: Tomcat Install Documentation has incorrect required JARs

Guide from source using bookbinder, new text introduced no errors. Thanks, Dave Barnes

Review Request 59866: GEODE-2555: Region Management docs page refers to the wrong field (id= should be refid=)

--- Found and corrected 3 occurrences. Thanks, Dave Barnes

Review Request 59027: GEODE-1996 Confusing references to "multicast" for locators ports

his checkin to save the overhead of creating a separate ticket and review cycle. Thanks, Dave Barnes

Review Request 59034: GEODE-2352 Document that REST API requires two properties

to default, they may not be publicly visible. So we'll say they're optional, but that it's *good practice* to specify them for visibility. This checkin also picks up some other corrections regarding API library name and some format fixes. Thanks, Dave Barnes

Re: [DISCUSS] GEODE-3617 Replace gemfire prefix with geode

Here's an updated link to the properties spreadsheet that should have wider viewability: https://docs.google.com/spreadsheets/d/1C2D7cpcYMy5bd0aXXReJn6wWsBuLZrCegl7_cevvKo0/edit?usp=sharing On Tue, Sep 19, 2017 at 12:10 PM, Dave Barnes <dbar...@pivotal.io> wrote: > There's no si

Re: Rebase and squash before merging PRs

me to squash > yourself. > > Then the pull would show your new rebased commits for someone to approve > and merge (squash too if they want). > > -Jake > > > > On Oct 5, 2017, at 5:20 PM, Dave Barnes <dbar...@pivotal.io> wrote: > > > > Jake, > > Say

Re: Rebase and squash before merging PRs

Jake, Say I have a PR with the original commit plus two more to incorporate reviewer suggestions. How is it possible within the github UI to just rebase without also merging? I don't see that choice in the gitbox pulldown menu. On Thu, Oct 5, 2017 at 4:59 PM, Jacob Barrett

Re: [DISCUSS] Removal of "Submit an Issue" from Geode webpage

Done. On Mon, Oct 2, 2017 at 10:05 AM, Dave Barnes <dbar...@pivotal.io> wrote: > Created GEODE-3726 (https://issues.apache.org/jira/browse/GEODE-3726) > > On Mon, Oct 2, 2017 at 9:07 AM, Dave Barnes <dbar...@pivotal.io> wrote: > >> I volunteer to handle this

Re: How to setup 2-phase auth for Github

It's kind of buried under the "TOTP Mobile App" heading. You connect Google Authenticator to Github when you shoot a photo of the code square. On Tue, Sep 12, 2017 at 10:58 AM, Kirk Lund wrote: > I'm trying to get setup for gitbox, but a couple details are not panning > out

Re: [DISCUSS] Removal of "Submit an Issue" from Geode webpage

l.io> wrote: > > > > > Yes please, especially since I'm not the one posting these :) > > > > > > On Fri, Sep 29, 2017 at 11:35 AM, Dave Barnes <dbar...@pivotal.io> > > wrote: > > > > > > > +1 to removing the button. > > > &g

Re: [DISCUSS] Removal of "Submit an Issue" from Geode webpage

Created GEODE-3726 (https://issues.apache.org/jira/browse/GEODE-3726) On Mon, Oct 2, 2017 at 9:07 AM, Dave Barnes <dbar...@pivotal.io> wrote: > I volunteer to handle this, beginning with a JIRA ticket. > I'm not sure we need to add any text anywhere. On the Geode home page > t

Re: [DISCUSS] Removal of "Submit an Issue" from Geode webpage

+1 to removing the button. +1 to Dan's suggestion of nudging users toward the mailing list. I see a place we could add a few words on the Community page, where the Users mailing list is the first entry; add to the blurb "or raise an issue". (The Mailing Lists menu choice takes you here, as well.)

Re: Font for geode.apache.org

If you're asking about the line "Performance is key..." and the paragraph that follows, it's a font called "Klavika web", specified in the file geode-site.css. See https://processtypefoundry.com/fonts/klavika/complete-specs-webfonts for a description. On Mon, Nov 27, 2017 at 10:10 AM, Michael

Re: Has github changed some preferences?

I was bitten by that earlier this afternoon. Instead of 2 files modified in 1 commit, I had 5,000 commits! On Wed, Dec 6, 2017 at 3:52 PM, Jens Deppe wrote: > It seems that (at least my github pages) are acting a bit differently. > > When creating a Pull Request make sure

Re: Default branch for geode should be 'develop'

+1 On Mon, Dec 11, 2017 at 3:14 PM, Nabarun Nag wrote: > +1 > > On Mon, Dec 11, 2017 at 3:10 PM Bruce Schuchardt > wrote: > > > +1 > > > > > > On 12/11/17 1:40 PM, Jens Deppe wrote: > > > Currently, github has the default branch for apache/geode set to

Re: Volunteer for ASF Board report?

I'll do it. On Fri, May 4, 2018 at 2:27 PM, Anthony Baker wrote: > Bumping this thread. Any volunteers? > > Anthony > > > > On Apr 25, 2018, at 4:44 PM, Anthony Baker wrote: > > > > Correction, the due date is 5/9. > > > >> On Apr 25, 2018, at 11:33 AM,

Quarterly report - DRAFT for your review

Here's the near-final draft of our quarterly report. Responses received by 5pm PDT today (May 8) will be incorporated. Thanks, Dave Barnes ## Description: - Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain

Re: Quarterly report - DRAFT for your review

rds > > > Naba > > > > > > On Tue, May 8, 2018 at 10:44 AM Joey McAllister < > jmcallis...@pivotal.io> > > > wrote: > > > > > > > Looks good to me, too. Thanks, Dave! > > > > > > > > On Tue, May 8, 2018 at

Re: [PROPOSAL]: Finer Grained Security When Invoking Methods in OQL

Juan, Nice work - you've obviously given this plenty of thought. I'm not qualified to comment on the technical aspects of your proposal, but as a proofreader I noticed that there are a couple of occurrences of "invokation" that should be spelled "invocation". Dave On Mon, Jun 25, 2018 at 2:52

Re: [jira] [Commented] (GEODE-3843) gfsh shutdown error message suggests non-existent option

; gfsh shutdown error message suggests non-existent option > > > > > > Key: GEODE-3843 > > URL: https://issues.apache.org/jira/browse/GEODE-3843 > > Project: Geode > &g

Re: [jira] [Commented] (GEODE-3843) gfsh shutdown error message suggests non-existent option

...(continued) And perhaps the real point of the ticket was missed: there's no such option as "--shutdown-locators", so the message definitely needs a rewrite. On Mon, Oct 23, 2017 at 8:51 AM, Dave Barnes <dbar...@pivotal.io> wrote: > Swapnil, > Are you suggesting that the

Re: Geode Website Docs page: Proposal to limit the number of versions listed.

s a developer I access > the Java docs in my IDE based on which ever version I am using to build > geode application. > > Sai > > On Wed, Jan 31, 2018 at 10:23 AM, Dave Barnes <dbar...@pivotal.io> wrote: > >> I'm hearing that access to earlier versions of the User Gui

Re: Geode Website Docs page: Proposal to limit the number of versions listed.

just rely on > > Google? ;) > > > > Sarge > > > > > On 29 Jan, 2018, at 10:39, Dave Barnes <dbar...@pivotal.io> wrote: > > > > > > Question: > > > How many versions of the User Documentation and the Javadocs do we need > > t

ASF Quarterly report - please review by Tuesday Noon

Please review this report and send me any corrections by Noon on Tuesday, 12/13/18. Thanks, Dave ## Description: - Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high

ASF Quarterly report - final

Here's the final report, approved by all who reviewed it. Mark: I lack credentials to submit this myself - I'll leave that to you. Cheers, Dave ## Description: - Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to

Re: Geode Jira/GitHub Integration configuration changes

I must have just missed the cutoff - my PR (#1207), which I created at 2:48, generated diffs in the JIRA. On Wed, Dec 27, 2017 at 3:06 PM, Kirk Lund wrote: > INFRA has made the change. Does anyone have a PR ready to submit so I can > confirm the behavior on a Jira ticket? > >

Re: August 2018 Board Report Volunteer

...and just between you and me, if people knew how easy is to generate this report using the template, they wouldn't be so reluctant to put forth a little effort on behalf of this great project :). Oh, did I say that out loud? On Thu, Jul 26, 2018 at 1:45 PM, Dave Barnes wrote: > Hi M

Re: August 2018 Board Report Volunteer

> > - iss...@geode.apache.org: > >- 54 subscribers (up 0 in the last 3 months): > >- 2991 emails sent to list (6890 in previous quarter) > > > > - u...@geode.apache.org: > >- 242 subscribers (down -9 in the last 3 months): > >- 141 emails

Re: [VOTE] Apache Geode 1.5.0 RC1

+1 User Guide builds correctly from source, javadocs look up-to-date On Wed, Mar 21, 2018 at 8:27 AM, Jens Deppe wrote: > +1 - basic gfsh functionality looks good on Windows. > > On Tue, Mar 20, 2018 at 5:07 PM, Anthony Baker wrote: > > > md5 generation is

Re: Next release: 1.5.0

gt; > On Mon, Feb 26, 2018 at 5:03 PM Dave Barnes <dbar...@pivotal.io> wrote: > > > Status on the 3 doc issues: > > GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered > > GEODE-4101: redirect-output - Dave, in process, on track > > GEODE-3

Re: Next release: 1.5.0

Status on the 3 doc issues: GEODE-4737 / GEODE-3915: JSON args in gfsh - Karen's got it covered GEODE-4101: redirect-output - Dave, in process, on track GEODE-3948: client timeout - Dave, in process. Probably on track - will keep you posted On Mon, Feb 26, 2018 at 11:07 AM, Anthony Baker

Re: [DISCUSS] Predictable minor release cadence

If we go with more frequent releases, the number of available releases will ramp up quickly. What would be the best policy regarding earlier releases? The Geode website's Release page currently links to 1.7.0, 1.6.0, 1.5.0, and 1.4.0. Would it be prudent to adopt a policy (as suggested by Craig

Re: Release process for Apache Geode wiki

Good work! I had no idea there was so much involved with regard to Apach permissions and such. I fixed a few typos / rewordings. Very minor. There's one thing I wanted to ask you about: The sample paragraph under release doc preparation is one long line. Would it be OK to reformat so it wraps?

Re: Geode Native & Apache Geode 1.8 Release

Re: the docs links mentioned in Anthony's message: docs/README.md - the reference to the Geode CONTRIBUTE.md file is useful. I think we can assume that a user of the geode-native API will have a Geode installation, too. docs/api/unix_index.html and docs/api/win_index.html - These files (and their

Re: Geode Native & Apache Geode 1.8 Release

unix_index.html and win_index.html cannot simply be removed, as they're referenced by Cmake. I created a ticket to address this: https://issues.apache.org/jira/browse/GEODE-5958. On Tue, Oct 30, 2018 at 11:48 AM Dave Barnes wrote: > Re: the docs links mentioned in Anthony's message: >

Re: [VOTE] Time-based release schedule for minor releases

+0 Willing to try any reaonable plan that emerges. Would like to see some articulation of an "upgrade policy" if such things exist in the open source universe. That is, will each quarterly (or whatever) release necessarily be backward compatible with the previous release? Will a user be able to

Re: [VOTE] Apache Geode 1.7.0 RC1

+0 Recasting my vote, just for full disclosure. I found a (very minor) problem in the source release doc files: If a user builds their own docs from sources, they'll say version 1.8. - NOT (even close to) a showstopper - This will NOT affect the User Guide we'll push to the website with the

Re: [VOTE] Apache Geode 1.7.0 RC2

+1 Downloaded the release & successfully ran some representative gfsh commands. There is still a problem that I noted in my RC1 review: the user guide config files incorrectly specify v1.8. This is not a showstopper, but this time I have created a JIRA ticket (GEODE-5795) so if (heaven forfend) we

Re: New Geode PMC Chair: Karen Miller

Thanks, Mark - Welcome Karen! On Mon, Nov 26, 2018 at 12:17 PM Dan Smith wrote: > Congratulations Karen! And thanks for all of your hard work, Mark! > > -Dan > > On Mon, Nov 26, 2018 at 11:56 AM Mark Bretl wrote: > > > Hello Geode Community, > > > > After two years, the Project Management

Re: [VOTE] Apache Geode 1.7.0 RC1

+1 Downloaded, ran some gfsh commands, opened & browsed javadocs. On Tue, Sep 18, 2018 at 2:16 PM, Jinmei Liao wrote: > +1 downloaded the distribution, ran gfsh and execute random gfsh commands > and verified pulse. > > On Tue, Sep 18, 2018 at 1:36 PM Ryan McMahon wrote: > > > +1 > > > > -

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

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

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

> 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 that repo; should be ready

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

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

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

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: [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',

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

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

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. To

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

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

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

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

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

to the 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: [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.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

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

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

  1   2   3   4   >