[DISCUSS and NOMINATE] Time for a new Geode PMC Chair

[Karen Miller]

I've been the Geode PMC chair since December 2018. I'd like to step
down from this position as soon as we nominate and then vote on a new
PMC chair. (See https://www.apache.org/dev/pmc.html#newchair)

Please use this email thread to discuss and nominate. I believe the
only requirement for the PMC chair is that the person already be a
Geode PMC member. You are welcome to self-nominate, or to nominate
another person. After nominations have been made, there will be a
separate thread to allow current PMC members to vote on who will
become the new PMC chair.

Thanks.
Karen Miller
I work for VMware.
This email is written in my capacity as Chair of the Apache Geode PMC.

Re: Geode Quarterly Report DRAFT for your review

[Karen Miller]

I've filed the Geode report.  Thanks, Dave!
Karen Miller
I work for VMware.
This email is written in my capacity as Chair of the Apache Geode PMC.

On Mon, Feb 8, 2021 at 6:47 PM Dave Barnes  wrote:
>
> The numbers come from Apache - I'm not sure how they count 'em up. It was
> our practice for the first years of opensourcehood to appoint people to
> both roles, but that's no longer automatic.
>  I'm going with 110 / 53 ~= 2. Not perfectly in tune, but close enough for
> rock'n'roll.
>
> On Mon, Feb 8, 2021 at 4:17 PM Mark Hanson  wrote:
>
> > Hi Dave,
> >
> > Does the 110 committers number include PMC members? If so, that 2:1
> > doesn't line up. It would be more like 1:1.
> >
> > Thanks,
> > Mark
> >
> > On 2/8/21, 12:13 PM, "Dave Barnes"  wrote:
> >
> > Revised Committer-to-PMC ratio to 2:1 (thanks, Karen)
> >
> > On Mon, Feb 8, 2021 at 12:09 PM Dave Barnes 
> > wrote:
> >
> > > Please respond by noon (PT) Tuesday. 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
> > > architectures.
> > >
> > >
> > > ## Issues:
> > >
> > > There are no issues requiring board attention.
> > >
> > >
> > > ## Membership Data:
> > >
> > > Apache Geode was founded 2016-11-15 (4 years ago)
> > >
> > > There are currently 110 committers and 53 PMC members in this
> > project.
> > >
> > > The Committer-to-PMC ratio is roughly 7:4.
> > >
> > >
> > > Community changes, past quarter:
> > >
> > > - No new PMC members. One member resigned due to retirement (but
> > remains a
> > > committer).
> > >
> > > - No new committers. Two candidates have been proposed and
> > discussed, and
> > > are in the voting process.
> > >
> > >
> > > ## Project Activity:
> > >
> > > - Apache Geode v1.13.1 was released on 2020-11-18.
> > >
> > > - We're actively working on v1.14, which will contain many bug fixes.
> > >
> > > - PMC Member Barry Oglesby published two articles this quarter:
> > >
> > >   - ["Calculating Apache Geode GatewaySender Event Queue,
> > Transmission
> > > and Processing Times"](
> > >
> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmedium.com%2Fswlh%2Fcalculating-apache-geode-gatewaysender-event-queue-transmission-and-p%2Fdata=04%7C01%7Chansonm%40vmware.com%7C3bf16ee091fc47b456ed08d8cc6df06f%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637484119850376975%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=obCBhMTpwpEzmcj239Ju5MCgld5eyMm3XoQpZ0m4zVU%3Dreserved=0
> > >
> > > rocessing-times-c39839bd45a7) in November, 2020.
> > >
> > >   - ["Calculating the Size of an Apache Geode GatewaySender Queue"](
> > >
> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmedium.com%2F%40boglesby_2508%2Fcalculating-the-size-of-an-apache-geode-gatewaysender-queue-7c41e2f6ba83data=04%7C01%7Chansonm%40vmware.com%7C3bf16ee091fc47b456ed08d8cc6df06f%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637484119850376975%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=6gANHVqIfSg0jv6dPRPk1FLhJ8aFm2lg1DSbyN89FRk%3Dreserved=0
> > )
> > > in January,\
> > >
> > >  2021.
> > >
> > >
> > > ## Community Health:
> > >
> > > - 211 issues opened in JIRA, past quarter (-26%)
> > >
> > > - 203 issues closed in JIRA, past quarter (-15%)
> > >
> > > - 416 commits in the past quarter (-21% decrease)
> > >
> > > - 56 code contributors in the past quarter (-1%)
> > >
> > > - 322 PRs opened on GitHub, past quarter (-1%)
> > >
> > > - 321 PRs closed on GitHub, past quarter (-1%)
> > >
> >
> >

Apache board report submitted, Tues. Nov 10

[Karen Miller]

Here is a copy of the board report submitted today, Tues. Nov 10, 2020.
Karen Miller
I work for VMware.
This email is written in my capacity as Chair of the Apache Geode PMC.


## 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 architectures.

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Geode was founded 2016-11-15 (4 years ago)
There are currently 110 committers and 54 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Alexander Murmann on 2020-03-26.
- Sarah Abbey was added as committer on 2020-09-29

## Project Activity:
- Apache Geode v1.13.0 was released on 2020-09-10.
- We're actively working on v1.13.1, which will contain many bug fixes.
- 10 community members presented 8 talks at ApacheCon 2020. See
  https://www.youtube.com/playlist?list=PLU2OcwpQkYCxKxd7dVETcwEtx5AEDIp1j for
  a playlist that includes all 8 talks.

## Community Health:
- 259 issues opened in JIRA, past quarter (-15% decrease)
- 212 issues closed in JIRA, past quarter (-16% decrease)
- 463 commits in the past quarter (-19% decrease)
- 57 code contributors in the past quarter (-6% decrease)
- 324 PRs opened on GitHub, past quarter (-16% decrease)
- 325 PRs closed on GitHub, past quarter (-14% decrease)

Please review and contribute: draft of Nov 2020 Apache board report

[Karen Miller]

All, our board report is due in less than 48 hours.  I've included a
first draft below.
Please help correct my mistakes and let me know of blog posts and presentations
that are not yet on the list.

I think that we might also add to our Project Activity category mentions of the
community's focus.  Would it be a good idea to add something like this?
  - We're actively working on v1.13.1, which will contain many bug fixes.

Since the report is due quite soon, please get corrections/additions
to me before
Tuesday Nov 10 (tomorrow) at 3pm Pacific time.
Thanks.
Karen Miller
I work for VMware.
This email is written in my capacity as Chair of the Apache Geode PMC.


## 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 architectures.

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Geode was founded 2016-11-15 (4 years ago)
There are currently 110 committers and 54 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- No new PMC members. Last addition was Alexander Murmann on 2020-03-26.
- Sarah Abbey was added as committer on 2020-09-29

## Project Activity:
- Apache Geode v1.13.0 was released on 2020-09-10.
- 10 community members presented 8 talks at ApacheCon 2020. See
  https://www.youtube.com/playlist?list=PLU2OcwpQkYCxKxd7dVETcwEtx5AEDIp1j for
  a playlist that includes all 8 talks.

## Community Health:
- 259 issues opened in JIRA, past quarter (-15% decrease)
- 212 issues closed in JIRA, past quarter (-16% decrease)
- 463 commits in the past quarter (-19% decrease)
- 57 code contributors in the past quarter (-6% decrease)
- 324 PRs opened on GitHub, past quarter (-16% decrease)
- 325 PRs closed on GitHub, past quarter (-14% decrease)

August 2020 board report filed

[Karen Miller]

I've filed the August 2020 board report. Thanks for the updates about blogs.
Here is a capture of the report:

## 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
architectures.

## Issues:
There are no issues requiring board attention.
- 309 issues opened in JIRA, past quarter (-3% decrease)
- 244 issues closed in JIRA, past quarter (1% increase)

## Membership Data:
Apache Geode was founded 2016-11-15 (4 years ago) There are currently 109
committers and 54 PMC members in this project.

Community changes, past quarter:
- No new PMC members. Last addition was Alexander Murmann on 2020-03-26.
- No new committers. Last addition was Mario Kevo on 2020-03-23.

## Project Activity:
We're actively working on the version 1.13 release, with many discussions
over
code inclusions that delay the release, but provide a higher quality
product.

There is significant discussion and activity surrounding:
- WAN Configuration for an Ingress Proxy
- Avoiding the queuing of dropped events by the primary gateway sender when
  the gateway sender is stopped
- Geode Redis API improvements
- Modularization / classloader isolation
- Support for an operation that clears a partitioned region

## Community Health:
The Apache Geode dev mailing list had a 26% decrease in traffic, while the
issues mailing list experienced a 32% increase in traffic in Q2.

We are planning a Geode content track for ApacheCon @Home.  We have two days
of content based on submissions from the community.

May-July brought 7 new blog posts:
- "Spring Security & Geode" by community member Juan José Ramos at
   https://medium.com/@jujoramos/spring-security-geode-4670faff47a0
- "Logging Apache Geode GatewaySender Queue Events" by community member
Barry
   Oglesby at https://medium.com/

 @boglesby_2508/logging-apache-geode-gatewaysender-queue-events-e7e19937a542
- "Verifying Apache Geode Region Consistency in Different Distributed
Systems"
   by community member Barry Oglesby at
   https://medium.com/@boglesby_2508/verifying-ap

 ache-geode-region-consistency-in-different-distributed-systems-e15d6edfe15d
- "Geode Write-Behind Event Handling with Spring JPA" by community member
Juan
   José Ramos at https://medium.co

 m/@jujoramos/geode-write-behind-event-handling-with-spring-jpa-a54f17e19709
- "Calculating the Size of an Apache Geode Region" by community member Barry
   Oglesby at https://

medium.com/swlh/calculating-the-size-of-an-apache-geode-region-5ffb3b141464
- "Improving the Performance of Apache Geode Persistence Recovery" by
   community member Jianxia Chen at https://medium.com/@luckycjx

 /improving-the-performance-of-apache-geode-persistence-recovery-af08918d2ef
- "Threads Used in Apache Geode Function Execution" by community member
Barry
   Oglesby at https://m

edium.com/swlh/threads-used-in-apache-geode-function-execution-9dd707cf227c

Re: Draft of August 2020 Geode report to the board

[Karen Miller]

Thanks, Anthony.  Here is Draft 2 of the August board report. Corrections
and comments by Monday at noon please.

## 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
architectures.

## Issues:
There are no issues requiring board attention.
- 309 issues opened in JIRA, past quarter (-3% decrease)
- 244 issues closed in JIRA, past quarter (1% increase)

## Membership Data:
Apache Geode was founded 2016-11-15 (4 years ago)
There are currently 109 committers and 54 PMC members in this project.

Community changes, past quarter:
- No new PMC members. Last addition was Alexander Murmann on 2020-03-26.
- No new committers. Last addition was Mario Kevo on 2020-03-23.

## Project Activity:
We're actively working on the version 1.13 release, with many discussions
over
code inclusions that delay the release, but provide a higher quality
product.

There is significant discussion and activity surrounding:
- WAN Configuration for an Ingress Proxy
- Avoiding the queuing of dropped events by the primary gateway sender when
  the gateway sender is stopped
- Geode Redis API improvements
- Modularization / classloader isolation
- Support for an operation that clears a partitioned region

## Community Health:
The Apache Geode dev mailing list had a 26% decrease in traffic, while the
issues mailing list experienced a 32% increase in traffic in Q2.

We are planning a Geode content track for ApacheCon @Home.  We have two days
of content based on submissions from the community.

May-July brought 7 new blog posts:
- "Spring Security & Geode" by community member Juan José Ramos at
   https://medium.com/@jujoramos/spring-security-geode-4670faff47a0
- "Logging Apache Geode GatewaySender Queue Events" by community member
Barry
   Oglesby at https://medium.com/

 @boglesby_2508/logging-apache-geode-gatewaysender-queue-events-e7e19937a542
- "Verifying Apache Geode Region Consistency in Different Distributed
Systems"
   by community member Barry Oglesby at
   https://medium.com/@boglesby_2508/verifying-ap

 ache-geode-region-consistency-in-different-distributed-systems-e15d6edfe15d
- "Geode Write-Behind Event Handling with Spring JPA" by community member
Juan
   José Ramos at https://medium.co

 m/@jujoramos/geode-write-behind-event-handling-with-spring-jpa-a54f17e19709
- "Calculating the Size of an Apache Geode Region" by community member Barry
   Oglesby at https://

medium.com/swlh/calculating-the-size-of-an-apache-geode-region-5ffb3b141464
- "Improving the Performance of Apache Geode Persistence Recovery" by
   community member Jianxia Chen at https://medium.com/@luckycjx

 /improving-the-performance-of-apache-geode-persistence-recovery-af08918d2ef
- "Threads Used in Apache Geode Function Execution" by community member
Barry
   Oglesby at https://m

edium.com/swlh/threads-used-in-apache-geode-function-execution-9dd707cf227c

>
>

Draft of August 2020 Geode report to the board

[Karen Miller]

Here's a first draft of a board report.  I'd like to include some of the
project's many blog posts (any new videos? did anyone give a Geode talk at
a workshop or conference?) in our Community Health section.  Please send me
a link and hopefully an approximate date when the blog was posted.

Please approve or get me additions/corrections before Monday August 10 at
noon Pacific time, so I can file our report on time.
Thanks.  Karen

## 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
architectures.

## Issues:
There are no issues requiring board attention.
- 309 issues opened in JIRA, past quarter (-3% decrease)
- 244 issues closed in JIRA, past quarter (1% increase)

## Membership Data:
Apache Geode was founded 2016-11-15 (4 years ago)
There are currently 109 committers and 54 PMC members in this project.

Community changes, past quarter:
- No new PMC members. Last addition was Alexander Murmann on 2020-03-26.
- No new committers. Last addition was Mario Kevo on 2020-03-23.

## Project Activity:
We're actively working on the version 1.13 release, with many discussions
over code inclusions that delay the release, but provide a higher quality
product.

## Community Health:
The Apache Geode dev mailing list had a 26% decrease in traffic, while the
issues mailing list experienced a 32% increase in traffic in Q2.

We are planning a Geode content track for ApacheCon @Home.  We have two days
of content based on submissions from the community.

Re: Geode Board Report due by Wed Aug 12nd - Initial Reminder

[Karen Miller]

Still no volunteers?  It is a nice service that you can perform for our
community.
Thanks.  Karen


On Tue, Aug 4, 2020 at 9:15 AM Karen Miller  wrote:

> Can I get a volunteer to draft our August 2020 report?  Doesn't take much
> time. Help is available for the asking if you've never done this community
> activity before.  First draft would be super by this Friday, August 7.
> Thanks.  Karen
>
> -- Forwarded message -
> From: Roy T. Fielding 
> Date: Mon, Aug 3, 2020 at 10:52 AM
> Subject: Geode Board Report due by Wed Aug 12nd - Initial Reminder
> To: Karen Miller 
> Cc: 
>
>
> Hello,
>
> According to our records, you are listed as the chair of Geode,
> a committee that is due to submit a report by Wed Aug 12nd
> for the next ASF board meeting. This is an initial reminder to prepare a
> report for Geode and submit it as described below.
>
> Thank you for being a responsible project chair and helping us maintain
> oversight over the Apache Software Foundation. If, for whatever reason,
> a full report is not possible by the deadline, please report just that.
> It's okay to postpone a report by a month.
>
> Please note that we have initiated a new process for reviewing
> and approving these reports, asynchronously, during the week prior
> to our scheduled board meeting.
>
> Reports received after Wed Aug 12nd will be postponed to the
> next regular meeting. Please try to submit your report much earlier.
>
>
> Submitting your report
> --
>
> Full details about reporting to the board are at
>
>   https://www.apache.org/foundation/board/reporting
>
> Please be aware that the board is looking for your personal observations,
> assessment, and ideas, not just raw statistics.
>
> Chairs may use one of several mechanisms to submit or edit their report:
>
>  a) the Apache Reporter Service
> https://reporter.apache.org/
>
>  b) the Whimsy online agenda tool
> https://whimsy.apache.org/board/agenda/2020-08-19/Geode
>
>  c) carefully editing and committing changes to the dated agenda in
> https://svn.apache.org/repos/private/foundation/board
>
>  d) or, if none of the above work, send an email to bo...@apache.org with
> Subject: [REPORT] Geode
>
> If you believe it won't be possible to prepare a report before the
> deadline,
> or if the PMC is aware that the Chair is unavailable, please report that
> and we can reschedule or have someone else report on your behalf.
>
>
> Attending the Board Meeting
> ---
>
> The formal board meeting (usually an online videoconference) will be held
> at
>
>   Wed, 19 Aug 2020 at 12:30 UTC
>
> which in other time zones is
>
>   https://timeanddate.com/s/429w
>
> As always, chairs and ASF members are welcome to attend the board meeting.
> However, in most cases, we will not be using meeting time to discuss
> reports
> unless you specifically request time to speak in person.
>
> During the week prior to the meeting, the directors will read the received
> reports, make comments (if any) within the agenda tool, discuss those
> comments on the board and/or private committee lists, and vote to approve.
>
> If we have comments on a report, we will forward them during the
> review and attempt to complete any associated action items as well.
> This will allow us to be more responsive to project needs and give you
> an opportunity to expand on your report if additional details are
> requested prior to the meeting.
>
> Regular board meetings are held monthly, as scheduled at
>
>   https://svn.apache.org/repos/private/committers/board/calendar.txt
>
>
> Requesting a Board Action
> -
>
> If you want the board to make a decision related to your report, such as
> changing the chair, establishing a new committee, or allocating a budget
> for something related to Geode, you should author a resolution
> for that purpose or ask a director to do so for you.
>
> To make this easy, there are several templates we use for common board
> resolutions. They can be found in
>
>   https://svn.apache.org/repos/private/committers/board/templates
>
> or accessible within the Whimsy online agenda tool
>
>   https://whimsy.apache.org/board/agenda/2020-08-19/Geode
>
> If you do place a resolution before the board and that resolution
> has not been preapproved before the board meeting, you are encouraged
> to attend the meeting in person to address any last-minute questions
> or concerns that might arise.
>
> Thanks,
> The ASF Board
>

Fwd: Geode Board Report due by Wed Aug 12nd - Initial Reminder

[Karen Miller]

Can I get a volunteer to draft our August 2020 report?  Doesn't take much
time. Help is available for the asking if you've never done this community
activity before.  First draft would be super by this Friday, August 7.
Thanks.  Karen

-- Forwarded message -
From: Roy T. Fielding 
Date: Mon, Aug 3, 2020 at 10:52 AM
Subject: Geode Board Report due by Wed Aug 12nd - Initial Reminder
To: Karen Miller 
Cc: 


Hello,

According to our records, you are listed as the chair of Geode,
a committee that is due to submit a report by Wed Aug 12nd
for the next ASF board meeting. This is an initial reminder to prepare a
report for Geode and submit it as described below.

Thank you for being a responsible project chair and helping us maintain
oversight over the Apache Software Foundation. If, for whatever reason,
a full report is not possible by the deadline, please report just that.
It's okay to postpone a report by a month.

Please note that we have initiated a new process for reviewing
and approving these reports, asynchronously, during the week prior
to our scheduled board meeting.

Reports received after Wed Aug 12nd will be postponed to the
next regular meeting. Please try to submit your report much earlier.


Submitting your report
--

Full details about reporting to the board are at

  https://www.apache.org/foundation/board/reporting

Please be aware that the board is looking for your personal observations,
assessment, and ideas, not just raw statistics.

Chairs may use one of several mechanisms to submit or edit their report:

 a) the Apache Reporter Service
https://reporter.apache.org/

 b) the Whimsy online agenda tool
https://whimsy.apache.org/board/agenda/2020-08-19/Geode

 c) carefully editing and committing changes to the dated agenda in
https://svn.apache.org/repos/private/foundation/board

 d) or, if none of the above work, send an email to bo...@apache.org with
Subject: [REPORT] Geode

If you believe it won't be possible to prepare a report before the deadline,
or if the PMC is aware that the Chair is unavailable, please report that
and we can reschedule or have someone else report on your behalf.


Attending the Board Meeting
---

The formal board meeting (usually an online videoconference) will be held at

  Wed, 19 Aug 2020 at 12:30 UTC

which in other time zones is

  https://timeanddate.com/s/429w

As always, chairs and ASF members are welcome to attend the board meeting.
However, in most cases, we will not be using meeting time to discuss reports
unless you specifically request time to speak in person.

During the week prior to the meeting, the directors will read the received
reports, make comments (if any) within the agenda tool, discuss those
comments on the board and/or private committee lists, and vote to approve.

If we have comments on a report, we will forward them during the
review and attempt to complete any associated action items as well.
This will allow us to be more responsive to project needs and give you
an opportunity to expand on your report if additional details are
requested prior to the meeting.

Regular board meetings are held monthly, as scheduled at

  https://svn.apache.org/repos/private/committers/board/calendar.txt


Requesting a Board Action
-

If you want the board to make a decision related to your report, such as
changing the chair, establishing a new committee, or allocating a budget
for something related to Geode, you should author a resolution
for that purpose or ask a director to do so for you.

To make this easy, there are several templates we use for common board
resolutions. They can be found in

  https://svn.apache.org/repos/private/committers/board/templates

or accessible within the Whimsy online agenda tool

  https://whimsy.apache.org/board/agenda/2020-08-19/Geode

If you do place a resolution before the board and that resolution
has not been preapproved before the board meeting, you are encouraged
to attend the meeting in person to address any last-minute questions
or concerns that might arise.

Thanks,
The ASF Board

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

[Karen Miller]

+1 for including this documentation 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
> > 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 Melchior  wrote:
> > > More documentation is good!
> > >
> > > +1
> > > 
> > > From: Jinmei Liao 
> > > Sent: May 19, 2020 14:26
> > > To: geode 
> > > Subject: [PROPOSAL] Bring GEODE-8100 to support branches
> > >
> > > This is to update documentation to better explain the Cluster
> management
> > > service and various geode/system properties that control the behavior
> of
> > > it. It also provides more usage examples in the documentation. There
> is no
> > > product code change in this, but tt would be helpful to the users who
> would
> > > like to understand Cluster management service more.
> > >
> > > --
> > > Cheers
> > >
> > > Jinmei
> > >
> >
>

Our May 2020 report to the board

[Karen Miller]

Apache Geode developers, please thank Dave Barnes for putting together
the May 2020 board report that I filed today.  Here is the contents of the
report:

## 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
architectures.

## Issues:
296 issues opened in JIRA, past quarter (-16% decrease) 226 issues closed in
JIRA, past quarter (-26% decrease)

Given the worldwide impact of the Covid-19 pandemic disruption to our
community's work routines, we feel these figures, though lower than those of
the previous reporting period, reveal an engaged and productive development
community.

## Membership Data:
Apache Geode was founded 2016-11-15 (3 years ago)
There are currently 109 committers and 54 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- Alexander Murmann was added to the PMC on 2020-03-26
- Joris Melchior was added to the PMC on 2020-03-22
- Mark Hanson was added to the PMC on 2020-03-26
- Joris Melchior was added as committer on 2020-03-19
- Mario Kevo was added as committer on 2020-03-23

## Project Activity:
- version 1.12.0 was released on 2020-03-31 This release included improvements
  to the management REST API, .NET and C++ native clients, client/server
  security, and error recovery.
- version 1.13 release is under way

## Community Health:
The Apache Geode dev and issues mailing lists both experienced upticks in
discussion traffic, up 15% and 44%, respectively, in Q1.

The number of JIRA tickets opened and closed remained robust, though down 16%
and 26%, respectively, from the previous quarter. Points of emphasis included
error recovery improvements, API extensions, and compatibility to accommodate
containers such as Kubernetes and BOSH.

In February, community member Jason Huynh posted an article entitled "Apache
Geode as a remote Gradle Build Cache"
(https://jasonhuynh.blogspot.com/2020/02/apache-geode-as-remote-gradle-build.html).
In March, Jason posted "Publishing Apache Geode Metrics to Wavefront"
(https://medium.com/@huynhja/
publishing-apache-geode-metrics-to-wavefront-6e9a6cf5992b) along with an
accompanying video (https://youtu.be/BDZh-FLkDTg).

Community member Juan Jose Ramos posted an article in March entitled "Geode
Distributed Sequences"
(https://medium.com/@jujoramos/geode-distributed-sequences-12626251d5e3), and
another in April, "The Command Region Pattern"
(https://medium.com/@jujoramos/the-command-region-pattern-14bc49594eca).

In April, community member Barry Oglesby published "Remove Unused PdxTypes
from an Apache Geode Distributed System"
(https://medium.com/@boglesby_2508/remove-unused-pdxtypes-from-an-apache-geode-distributed-system-5a4f0e199e34).

Re: Switching default branch in .net core repo

[Karen Miller]

+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
> > (gitflow-ish).
> >
> > +1
> >
> > Anthony
> >
> >
> > > On Apr 23, 2020, at 7:35 AM, Blake Bender  wrote:
> > >
> > > Good morning,
> > >
> > > We created a repo yesterday for the .net core client work, and the
> > default
> > > branch out of the gate is set to master.  I'd like to switch it to
> > develop,
> > > like the rest of the Geode repos, which apparently requires a quick
> > > heads-up and a couple of +1s to go ahead with.  So... is everyone okay
> > with
> > > this change?
> > >
> > > Thanks,
> > >
> > > Blake
> >
> >
>

Feb 2020 Apache Geode quarterly report

[Karen Miller]

I've submitted our quarterly report.  The ASF requests that we no longer
email
the board with the report as part of the process.  So, this email is a copy
of the
report that I submitted.  Karen

## Description:
Apache Geode is a data management platform that provides a database-like
consistency model, reliable transaction processing and a shared-nothing
architecture to maintain very low latency performance with high concurrency
processing.

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Geode was founded 2016-11-15 (3 years ago)
There are currently 107 committers and 52 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Bill Burcham on 2019-09-08.
- Aaron Lindsey was added as committer on 2019-12-16
- Benjamin Ross was added as committer on 2019-12-06
- Donal Evans was added as committer on 2019-11-22

## Project Activity:
1.11.0 was released on 2019-12-31. We are well on our way to a 1.12.0
release.
Two areas of focus on our code base have been toward fixing tests marked as
flaky, and introducing the ability to specify (authorize) access to data
when
querying a dataset (see
https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security
).

## Community Health:
The community is actively contributing to the Apache Geode code base. In the
past quarter:
- 393 emails sent to dev@geode.apache.org
- 315 issues opened in JIRA
- 288 issues closed in JIRA
- 379 PRs opened on GitHub
- 396 PRs closed on GitHub
- 563 commits by 57 code contributors

quarterly board report: what should we add?

[Karen Miller]

Geode Developers,
Here's the start of a board report that is due tomorrow (Feb 12).
I feel that the Project Activity or Community Health section could use more
information
about what we're working on. There are so many developers working on so many
exciting areas that I'm not sure which we all feel would be best to include
in the report.
Are there any blogs or conference activity that I might include in the
report?
Thanks.  Karen

Draft of the report:

## 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
architectures.

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Geode was founded 2016-11-15 (3 years ago)
There are currently 107 committers and 52 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- No new PMC members. Last addition was Bill Burcham on 2019-09-08.
- Aaron Lindsey was added as committer on 2019-12-16
- Benjamin Ross was added as committer on 2019-12-06
- Donal Evans was added as committer on 2019-11-22

## Project Activity:
1.11.0 was released on 2019-12-31.
We are well on our way to a 1.12.0 release.

## Community Health:
The community is actively contributing to the Apache Geode code base. In the
past quarter:
- 315 issues opened in JIRA
- 288 issues closed in JIRA
- 563 commits by 57 code contributors

Re: [VOTE] Apache Geode 1.11.0.RC4

[Karen Miller]

+1
My vote is only based on running the examples with RC 4.  I didn't check
anything else.

On Mon, Dec 23, 2019 at 3:09 PM Aaron Lindsey 
wrote:

> The release notes section on the wiki just says "tbd". Also, I cannot find
> Mark’s public key in any of the public PGP key servers (such as
> https://keyserver.ubuntu.com), but I did verify that the signatures in
> the source and binary distributions match the key that is listed in the
> geode KEYS file.
>
> Other than those 2 things, everything else looks good. I checked the
> following:
>
> - Built from source and ran unit tests
> - Used GFSH to create a locator and server and do some puts/gets
> - Checked version in GFSH
> - Built and ran all of the examples
> - Verified SHAs and signatures
>
> Aaron
>
> > On Dec 23, 2019, at 2:59 PM, Michael Oleske  wrote:
> >
> > +1
> >
> > - ran `./gradlew build` on Geode 1.11.0.RC4 on Mac and Windows
> > - built Geode Native 1.11.0.RC4 against Geode 1.11.0.RC4 on Mac and
> Windows
> > - ran `ctest -L STABLE -C Debug` on cppcache/integration-test on Mac and
> > Windows
> > - ran `ctest` on cppcache/integration/test on Mac and Windows (Did not
> test
> > IPV6 support as I don't generally use that)
> > - ran `ctest -L STABLE -C Debug` on clicache/integration-test on Windows
> > - ran XUnit tests in Rider on clicache/integrations-test2 on Windows
> > - installed and built Geode Native 1.11.0.RC4 examples on Windows
> >
> > -michael
> >
> >
> > On Fri, Dec 20, 2019 at 2:49 PM Mark Hanson  wrote:
> >
> >> Given it is the holidays, perhaps more time is in order. I am bumping
> the
> >> voting deadline to Friday, December 27th, 2019.
> >>
> >> Thanks,
> >> Mark
> >>
> >>
> >>
> >>> On Dec 20, 2019, at 2:46 PM, Mark Hanson  wrote:
> >>>
> >>> Subject: [VOTE] Apache Geode 1.11.0.RC4
> >>> Hello Geode Dev Community,
> >>>
> >>> This is a release candidate for Apache Geode version 1.11.0.RC4.
> >>> Thanks to all the community members for their contributions to this
> >> release!
> >>>
> >>> Please do a review and give your feedback, including the checks you
> >> performed.
> >>>
> >>> Voting deadline:
> >>> 3PM PST Friday, December 27 2019.
> >>>
> >>> Please note that we are voting upon the source tag:
> >>> rel/v1.11.0.RC4
> >>>
> >>> Release notes:
> >>>
> >>
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.11.0
> >>>
> >>> Source and binary distributions:
> >>> https://dist.apache.org/repos/dist/dev/geode/1.11.0.RC4/
> >>>
> >>> Maven staging repo:
> >>> https://repository.apache.org/content/repositories/orgapachegeode-1064
> >>>
> >>> GitHub:
> >>> https://github.com/apache/geode/tree/rel/v1.11.0.RC4
> >>> https://github.com/apache/geode-examples/tree/rel/v1.11.0.RC4
> >>> https://github.com/apache/geode-native/tree/rel/v1.11.0.RC4
> >>>
> >>> Pipelines:
> >>>
> >>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-11-0-main
> >>>
> >>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-11-0-rc
> >>>
> >>> Geode's KEYS file containing PGP keys we use to sign the release:
> >>> https://github.com/apache/geode/blob/develop/KEYS
> >>>
> >>> Command to run geode-examples:
> >>> ./gradlew -PgeodeReleaseUrl=
> >> https://dist.apache.org/repos/dist/dev/geode/1.11.0.RC4
> >> -PgeodeRepositoryUrl=
> >> https://repository.apache.org/content/repositories/orgapachegeode-1064
> >> build runAll
> >>>
> >>> Regards
> >>> Mark Hanson
> >>>
> >>
> >>
>
>

[REPORT] Apache Geode - November 2019

[Karen Miller]

## 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
architectures.

## Issues:
There are no issues requiring board attention at this time.

## Membership Data:
Apache Geode was founded 2016-11-15 (3 years ago) There are currently 104
committers and 52 PMC members in this project. The Committer-to-PMC ratio is
2:1.

Community changes, past quarter:
- Bill Burcham was added to the PMC on 2019-09-08
- Mario Ivanac was added to the PMC on 2019-09-08
- Bill Burcham was added as committer on 2019-09-09
- Mario Ivanac was added as committer on 2019-09-09

## Project Activity:
- Released Apache Geode 1.10.0 on 2019-09-26.
- Released Apache Geode 1.9.1 on 2019-09-06.
- Released Apache Geode 1.9.2 on 2019-10-29.

## Community Health:
The community is actively contributing to the Apache Geode code base. In the
past quarter:
- 61 code contributors
- 347 issues opened in JIRA
- 275 issues closed in JIRA
- 434 PRs opened on GitHub
- 426 PRs closed on GitHub

Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in
Austin, Texas, with 500 attendees at the 12 sessions.

Re: Quick turnaround needed, feedback on this DRAFT Nov board report

[Karen Miller]

Thanks Owen.  I have revised our report, and you'll see the revised version
as I email it to the Apache board.


On Wed, Nov 13, 2019 at 11:25 AM Owen Nichols  wrote:

> We also released 1.9.2 on 2019-10-28
>
> > On Nov 13, 2019, at 9:51 AM, Dave Barnes  wrote:
> >
> > +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 provides real-time, consistent
> access to
> >> data-intensive applications throughout widely distributed cloud
> >> architectures.
> >>
> >> ## Issues:
> >> There are no issues requiring board attention at this time.
> >>
> >> ## Membership Data:
> >> Apache Geode was founded 2016-11-15 (3 years ago)
> >> There are currently 104 committers and 52 PMC members in this project.
> >> The Committer-to-PMC ratio is 2:1.
> >>
> >> Community changes, past quarter:
> >> - Bill Burcham was added to the PMC on 2019-09-08
> >> - Mario Ivanac was added to the PMC on 2019-09-08
> >> - Bill Burcham was added as committer on 2019-09-09
> >> - Mario Ivanac was added as committer on 2019-09-09
> >>
> >> ## Project Activity:
> >> - Released Apache Geode 1.10.0 on 2019-09-26.
> >> - Released Apache Geode 1.9.1 on 2019-09-06.
> >>
> >>
> >> ## Community Health:
> >> The community is actively contributing to the Apache Geode code base. In
> >> the
> >> past quarter:
> >> - 61 code contributors
> >> - 347 issues opened in JIRA
> >> - 275 issues closed in JIRA
> >> - 434 PRs opened on GitHub
> >> - 426 PRs closed on GitHub
> >>
> >> Enjoyed great attendance at the Apache Geode Summit held October 7,
> 2019,
> >> in
> >> Austin, Texas.
> >>
>
>

Apache Geode Nov 2019 board report submitted

[Karen Miller]

Here's the text of the board report I submitted (November 2019).  Thank you
everyone for the quick feedback.

## 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 architectures.

## Issues:
There are no issues requiring board attention at this time.

## Membership Data:
Apache Geode was founded 2016-11-15 (3 years ago)
There are currently 104 committers and 52 PMC members in this project.
The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
- Bill Burcham was added to the PMC on 2019-09-08
- Mario Ivanac was added to the PMC on 2019-09-08
- Bill Burcham was added as committer on 2019-09-09
- Mario Ivanac was added as committer on 2019-09-09

## Project Activity:
- Released Apache Geode 1.10.0 on 2019-09-26.
- Released Apache Geode 1.9.1 on 2019-09-06.


## Community Health:
The community is actively contributing to the Apache Geode code base. In the
past quarter:
- 61 code contributors
- 347 issues opened in JIRA
- 275 issues closed in JIRA
- 434 PRs opened on GitHub
- 426 PRs closed on GitHub

Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in
Austin, Texas, with 500 attendees at the 12 sessions.

Quick turnaround needed, feedback on this DRAFT Nov board report

[Karen Miller]

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 provides real-time, consistent access to
data-intensive applications throughout widely distributed cloud
architectures.

## Issues:
There are no issues requiring board attention at this time.

## Membership Data:
Apache Geode was founded 2016-11-15 (3 years ago)
There are currently 104 committers and 52 PMC members in this project.
The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
- Bill Burcham was added to the PMC on 2019-09-08
- Mario Ivanac was added to the PMC on 2019-09-08
- Bill Burcham was added as committer on 2019-09-09
- Mario Ivanac was added as committer on 2019-09-09

## Project Activity:
- Released Apache Geode 1.10.0 on 2019-09-26.
- Released Apache Geode 1.9.1 on 2019-09-06.


## Community Health:
The community is actively contributing to the Apache Geode code base. In the
past quarter:
- 61 code contributors
- 347 issues opened in JIRA
- 275 issues closed in JIRA
- 434 PRs opened on GitHub
- 426 PRs closed on GitHub

Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in
Austin, Texas.

access to concourse.apachegeode-ci.info

[Karen Miller]

May I have access to concourse.apachegeode-ci.info, so that I can see
details of
of my jobs, and re-trigger failed PR jobs?
Thanks.  Karen

Re: [DISCUSS] Blocking merge button in PR

[Karen Miller]

I have (more than once) committed docs changes for typo fixes without
review.  I generally label the commits
with a bold "Commit then Review" message.  But, I am bringing this up as I
have purposely not followed what
looks to be a positively-received proposed policy, since I have not gotten
reviews. If all feel that we need a
rule for everyone to follow (instead of a guideline that PRs shall have at
least 1 review), I will follow the rule,
but I'm a -0 on the process. I get it, and I understand its purpose and
intent, but I personally prefer to trust that each
comitter takes personal responsibility for the code they commit WRT waiting
for tests and/or obtaining reviews.
Karen


On Mon, Oct 21, 2019 at 6:24 AM Joris Melchior  wrote:

> +1 to the revised approach. I think requiring at least one review is
> important. More eyes make for better code.
>
> Cheers, Joris.
>
> On Mon, Oct 21, 2019 at 8:11 AM Ju@N  wrote:
>
> > +10 to Naba's proposal, it seems the right thing to do and will help us
> to
> > prevent accidentally breaking *develop* while keeping focus on people
> > instead of processes.
> > I'd add, however, that the *Merge Pull Request* button should remain
> > disabled until *all CIs have finished*, and only enable it once the
> *Build,
> > Unit, Stress Tests and LGTM are green *(that is, force the committer to
> > wait at least until all CIs are done)*. *I also agree in that that we
> > should require *at least one* official approval.
> > Cheers.
> >
>
>
> --
> *Joris Melchior *
> CF Engineering
> Pivotal Toronto
> 416 877 5427
>
> “Programs must be written for people to read, and only incidentally for
> machines to execute.” – *Hal Abelson*
> 
>

Re: [DISCUSS] Time to cut Geode 1.10.0?

[Karen Miller]

Alexander, can you point me at the policy decision for the "critical issue"
rule you mention? I always though it was up
to the release manager.

I want GEODE-7013 fixes in because it is the right thing to do.  Our gfsh
help/hint wasn't working the way we say that it did.
With the fix, it does.  I want either the documentation to match the code,
or I want the code to match the documentation.
The fix in GEODE-7013 changes the code to match the existing documentation,
so we don't have to change the documentation
(which would have needed to be cherry-picked into our 1.10 release branch).


On Tue, Jul 30, 2019 at 11:47 AM Owen Nichols  wrote:

> Our "critical issue” rule has the effect that the bar to commit to develop
> is “low”, but the bar to cherry-pick to support branch is “very high”.
>
> Contributors could plan around this disparity more easily if any of the
> following were true:
> - releases were more frequent
> - planned cut date of release branch was announced in advance (rather than
> retroactively)
> - a process existed for making exceptions to the “critical issue” rule
>
> I agree that the proposed SHA looks like a relatively stable branchpoint
> (coming near the end of a nice period of solid green in the pipeline), and
> I acknowledge that fair warning was given a week ago that a branch was
> “coming soon”, but I wonder if there is anything we can do to make the
> rules for what gets in a release and what doesn’t feel a little less
> arbitrary?
>
> -Owen
>
>
> > On Jul 30, 2019, at 11:16 AM, Alexander Murmann 
> wrote:
> >
> > Dick, thank you for stepping up!
> >
> > I think it's great to cut the branch sooner rather than later. There
> > already is GEODE-7012 which introduces a distributed deadlock during
> > startup. That seems like a critical issue to fix. That should be able to
> > happen after we cut the branch though.
> >
> > Karen, I wonder if that could be merged after the branch got cut, but
> also
> > wonder if that fits our "critical issue" rule for being merged after the
> > branch has been cut or hold up the release. This has been broken since a
> > very long time. Thoughts?
> >
> > On Tue, Jul 30, 2019 at 10:51 AM Karen Miller 
> wrote:
> >
> >> I'd like to see the changes from
> >> https://issues.apache.org/jira/browse/GEODE-7013 included in the Geode
> >> 1.10
> >> release. GEODE-7013's changes restore gfsh help/hint behavior that was
> lost
> >> during a refactor in the earliest
> >> releases of Geode.  The commit occurred after SHA1
> >> dc6890107a2651d8ba1450e8db8a1c39d712fdc7.
> >> Thanks.  Karen
> >>
> >>
> >> On Tue, Jul 30, 2019 at 10:39 AM Dick Cavender 
> wrote:
> >>
> >>> I'll take on the Release Manager role for Geode 1.10 with the 1.9.0
> >> release
> >>> manager's help (Owen:).
> >>>
> >>> I'd like to propose cutting the release/1.10 branch off develop sha:
> >>> dc6890107a2651d8ba1450e8db8a1c39d712fdc7
> >>>
> >>> aka: 1.10.0-SNAPSHOT.476
> >>>
> >>> Please speak up and discuss. We'll then start taking considerations for
> >>> additional changes for 1.1.0 after we get the branch and pipeline in
> >> place.
> >>>
> >>> -Dick
> >>>
> >>>
> >>>
> >>>
> >>> On Mon, Jul 29, 2019 at 4:08 PM Alexander Murmann  >
> >>> wrote:
> >>>
> >>>> Thanks for calling this out Ernie!
> >>>>
> >>>> It might be a good idea to cut the release and at the same time keep
> >>>> looking for urgent issues that need to be resolved and merged. Once
> the
> >>>> branch is cut, we release likelihood of new issues being introduced.
> >>>>
> >>>> Does anyone know of any other issues, we'd want to make sure get
> >>> addressed
> >>>> before we ship?
> >>>>
> >>>> On Mon, Jul 29, 2019 at 3:36 PM Ernest Burghardt <
> >> eburgha...@pivotal.io>
> >>>> wrote:
> >>>>
> >>>>> There is a PR #3844 <https://github.com/apache/geode/pull/3844> up
> >> to
> >>>>> address GEODE-7012 <https://issues.apache.org/jira/browse/GEODE-7012
> >>>
> >>> I
> >>>>> think this should be in the next release...
> >>>>>
> >>>>> EB
> >>>>>
> >>>>> On Fri, Jul 26, 2019 at 4:07 PM Alexander Murmann <
> >>

Re: [DISCUSS] Time to cut Geode 1.10.0?

[Karen Miller]

I'd like to see the changes from
https://issues.apache.org/jira/browse/GEODE-7013 included in the Geode 1.10
release. GEODE-7013's changes restore gfsh help/hint behavior that was lost
during a refactor in the earliest
releases of Geode.  The commit occurred after SHA1
dc6890107a2651d8ba1450e8db8a1c39d712fdc7.
Thanks.  Karen


On Tue, Jul 30, 2019 at 10:39 AM Dick Cavender  wrote:

> I'll take on the Release Manager role for Geode 1.10 with the 1.9.0 release
> manager's help (Owen:).
>
> I'd like to propose cutting the release/1.10 branch off develop sha:
> dc6890107a2651d8ba1450e8db8a1c39d712fdc7
>
> aka: 1.10.0-SNAPSHOT.476
>
> Please speak up and discuss. We'll then start taking considerations for
> additional changes for 1.1.0 after we get the branch and pipeline in place.
>
> -Dick
>
>
>
>
> On Mon, Jul 29, 2019 at 4:08 PM Alexander Murmann 
> wrote:
>
> > Thanks for calling this out Ernie!
> >
> > It might be a good idea to cut the release and at the same time keep
> > looking for urgent issues that need to be resolved and merged. Once the
> > branch is cut, we release likelihood of new issues being introduced.
> >
> > Does anyone know of any other issues, we'd want to make sure get
> addressed
> > before we ship?
> >
> > On Mon, Jul 29, 2019 at 3:36 PM Ernest Burghardt 
> > wrote:
> >
> > > There is a PR #3844  up to
> > > address GEODE-7012 
> I
> > > think this should be in the next release...
> > >
> > > EB
> > >
> > > On Fri, Jul 26, 2019 at 4:07 PM Alexander Murmann  >
> > > wrote:
> > >
> > > > *Cutting the release*
> > > > Do we have any volunteers to take over the release manager role?
> > > >
> > > > *Re: Udo's concerns*
> > > > While I believe that iterations of this particular work have been
> > > discussed
> > > > on the mailing list as far back as March 2018, I do think that we
> > should
> > > > take Udo's response as an indicator that something with our larger
> > > proposal
> > > > process needs to be improved. We used to have synchronous Geode club
> > > house
> > > > sessions. For future discussions and for proposals in particular, I
> > think
> > > > it would be great to supplement our asynchronous mailing list
> > > communication
> > > > with a synchronous video chat discussions by the community.
> > > >
> > > > On Fri, Jul 26, 2019 at 4:02 PM Dan Smith  wrote:
> > > >
> > > > > +1 for cutting a 1.10.0 release branch.
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Jul 26, 2019 at 3:55 PM Nabarun Nag 
> wrote:
> > > > >
> > > > > > Hi,
> > > > > > I believe the original authors of the feature has done their due
> > > > > diligence
> > > > > > and followed all steps, we can get this feature in under the
> > > > Experimental
> > > > > > flag and let the community improve on it, if there is anything
> else
> > > > that
> > > > > > needs to be done.
> > > > > >
> > > > > > We have done this before for Lucene re-index feature, where we
> > > involved
> > > > > the
> > > > > > entire community in its development, phase by phase. The wiki is
> up
> > > and
> > > > > > running, if someone has any concerns can raise it as a JIRA or
> > > comment
> > > > in
> > > > > > the wiki and the community as a whole can decide if it is a valid
> > > > > > concern or not and act upon it.
> > > > > >
> > > > > > Regards
> > > > > > Nabarun Nag
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Jul 26, 2019 at 3:40 PM Udo Kohlmeyer 
> > > wrote:
> > > > > >
> > > > > > > @Alexander + @Jared,
> > > > > > >
> > > > > > > So maybe that was my misunderstanding on the RFC (not being
> > > optional
> > > > on
> > > > > > > new feature work). Given that this is a new feature, there is
> > > > > > > significant risk to getting it "wrong".
> > > > > > >
> > > > > > > I was expecting more discussion around this. I have some
> > objections
> > > > to
> > > > > > > the current approach/design. Given that my day job does not
> allow
> > > me
> > > > to
> > > > > > > respond in a timely manner, I would have not been able to get
> all
> > > my
> > > > > > > concerns raised. In addition, throwing something onto the wiki,
> > and
> > > > > then
> > > > > > > a few weeks before we'd like to cut a version raising a
> > discussion
> > > > > > > thread on work that has been going on for months already does
> not
> > > > help
> > > > > > > with the community being able to read, digest, think, reason
> and
> > > > > respond
> > > > > > > BEFORE it is released.
> > > > > > >
> > > > > > > I know `@Experimental` is non-binding on API's or usage, BUT I
> > > prefer
> > > > > > > some of the ground work to have been discussed, API's validated
> > > > BEFORE
> > > > > > > it is released into the wild. I mean this is a PUBLIC API, so
> > we'd
> > > > > > > prefer to get it more correct than the previous one.
> > > > > > >
> > > > > > > Maybe it is just me, taking it too serious... Where I prefer
> not
> > > > > release
> > > > > > > 

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

[Karen Miller]

Geode devs,  I think that my merges of commits for GEODE-5071 and
GEODE-5242 really
belong in Geode 1.7.  They just missed making it in before the release
branch was cut.  I'm going to
cherry pick them into the 1.7 release branch.  If anyone disagrees with
this, let's discuss why, and we
can always revert the commits.  Thanks!


On Mon, May 21, 2018 at 4:39 PM, Nabarun Nag  wrote:

> Hello Geode dev community,
>
> We have created a release branch for Apache Geode 1.7.0 - "release/1.7.0"
>
> Please do review and raise any issue with the release branch.
>
> If no concerns are raised we will start with voting for release candidate
> within a week.
>
> Regards
> Nabarun Nag
>

Re: Geode 1.6.0 release branch has been created

[Karen Miller]

Mike,
  I've just cherry picked commit SHA1
ac7db5b2950af134233c976b3f63f3e48e8d3fb9 onto the release/1.6.0 branch.
This commit updates the documentation for GEODE-4384. This JIRA ticket
already had its code committed prior to
creation of the release branch, but the JIRA ticket was still unresolved
due to the missing documentation.

On Thu, Apr 12, 2018 at 3:03 PM, Michael Stolz  wrote:

> Can someone please create a concourse pipeline for this release?
>
>
> --
> Mike Stolz
>

Re: [VOTE] Apache Geode release - v1.2.1 RC4

[Karen Miller]

+1

Ran the 1.2.1 RC4 partitioned geode-example against Geode 1.2.1 RC4.  So,
built Geode from
source, built one of the examples, ran gfsh commands to start locator and
servers as well as ran
a query, and did some puts and gets via API.

Also checked that the manual builds and contains 1.2.1 changes.


On Mon, Sep 18, 2017 at 3:10 PM, William Markito Oliveira <
mark...@apache.org> wrote:

> +1
>
> Checked:
> - Basic operations from command line
> - Checksums match
> - Release build green (blue actually)  (
> https://builds.apache.org/job/Geode-release/lastBuild/)
>
>
>
> On Mon, Sep 18, 2017 at 3:57 PM, Dan Smith  wrote:
>
> > +1
> >
> > The jenkins release build was green and release check passed as well -
> > https://github.com/upthewaterspout/geode-release-check
> >
> > -Dan
> >
> > On Sat, Sep 16, 2017 at 8:01 AM, Anthony Baker 
> wrote:
> >
> > > This is the fourth release candidate for Apache Geode, version 1.2.1.
> > > Thanks to all the community members for their contributions to this
> > > release!
> > >
> > > *** Please download, test and vote by Wednesday, September 20, 0800 hrs
> > > US Pacific. ***
> > >
> > > It fixes the following issues:
> > >  https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12318420=12341124
> > >
> > > Note that we are voting upon the source tags:  rel/v1.2.1.RC4
> > >  https://github.com/apache/geode/tree/rel/v1.2.1.RC4
> > >  https://github.com/apache/geode-examples/tree/rel/v1.2.1.RC4
> > >
> > > Commit ID:
> > >  0b881b515eb1dcea974f0f5c1b40da03d42af9cf (geode)
> > >  5d034de588a43cdefb8fbb3a6259579785768340 (geode-examples)
> > >
> > > Source and binary files:
> > >  https://dist.apache.org/repos/dist/dev/geode/1.2.1.RC4
> > >
> > > Maven staging repo:
> > >  https://repository.apache.org/content/repositories/
> orgapachegeode-1027
> > >
> > > Geode's KEYS file containing PGP keys we use to sign the release:
> > >  https://github.com/apache/geode/blob/develop/KEYS
> > >
> > > pub  4096R/C72CFB64 2015-10-01
> > >  Fingerprint=948E 8234 14BE 693A 7F74  ABBE 19DB CAEE C72C FB64
> > >
> > >
> > > Anthony
> > >
> >
>

Re: [VOTE] Apache Geode release - v1.2.1 RC2

[Karen Miller]

A guarded +1 based on limited testing of the RC:

Built the Geode RC from source.
Built and ran the RC (partitioned) geode-example against the Geode RC, which
means I ran gfsh, started a locator and some servers with gfsh, did some
puts and gets via
the API, and ran a query and other commands via gfsh.

The manual builds and looks good in the RC.


On Fri, Sep 1, 2017 at 6:39 AM, Anthony Baker  wrote:

> This is the second release candidate for Apache Geode, version 1.2.1.
> Thanks to all the community members for their contributions to this
> release!
>
> *** Please download, test and vote by Thursday, September 7, 0800 hrs
> US Pacific. ***
>
> It fixes the following issues:
>   https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318420=12341124
>
> Note that we are voting upon the source tags:  rel/v1.2.1.RC2
>   https://git-wip-us.apache.org/repos/asf?p=geode.git;a=commit;h=
> afcd9817bc28069453861c935f428e89b8c7ff5d
>   https://git-wip-us.apache.org/repos/asf?p=geode-examples.git;a=commit;h=
> 5d034de588a43cdefb8fbb3a6259579785768340
>
> Commit ID:
>   afcd9817bc28069453861c935f428e89b8c7ff5d (geode)
>   5d034de588a43cdefb8fbb3a6259579785768340 (geode-examples)
>
> Source and binary files:
>   https://dist.apache.org/repos/dist/dev/geode/1.2.1.RC2
>
> Maven staging repo:
>   https://repository.apache.org/content/repositories/orgapachegeode-1022
>
> Geode's KEYS file containing PGP keys we use to sign the release:
>   https://git-wip-us.apache.org/repos/asf?p=geode.git;a=blob_
> plain;f=KEYS;hb=HEAD
>
> pub  4096R/C72CFB64 2015-10-01
>   Fingerprint=948E 8234 14BE 693A 7F74  ABBE 19DB CAEE C72C FB64
>
>
> Anthony
>

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60881/#review180608
---


Ship it!




Ship It!

- Karen Miller


On July 14, 2017, 8:02 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60881/
> ---
> 
> (Updated July 14, 2017, 8:02 p.m.)
> 
> 
> Review request for geode and Jared Stewart.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-3207 Swagger library updates: update user guide
> 
> 
> Diffs
> -
> 
>   geode-docs/rest_apps/setup_config.html.md.erb 
> c557f4f5a92a7331a434d670b99d24928a415e6a 
>   geode-docs/rest_apps/using_swagger.html.md.erb 
> 05f41295057e5c684b7b6403bc3273e33df821c1 
> 
> 
> Diff: https://reviews.apache.org/r/60881/diff/1/
> 
> 
> Testing
> ---
> 
> Compiled manual to verify formatting, executed examples to verify that they 
> work as advertised.
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60873/#review180607
---


Ship it!




Ship It!

- Karen Miller


On July 14, 2017, 5:08 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60873/
> ---
> 
> (Updated July 14, 2017, 5:08 p.m.)
> 
> 
> Review request for geode.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2189 Docs: Update Swagger UI links Added link to OpenAPI specification.
> 
> 
> Diffs
> -
> 
>   geode-docs/rest_apps/using_swagger.html.md.erb 
> 05f41295057e5c684b7b6403bc3273e33df821c1 
> 
> 
> Diff: https://reviews.apache.org/r/60873/diff/1/
> 
> 
> Testing
> ---
> 
> Compiled the user manual, verified that the links connect as they should.
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59923/#review177342
---


Ship it!




Ship It!

- Karen Miller


On June 8, 2017, 5:33 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59923/
> ---
> 
> (Updated June 8, 2017, 5:33 p.m.)
> 
> 
> Review request for geode.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-3029: Tomcat Install Documentation has incorrect required JARs
> 
> 
> Diffs
> -
> 
>   
> geode-docs/tools_modules/http_session_mgmt/tomcat_installing_the_module.html.md.erb
>  b96a2548352e4dc6d945830f67c6c986d873c9f5 
> 
> 
> Diff: https://reviews.apache.org/r/59923/diff/1/
> 
> 
> Testing
> ---
> 
> Successfully built User Guide from source using bookbinder, new text 
> introduced no errors.
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59866/#review177130
---


Ship it!




Ship It!

- Karen Miller


On June 6, 2017, 10:50 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59866/
> ---
> 
> (Updated June 6, 2017, 10:50 p.m.)
> 
> 
> Review request for geode and Galen O'Sullivan.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2555: Region Management docs page refers to the wrong field (id= should 
> be refid=)
> 
> 
> Diffs
> -
> 
>   geode-docs/basic_config/data_regions/managing_data_regions.html.md.erb 
> c93f13a845544bcc3c1d3de4747aa7c18054ab6d 
> 
> 
> Diff: https://reviews.apache.org/r/59866/diff/1/
> 
> 
> Testing
> ---
> 
> Found and corrected 3 occurrences.
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59653/#review176370
---


Ship it!




- Karen Miller


On May 30, 2017, 9:21 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59653/
> ---
> 
> (Updated May 30, 2017, 9:21 p.m.)
> 
> 
> Review request for geode, Joey McAllister, Karen Miller, and Ken Howe.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2420 Warn a user if they try to export too much data. Added gfsh ref 
> docs for --file-size-limit option.
> 
> 
> Diffs
> -
> 
>   geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb 
> ccf95ccf2d8449afeb1dc8381b1c0b5a05c36796 
> 
> 
> Diff: https://reviews.apache.org/r/59653/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

Re: Last call on 1.2.0 (and fixing test failures)

[Karen Miller]

Let's finish GEODE-2913, the documentation for improvements made to the
Lucene integration and include it with the 1.2.0 release!


On Sun, May 14, 2017 at 6:47 PM, Anthony Baker  wrote:

> Hi everyone,
>
> Our last release was v1.1.1 in March.  We have made a lot of great
> progress on the develop branch with over 250 issues fixed.  It would be
> great to get those changes into a release.  What’s left before we are ready
> to release 1.2.0?
>
> Note that we need a clean test run before releasing (except for “flaky"
> tests).  We haven’t had one of those in awhile [1].
>
> Anthony
>
> [1] https://builds.apache.org/job/Geode-nightly/
> lastCompletedBuild/testReport/
>
>

a new example needs your review

[Karen Miller]

Calling all Geode devs:

I've put together a new, and quite basic example that attempts to
demonstrate
what partitioning does.  Please review and see the PR at
  https://github.com/apache/geode-examples/pull/3

When reviewing this example, please keep in mind that my goal is to
tightly focus on partitioning, so it really doesn't do too much.  Other
(future)
examples will demonstrate other and more complex aspects of using or
developing
with Geode.

Here's the comment I placed in the PR, as you'd want to see this in order to
run the example yourself:

  This example intends to demonstrate what partitioning does (distributes
> entries across buckets, and therefore across servers). It also illustrates
> what goes wrong when a bad hashcode is used, such that all entries end up
> in the same bucket.
> Running the example is explained in the partitioned/README.md file. It
> assumes that the reader has already read and followed the minimal
> directions in the README.md file at the root of the geode-examples repo.

Re: for discussion: separate website into its own repo

[Karen Miller]

Seems like everyone is in favor of the separate repo.  I'll request one
early next week.
I created https://issues.apache.org/jira/browse/GEODE-2507 to handle the
first parts
of the task of getting the new repo up and running.


On Fri, Feb 17, 2017 at 9:25 AM, Kirk Lund <kl...@apache.org> wrote:

> +1
>
> On Thu, Feb 16, 2017 at 4:45 PM, Joey McAllister <jmcallis...@pivotal.io>
> wrote:
>
> > +1 to Karen's suggestion of moving the website to its own repo.
> >
> > +1 to Dan's suggestion scripting the website build/publishing with a CI
> > system based on commits.
> >
> > On Thu, Feb 16, 2017 at 4:38 PM Dan Smith <dsm...@pivotal.io> wrote:
> >
> > > +1
> > >
> > > I think the current setup is confusing, because the website is supposed
> > to
> > > include docs that are generated from the last release, but the site
> > > instructions say the site should be generated from develop. A separate
> > repo
> > > with a single branch will probably reduce confusion.
> > >
> > > We also need to script the website building and publishing, and ideally
> > > have the publishing done by a CI system based on commits. It looks like
> > > some other projects are talking about doing this with jenkins jenkins -
> > see
> > > INFRA-10722 for example.
> > >
> > > -Dan
> > >
> > > On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller <kmil...@apache.org>
> > wrote:
> > >
> > > > I think that the website content that is currently in
> geode/geode-site
> > > > ought to be moved to its own repository.  The driving reason for this
> > is
> > > > that changes to the website occur on a different schedule than code
> > > > releases.  We often want to add a new committer's name or a new
> > > > event, and these items are not associated with sw releases. A new
> > website
> > > > release that comes from the develop branch may have commits that
> > > > should not yet be made public.
> > > >
> > > > Are there downsides to separating the website content into its own
> > repo?
> > > >
> > >
> >
>

for discussion: separate website into its own repo

[Karen Miller]

I think that the website content that is currently in geode/geode-site
ought to be moved to its own repository.  The driving reason for this is
that changes to the website occur on a different schedule than code
releases.  We often want to add a new committer's name or a new
event, and these items are not associated with sw releases. A new website
release that comes from the develop branch may have commits that
should not yet be made public.

Are there downsides to separating the website content into its own repo?

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

[Karen Miller]

> On Feb. 14, 2017, 12:48 a.m., Hitesh Khamesra wrote:
> > geode-docs/developing/data_serialization/auto_serialization.html.md.erb, 
> > line 133
> > <https://reviews.apache.org/r/56626/diff/1/?file=1632587#file1632587line133>
> >
> > I thought this info is good to keep; Do we have similar info somewhere 
> > else?

The subsections are still in the manual, and the links to them are in the 
navigation panel.  I only removed the missplaced links within this section.


- Karen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56626/#review165417
-------


On Feb. 14, 2017, 12:22 a.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56626/
> ---
> 
> (Updated Feb. 14, 2017, 12:22 a.m.)
> 
> 
> Review request for geode, Bruce Schuchardt, Dave Barnes, Hitesh Khamesra, 
> Joey McAllister, and Udo Kohlmeyer.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2479 Remove docs reference to gemstone.com package
> 
> 
> Diffs
> -
> 
>   geode-docs/developing/data_serialization/auto_serialization.html.md.erb 
> cdb63a8fb5f5c5bcf7330bc2d611c3e126618b51 
> 
> Diff: https://reviews.apache.org/r/56626/diff/
> 
> 
> Testing
> ---
> 
> Gradle rat check passes.  I did not build Geode.  I did build the manual, and 
> no errors occur for a manual build.
> 
> Devs with serialization experience should double check that the note changed 
> is now correct with the package name update.
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56626/
---

Review request for geode, Bruce Schuchardt, Dave Barnes, Hitesh Khamesra, Joey 
McAllister, and Udo Kohlmeyer.


Repository: geode


Description
---

GEODE-2479 Remove docs reference to gemstone.com package


Diffs
-

  geode-docs/developing/data_serialization/auto_serialization.html.md.erb 
cdb63a8fb5f5c5bcf7330bc2d611c3e126618b51 

Diff: https://reviews.apache.org/r/56626/diff/


Testing
---

Gradle rat check passes.  I did not build Geode.  I did build the manual, and 
no errors occur for a manual build.

Devs with serialization experience should double check that the note changed is 
now correct with the package name update.


Thanks,

Karen Miller

Re: [VOTE] RC2: Apache Geode release - v1.1.0

[Karen Miller]

+0 for me as well.  I had also noted that the documentation has a couple of
prominent
and incorrect instances of 1.0.0-incubating.  If there were to be a release
candidate 3,
let's for sure get as many of the incorrect instances of 1.0.0-incubating
fixed as possible.
However, the 2 within the reference manual (user guide) do not change the
functionality
of the SW:

geode-docs/about_geode.html.md.erb:This documentation describes product
concepts and provides complete setup instructions for Apache Geode
1.0.0-incubating. Source files are ava
geode-docs/prereq_and_install.html.md.erb:Each host of Apache Geode
1.0.0-incubating that meets a small set of prerequisites may follow the
provided installation instructions.


On Fri, Feb 10, 2017 at 2:30 PM, Hitesh Khamesra <
hitesh...@yahoo.com.invalid> wrote:

> Here are all the reference of incubating in release branch 1.1.0. Please
> look into this..
>
> -bash-4.2$ git grep 'incubat'
> BUILDING.md:v1.0.0-incubating
> BUILDING.md:v1.0.0-incubating
> dev-tools/docker/compile/start-compile-docker.sh:  -w
> "/home/${USER_NAME}/incubator-geode" \
> dev-tools/docker/compile/start-compile-docker.sh:  -v
> "$PWD:/home/${USER_NAME}/incubator-geode" \
> dev-tools/docker/docs/build-docs.sh:  -w 
> "/home/${USER_NAME}/incubator-geode/geode-book"
> \
> dev-tools/docker/docs/build-docs.sh:  -v 
> "$PWD:/home/${USER_NAME}/incubator-geode"
> \
> dev-tools/docker/docs/view-docs.sh:  -w "/home/${USER_NAME}/incubator-
> geode/geode-book/final_app/public" \
> dev-tools/docker/docs/view-docs.sh:  -v 
> "$PWD:/home/${USER_NAME}/incubator-geode"
> \
> docker/Dockerfile:  && git clone https://github.com/apache/
> incubator-geode.git \
> docker/Dockerfile:  && cd incubator-geode \
> docker/Dockerfile:  && git checkout rel/v1.0.0-incubating \
> docker/Dockerfile:  && ls /incubator-geode | grep -v geode-assembly |
> xargs rm -rf \
> docker/Dockerfile:  && rm -rf 
> /incubator-geode/geode-assembly/build/distributions/
> \
> docker/Dockerfile:ENV GEODE_HOME /incubator-geode/geode-
> assembly/build/install/apache-geode
> docker/README.md:docker build -t apachegeode/geode:1.0.0-incubating .
> docker/README.md:docker push apachegeode/geode:1.0.0-incubating
> docker/README.md:docker run -it -p 10334:10334 -p 7575:7575 -p 1099:1099
> apache/geode:1.0.0-incubating
> geode-core/src/main/java/org/apache/geode/internal/cache/AbstractLRURegionMap.java:
> * modification for LIFO Logic incubation
> geode-docs/about_geode.html.md.erb:This documentation describes product
> concepts and provides complete setup instructions for Apache Geode
> 1.0.0-incubating. Source files are ava
> geode-docs/prereq_and_install.html.md.erb:Each host of Apache Geode
> 1.0.0-incubating that meets a small set of prerequisites may follow the
> provided installation instructions.
> geode-old-versions/build.gradle:addTestSource('test100',
> '1.0.0-incubating')
> geode-site/website/content/docs/guide/10/about_geode.html:  Apache
> Geode 1.0.0-incubating Documentation |
> geode-site/website/content/docs/guide/10/about_geode.html:Apache
> Geode 1.0.0-incubating Documentation
> geode-site/website/content/docs/guide/10/about_geode.html:This
> documentation describes product concepts and provides complete setup
> instructions for Apache Geode 1.0.0-incuba
> geode-site/website/content/docs/guide/10/getting_started/book_intro.html:Each
> host of Apache Geode 1.0.0-incubating that meets a small set of
> prerequisites may follow the pro
> geode-site/website/content/docs/guide/10/getting_started/
> installation/install_standalone.html:Download the project source
> from the Releases page found at  geode-site/website/content/docs/guide/10/getting_started/
> installation/install_standalone.html:v1.0.0-incubating
> geode-site/website/content/docs/guide/10/getting_started/
> installation/install_standalone.html: Download the .zip or .tar file
> from the Releases page found at  plaintext">$ unzip apache-geode-1.0.0-incubating.zip -d
> geode-site/website/content/docs/guide/10/getting_started/
> installation/install_standalone.html:$ tar -xvf apache-geode-1.0.0-incubating.tar
> geode-site/website/content/docs/guide/10/getting_started/
> installation/install_standalone.html:v1.0.0-incubating
> geode-site/website/content/docs/guide/10/prereq_and_install.html:Each
> host of Apache Geode 1.0.0-incubating that meets a small set of
> prerequisites may follow the provided in
> geode-site/website/content/releases/index.html: class="icon-flag-checkered"> 1.0.0-incubating
> geode-site/website/content/releases/index.html:  [ http://apache.org/dyn/closer.cgi/geode/1.0.0-
> incubating/apache-geode-1.0.0-incubating.zip">ZIP,  geode-site/website/content/releases/index.html:  https://dist.apache.org/repos/dist/release/geode/1.0.
> 0-incubating/apache-geode-1.0.0-incubating.zip.asc">PG
> geode-site/website/content/releases/index.html:  [http://apache.org/dyn/closer.cgi/geode/1.0.0-
> 

GEODE-2260: reviews still needed. . .

[Karen Miller]

It's been a full week, but I haven't gotten any reviews on GEODE-2260, to
remove the geode-examples module from the geode repository.  I'm not
a build/gradle expert, and this commit changes the build, so it really needs
some reviews.

The review request is https://reviews.apache.org/r/55393/

Thanks.  Karen

Review Request 55393: GEODE-2260 Remove geode-examples from geode repo and geode build

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55393/
---

Review request for geode, Anthony Baker, William Markito, Mark Bretl, and Dan 
Smith.


Repository: geode


Description
---

GEODE-2260 Remove geode-examples from geode repo and geode build


Diffs
-

  build.gradle c9915358bd7b7071ddae9f8c058b2388db5a415b 
  geode-assembly/build.gradle dba5dc768a0b4829aff17c4143e8da3b87106319 
  geode-examples/.gitignore b1001a6575698224615e5d4b6ff804e9c4506d0a 
  geode-examples/README.md 62666035ab1bde5f9d5548e887e0133f006c2ef9 
  geode-examples/build.gradle 1e638bc2f18f5aed2ba007e60e7b8e48711383b9 
  geode-examples/gradle.properties c1739aff2825d87e10717f877cc4a12f4101c6c1 
  geode-examples/gradle/wrapper/gradle-wrapper.jar 
2c6137b87896c8f70315ae454e00a969ef5f6019 
  geode-examples/gradle/wrapper/gradle-wrapper.properties 
6132c99fbc50c6921e25432874c31a55382ef8fc 
  geode-examples/gradlew 9d82f78915133e1c35a6ea51252590fb38efac2f 
  geode-examples/gradlew.bat 5f192121eb4f5b109f22fa96a6246eb39e749ed6 
  geode-examples/replicated/.gitignore b858ea877b065d2420484a484d649f98054c9cc0 
  geode-examples/replicated/README.md ea923ddc76b3143bc288daf615e2c6a02e84447d 
  geode-examples/replicated/build.gradle 
52283ecef776b3f6a484bdc6e7cc3cdc5b1ffe29 
  geode-examples/replicated/scripts/.gitignore 
32f8870d0e0514786c159a18c9bcc6b62ac48956 
  geode-examples/replicated/scripts/pidkiller.sh 
ecf8f2d6911121f12df29d69dbbde7c0a67b5ced 
  geode-examples/replicated/scripts/setEnv.sh 
e9e860e271f523d4818f13b73de5df64897c19ed 
  geode-examples/replicated/scripts/startAll.sh 
2b08f197191ced868481462752b91cbe7d6e45b6 
  geode-examples/replicated/scripts/stopAll.sh 
a6364a861395e8e2077ff63f27946eee616e0b6b 
  
geode-examples/replicated/src/main/java/org/apache/geode/examples/replicated/BaseClient.java
 3e656f6a5b86b226db3611559eae13f92bf76b38 
  
geode-examples/replicated/src/main/java/org/apache/geode/examples/replicated/Consumer.java
 7954bb57b7a86bfe4baf8ba3b9798d713f71830e 
  
geode-examples/replicated/src/main/java/org/apache/geode/examples/replicated/Producer.java
 79d5dfecb2c21a09a9f926d505d466490e18c0b6 
  
geode-examples/replicated/src/test/java/org/apache/geode/examples/replicated/ConsumerTest.java
 2fab5087c0ce41dfeb57d2c97113165051d84096 
  
geode-examples/replicated/src/test/java/org/apache/geode/examples/replicated/ProducerTest.java
 9b4a2511bf27b83dbcd5552a5ed46ac2d85c1163 
  
geode-examples/replicated/src/test/java/org/apache/geode/examples/replicated/ReplicatedTest.java
 ab84485f8cd26a7da246fb59dc7856c79d1bcca2 
  geode-examples/settings.gradle 432a8ebc38f85e7e3e6c8b7d71328b90bc1356e4 
  
geode-examples/utils/src/main/java/org/apache/geode/example/utils/ShellUtil.java
 c5290b826ab40df4474e714e2a4d298e9f10e7f5 

Diff: https://reviews.apache.org/r/55393/diff/


Testing
---

Ran
`./gradlew precheckin -xdistributedTest -xintegrationTest -xflakyTest`
to verify that a geode-examples directory is not included in the source 
distribution.

Ran
`./gradlew build -Dskip.tests=true`
to verify no errors in the build (without tests).

Ran
`./gradlew tasks`
to observe that there were no tasks involving Examples.


Thanks,

Karen Miller

Re: [jira] [Commented] (GEODE-2260) Move geode examples to new repo home

[Karen Miller]

I'd appreciate reviews on this PR from Dan S, Swapnil B, Mark B, and Dave
B.,
along with anyone else who is interested in improving the new geode
examples.
Thanks.

On Fri, Jan 6, 2017 at 1:47 PM, ASF GitHub Bot (JIRA) <j...@apache.org>
wrote:

>
> [ https://issues.apache.org/jira/browse/GEODE-2260?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel=15805871#comment-15805871 ]
>
> ASF GitHub Bot commented on GEODE-2260:
> ---
>
> GitHub user karensmolermiller opened a pull request:
>
> https://github.com/apache/geode-examples/pull/1
>
> GEODE-2260: Revise geode-examples to be in their own repo
>
> - Revise build to add rat check and spotless task
> - Add Apache license to README.md files
> - Apply spotless format changes
> - Add .gitignore
> - Revise paths in README.md instructions
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/karensmolermiller/geode-examples
> feature/GEODE-2260
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/geode-examples/pull/1.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #1
>
> 
> commit 6b7eacb2bfb196b1aa390695445c6e8a28071d16
> Author: Karen Miller <kmil...@pivotal.io>
> Date:   2017-01-05T21:45:30Z
>
> GEODE-2260: Revise geode-examples to be in their own repo
>
> - Revise build to add rat check and spotless task
> - Add Apache license to README.md files
> - Apply spotless format changes
> - Add .gitignore
> - Revise paths in README.md instructions
>
> 
>
>
> > Move geode examples to new repo home
> > 
> >
> > Key: GEODE-2260
> > URL: https://issues.apache.org/jira/browse/GEODE-2260
> > Project: Geode
> >  Issue Type: New Feature
> >Reporter: Karen Smoler Miller
> >Assignee: Karen Smoler Miller
> >
> > Initialize new repository (https://github.com/apache/geode-examples)
> for geode-examples module.
> > Move current geode-examples module to the new repo.
> > Revise instructions to work outside the geode repo. Verify the
> replicated example works once moved.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Re: geode-examples vs geode/geode-examples

[Karen Miller]

Yes.  I'm moving everything over now, and after moving will remove it from
the
geode repository.  See https://issues.apache.org/jira/browse/GEODE-2260.

On Tue, Jan 3, 2017 at 2:02 PM, Kirk Lund  wrote:

> What's the plan for the new geode-examples repo and the existing
> geode-examples module of the geode repo? Are we planning to move examples
> and then delete geode/geode-examples?
>
> -Kirk
>

Review Request 55093: GEODE-2258 fix doc typos in section on setting properties

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55093/
---

Review request for geode, Bruce Schuchardt, Dave Barnes, and Joey McAllister.


Repository: geode


Description
---

GEODE-2258 fix doc typos in section on setting properties


Diffs
-

  
geode-docs/basic_config/gemfire_properties/setting_distributed_properties.html.md.erb
 22e373abccfdb89438f7ee5677578193c764c98b 

Diff: https://reviews.apache.org/r/55093/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55059/
---

Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

GEODE-2252 Update docs on vSphere performance tuning


Diffs
-

  geode-book/master_middleman/source/subnavs/geode-subnav.erb 
cb77952e6ad54f9aa1d5acd9bcad74e522cace0d 
  geode-docs/managing/monitor_tune/chapter_overview.html.md.erb 
db099459c5ef98b8dd7a86f1cb1434611ef51aa1 
  geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb 
2be5502a4e10cc5aed25c99bfc16808fb450bd0c 
  
geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb
 b5cb8a2af5857640cf653bc798d9b9ec4d1f26c9 

Diff: https://reviews.apache.org/r/55059/diff/


Testing
---

gradle rat check passes


Thanks,

Karen Miller

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

[Karen Miller]

> On Dec. 13, 2016, 11:11 p.m., Eric Shu wrote:
> > geode-docs/developing/transactions/data_location_cache_transactions.html.md.erb,
> >  line 44
> > <https://reviews.apache.org/r/54723/diff/1/?file=1583275#file1583275line44>
> >
> > Product may throw TransactionDataRebalancedException instead of 
> > TransactionDataNotColocatedException. Do we need to specify exact exception?

Wording changed to say that there will be an exception, but not which exception.

I'll rebase the second commit before merging to develop.


- Karen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54723/#review159073
-------


On Dec. 14, 2016, 4:33 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54723/
> ---
> 
> (Updated Dec. 14, 2016, 4:33 p.m.)
> 
> 
> Review request for geode, Dave Barnes, Eric Shu, and Joey McAllister.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> - First operation to a transactional system which has colocated
> data and replicated/distributed regions must be to a
> partitioned region (with colocated data), to set the transaction
> host.  Note that this was already documented, but not in a
> prominent place.  Now the basics of this info is repeated in
> a less-buried location.
> - Fixed poorly-working links within the subnav and fixed a
> couple of markdown errors.  The errors were improperly
> specified anchor tags.
> 
> 
> Diffs
> -
> 
>   
> geode-docs/developing/transactions/data_location_cache_transactions.html.md.erb
>  d96de82fa7d5f4074c88863c1732363530c12d39 
> 
> Diff: https://reviews.apache.org/r/54723/diff/
> 
> 
> Testing
> ---
> 
> gradle rat check passes
> 
> Geode book builds with no broken links
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54723/
---

(Updated Dec. 14, 2016, 4:33 p.m.)


Review request for geode, Dave Barnes, Eric Shu, and Joey McAllister.


Repository: geode


Description
---

- First operation to a transactional system which has colocated
data and replicated/distributed regions must be to a
partitioned region (with colocated data), to set the transaction
host.  Note that this was already documented, but not in a
prominent place.  Now the basics of this info is repeated in
a less-buried location.
- Fixed poorly-working links within the subnav and fixed a
couple of markdown errors.  The errors were improperly
specified anchor tags.


Diffs (updated)
-

  
geode-docs/developing/transactions/data_location_cache_transactions.html.md.erb 
d96de82fa7d5f4074c88863c1732363530c12d39 

Diff: https://reviews.apache.org/r/54723/diff/


Testing
---

gradle rat check passes

Geode book builds with no broken links


Thanks,

Karen Miller

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54723/
---

Review request for geode, Dave Barnes, Eric Shu, and Joey McAllister.


Repository: geode


Description
---

- First operation to a transactional system which has colocated
data and replicated/distributed regions must be to a
partitioned region (with colocated data), to set the transaction
host.  Note that this was already documented, but not in a
prominent place.  Now the basics of this info is repeated in
a less-buried location.
- Fixed poorly-working links within the subnav and fixed a
couple of markdown errors.  The errors were improperly
specified anchor tags.


Diffs
-

  geode-book/master_middleman/source/subnavs/geode-subnav.erb 
16aa1e78cb4ca64489c3c2c5d9fd4240684b0858 
  
geode-docs/developing/transactions/cache_transactions_by_region_type.html.md.erb
 fa3318a38356963262ea342d39fa98940812aa7e 
  geode-docs/developing/transactions/chapter_overview.html.md.erb 
b5e84a415451074e1ec803e0add20c7fe3272408 
  
geode-docs/developing/transactions/data_location_cache_transactions.html.md.erb 
d96de82fa7d5f4074c88863c1732363530c12d39 

Diff: https://reviews.apache.org/r/54723/diff/


Testing
---

gradle rat check passes

Geode book builds with no broken links


Thanks,

Karen Miller

Review Request 54616: GEODE-2098 Document that gfsh history is in .geode dir

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54616/
---

Review request for geode, Dave Barnes and Joey McAllister.


Repository: geode


Description
---

GEODE-2098 Document that gfsh history is in .geode dir


Diffs
-

  geode-docs/tools_modules/gfsh/command-pages/history.html.md.erb 
04e47366ad24341ec8831fe681b8f170d50e4c34 

Diff: https://reviews.apache.org/r/54616/diff/


Testing
---

gradle rat check passes

Book builds with no broken links.


Thanks,

Karen Miller

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54499/
---

Review request for geode, Dave Barnes, Jinmei Liao, Joey McAllister, and Kevin 
Duling.


Repository: geode


Description
---

GEODE-2092 Update docs with security examples location


Diffs
-

  geode-docs/managing/security/authentication_examples.html.md.erb 
b7634c851121e60c20b7a138aba32bd2bc002c2e 
  geode-docs/managing/security/authorization_example.html.md.erb 
2e725a107986f76a621a85bcdd8711e8b56b63a5 

Diff: https://reviews.apache.org/r/54499/diff/


Testing
---


Thanks,

Karen Miller

Re: Review Request 54332: GEODE-2178 - Docs: Update HTTP session management version numbers

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54332/#review158013
---




geode-docs/tools_modules/http_session_mgmt/tc_additional_info.html.md.erb (line 
48)
<https://reviews.apache.org/r/54332/#comment228665>

Can you update the java version number to 92 throughout?  That's what we 
call out as the minimum version that Geode works with.



geode-docs/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
 (line 191)
<https://reviews.apache.org/r/54332/#comment228667>

Please change java version number here as well.


- Karen Miller


On Dec. 3, 2016, 12:57 a.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54332/
> ---
> 
> (Updated Dec. 3, 2016, 12:57 a.m.)
> 
> 
> Review request for geode, Joey McAllister, Karen Miller, and Dan Smith.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2178 - Docs: Update HTTP session management version numbers
> 
> 
> Diffs
> -
> 
>   geode-docs/tools_modules/http_session_mgmt/quick_start.html.md.erb 
> cfab15a9e6834ba455afc2e7064f39bb0212a8fa 
>   geode-docs/tools_modules/http_session_mgmt/tc_additional_info.html.md.erb 
> 1e01978891bc3882e06c8e6a4dc7387c471c4ec6 
>   
> geode-docs/tools_modules/http_session_mgmt/tc_installing_the_module.html.md.erb
>  fdc199d90057a5760e12f0702c4a050d0628b9f6 
>   
> geode-docs/tools_modules/http_session_mgmt/tc_setting_up_the_module.html.md.erb
>  aa4244a61552dfa4378b4c638e241064cc6fbee4 
>   
> geode-docs/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
>  dc805b6fa9e9866dd2d9dbd64e6c155f95c581f9 
>   
> geode-docs/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
>  e0eb267903eca1c7180ecab884967e41b73a21e9 
> 
> Diff: https://reviews.apache.org/r/54332/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54315/
---

Review request for geode, Dave Barnes, Jinmei Liao, and Joey McAllister.


Repository: geode


Description
---

GEODE-2146 document new privileges req'd for deploy


Diffs
-

  geode-docs/managing/security/implementing_authorization.html.md.erb 
ec47133cd433be44b189628a44a780dbee49e6ee 

Diff: https://reviews.apache.org/r/54315/diff/


Testing
---

gradle rat check passes

Building the book finds no broken links.


Thanks,

Karen Miller

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53971/
---

(Updated Nov. 22, 2016, 6:02 p.m.)


Review request for geode, Bruce Schuchardt, Dave Barnes, Joey McAllister, and 
Kirk Lund.


Repository: geode


Description
---

GEODE-2125 Add doc note to not use kill cmd on servers


Diffs (updated)
-

  geode-docs/configuring/running/starting_up_shutting_down.html.md.erb 
01b191d2e09ea2e0fcd8b50f1677e91aed3a38de 

Diff: https://reviews.apache.org/r/53971/diff/


Testing
---

gradle rat check passes

geode book builds without any broken links


Thanks,

Karen Miller

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

[Karen Miller]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53971/
---

Review request for geode, Bruce Schuchardt, Dave Barnes, Joey McAllister, and 
Kirk Lund.


Repository: geode


Description
---

GEODE-2125 Add doc note to not use kill cmd on servers


Diffs
-

  geode-docs/configuring/running/starting_up_shutting_down.html.md.erb 
01b191d2e09ea2e0fcd8b50f1677e91aed3a38de 

Diff: https://reviews.apache.org/r/53971/diff/


Testing
---

gradle rat check passes

geode book builds without any broken links


Thanks,

Karen Miller