Re: PR Checks issues?

[Joey McAllister]

Hi Michael,

That may have been connected, at least in part, to a lack of a review. I
have given my review on adding this info to the README, which I think looks
good, and things seem to have gone green.

That said, as I mentioned in my review, I also wouldn't mind seeing a
thumbs up (or other feedback) from someone else in the community who will
be using these LGTM alerts regularly.

Best,
Joey

On Fri, Dec 13, 2019 at 11:31 AM Michael Oleske  wrote:

> Hi Geode Dev!
>
> This PR https://github.com/apache/geode/pull/4406 is a change to the
> readme.  However it took 3 empty commits to get it to go green enough to be
> allowed to be merged.  This seems odd, especially with just a readme
> change.  Is there something going with how CI works for PRs?  This was an
> incredibly frustrating experience.
>
> Thanks!
> -michael
>

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

[Joey McAllister]

+1 !!

On Fri, Nov 22, 2019 at 9:42 AM Dan Smith  wrote:

> +1
>
> Awesome!!!
>
> -Dan
>
> On Fri, Nov 22, 2019 at 9:33 AM Owen Nichols  wrote:
>
> > +1
> >
> > It makes total sense that gfsh should depend on core, and core should be
> > completely unaware of it.  The dependency untangling that results will
> also
> > help pave the way for other interfaces, such as a gfsh-free management
> REST
> > interface.
> >
> >
> > > On Nov 22, 2019, at 8:45 AM, Jinmei Liao  wrote:
> > >
> > > +100. Would be a great move.
> > >
> > > On Fri, Nov 22, 2019 at 8:40 AM Jens Deppe 
> wrote:
> > >
> > >> Hello All,
> > >>
> > >> We'd like to propose moving gfsh and all associated commands into its
> > own
> > >> gradle submodule (implicitly thus also producing a separate maven
> > >> artifact). The underlying intent is to decouple geode core from any
> > Spring
> > >> dependencies.
> > >>
> > >> The proposal is outlined here:
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/GEODE/Move+gfsh+code+to+a+separate+gradle+sub-project
> > >>
> > >> Please provide feedback for this proposal *on this email thread* and
> > not in
> > >> the comment section of the proposal page.
> > >>
> > >> The deadline for this proposal will be Monday, December 2.
> > >>
> > >> Thanks in advance for feedback / comments.
> > >>
> > >> --Jens & Patrick
> > >>
> > >
> > >
> > > --
> > > Cheers
> > >
> > > Jinmei
> >
> >
>

Re: Website Banner Graphic

[Joey McAllister]

Nick: I think the pertinent info on the trademarks page is this:

"The Apache Software Foundation considers the names of all top level
projects, all downloadable software products, our feather logo, and the
logos of our projects to be trademarks of the ASF. The ASF owns all Apache
trademarks on behalf of our volunteer project communities."

Only a few, not including Geode, are registered trademarks.

That said, I do think "Apache" should have a registered trademark symbol: ®

On Thu, Nov 14, 2019 at 12:13 PM Jacob Barrett  wrote:

> We have found the vector, which was already modified with the correct TM
> and a rendered PNG from it. That should get corrected on the site soon.
>
> > On Nov 14, 2019, at 11:32 AM, Nicholas Vallely 
> wrote:
> >
> > I feel like maybe this was talked about previously, but does Apache
> have a
> > registered Trademark for Geode? I don't see it on this list:
> > http://www.apache.org/foundation/marks/list/ which is fine for a TM from
> > what I know, but could we potentially be stepping on another TM'd thing
> > called Geode? Is there an ASF process for securing a registered TM, have
> we
> > already had this discussion and I am just late to the party?
> >
> > +1 to fixing the awfulness of that image though :)
> >
> >> On Thu, Nov 14, 2019 at 11:06 AM Alberto Bustamante Reyes
> >>  wrote:
> >>
> >> +1
> >>
> >> 
> >> De: Helena Bales 
> >> Enviado: jueves, noviembre 14, 2019 7:52 p. m.
> >> Para: dev@geode.apache.org
> >> Asunto: Re: Website Banner Graphic
> >>
> >> +1
> >>
> >> On Thu, Nov 14, 2019 at 10:47 AM Jacob Barrett 
> >> wrote:
> >>
> >>> Does anyone know who is responsible for our website’s graphics. The
> >>> recently added “TM” to the Geode logo needs to be redone. My design
> brain
> >>> can’t handle that the text is in the wrong font, the wrong color and
> >> isn’t
> >>> anti-aliased like the rest of the text and graphic components.
> >>>
> >>> https://geode.apache.org 
> >>> https://geode.apache.org/img/apache_geode_logo.png <
> >>> https://geode.apache.org/img/apache_geode_logo.png>
> >>>
> >>> The “TM" should be added to the original vector graphic and a new
> raster
> >>> should be generated from that.
> >>>
> >>> -Jake
> >>>
> >>>
> >>
>

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

[Joey McAllister]

+1 LGTM

On Wed, Nov 13, 2019 at 9:53 AM Dick Cavender  wrote:

> +1
>
> On Wed, Nov 13, 2019 at 9:52 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.
> > >
> >
>

Re: next steps on release/1.9.0

[Joey McAllister]

Sai,

It looks like the documentation issue around GEODE-2113 was fixed at some
point as part of another effort, so I've closed that ticket.

GEODE-4794 needs some docs clarification and then it will be ready to go,
as well.

Best,
Joey

On Wed, Feb 27, 2019 at 11:32 AM Bruce Schuchardt 
wrote:

> I want to merge the PR for GEODE-6451 into the release/1.9.0 branch.
> It's been reviewed and is going through final testing now.
>
> On 2/27/19 10:26 AM, Sai Boorlagadda wrote:
> > By end of this week, I am planning to create the first release candidate.
> > Are there any other issues other than this last one?
> >
> > - GEODE-6359 - Bruce is looking into it.
> > - geode-examples using https in build scripts.
> >
> > There are about 6[1] issues in JIRA that are in
> open/in-progress/re-opened
> > status for 1.9.0.
> > Can I request all the devs to reflect JIRA with current status?
> >
> > GEODE-6067 - add gfsh list data-source command - Darrel Schneider
> > GEODE-5817 - CI Failure: StopServerAccepta... - Kenneth Howe
> > GEODE-5816 - ClusterStartupRule fails to ...   - Dan Smith
> > GEODE-5711 - create jndi-binding gfsh ...     - Karen Smoler
> > Miller
> > GEODE-4794 - ConfigurePDXCommand    - Joey McAllister
> > GEODE-2113 - Implement SSL over NIO - Joey McAllister
> >
> > [1]https://issues.apache.org
> >
> /jira/browse/GEODE-6107?jql=project%20%3D%20GEODE%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%201.9.0
> >
>

Re: August 2018 Board Report Volunteer

[Joey McAllister]

Looks great, Anthony! Thanks for putting this together!

My only note is to capitalize "YouTube" in the reference to Addison's video
series.

Best,
Joey

On Thu, Aug 9, 2018 at 3:46 PM Anthony Baker  wrote:

> This is a bit late so please review asap.  Thanks!
>
> ## Description:
> Apache Geode provides a database-like consistency model, reliable
> transaction processing and a shared-nothing architecture to maintain
> very low latency performance with high concurrency processing.
>
> ## Issues:
> There are no issues requiring board attention at this time.
>
> ## Activity:
> - We held up releasing v1.7.0 in favor of fixing more bugs and making
> our tests more reliable.  We closed out 40% of the open test bugs (out
> of 220) and removed the ‘FlakyTest’ category from 136 tests.
> - We integrated our pre-commit tests directly into GitHub PR checks.
> This makes it super easy for committers and contributors to run and
> review test results.
> - We’ve optimized test runtimes for pull requests to get results in
> less than an hour.  If someone were to run the same tests on a laptop
> it would take over 18h.
> - We upgraded the project build tools to Gradle 4.9 in preparation for
> supporting Java 11.
> - We merged a contribution to add thread monitoring and take action if
> a thread appears to hang.
> - We discussed improvements to handling of the default SSL context.
> - We discussed improvements to allow customizable trust boundaries for
> securing OQL method invocations.
> - The Geode PMC discussed and approved a Geode session track at the
> SpringOnePlatform conference (see
> https://springoneplatform.io/2018/geode).
> - Community member Addison Huddy posted a series of seven (and
> counting) youtube videos on “Geode by Example”.
>
> ## Health report:
> - We’ve had a number of excellent contributions from new community
> members in the last three months.  Although the PMC did not add any
> committers this quarter we should definitely review and discuss adding
> new committers soon.
> - By increasing test speed, reliability, and ease of access we have
> lowered the barriers for new contributions and community
> participation.
>
> ## PMC changes:
>
> - Currently 46 PMC members.
> - No new PMC members added in the last 3 months
> - Last PMC addition was Dick Cavender on Tue Feb 20 2018
>
> ## Committer base changes:
>
> - Currently 87 committers.
> - No new committers added in the last 3 months
> - Last committer addition was Michael W. Dodge at Wed Jan 24 2018
>
> ## Releases:
>
> - Last release was 1.6.0 on Fri May 04 2018
>
> ## Mailing list activity:
>
> Mailing lists have remained active and have maintained consistent usage
> levels.
>
> - dev@geode.apache.org:
>- 183 subscribers (up 0 in the last 3 months):
>- 683 emails sent to list (793 in previous quarter)
>
> - iss...@geode.apache.org:
>- 54 subscribers (up 0 in the last 3 months):
>- 2991 emails sent to list (6890 in previous quarter)
>
> - u...@geode.apache.org:
>- 242 subscribers (down -9 in the last 3 months):
>- 141 emails sent to list (148 in previous quarter)
>
> ## JIRA activity:
>
> - 349 JIRA tickets created in the last 3 months
> - 330 JIRA tickets closed/resolved in the last 3 months
>
> Anthony
>
> On Thu, Jul 26, 2018 at 1:52 PM Dave Barnes  wrote:
> >
> > ...and just between you and me, if people knew how easy is to generate
> this
> > report using the template, they wouldn't be so reluctant to put forth a
> > little effort on behalf of this great project :). Oh, did I say that out
> > loud?
> >
> > On Thu, Jul 26, 2018 at 1:45 PM, Dave Barnes  wrote:
> >
> > > Hi Mark,
> > > Just between you and me, if nobody else steps up I'll be your safety
> net.
> > > Only tricky part is I'll be on PTO through 8/7. But if you don't have
> > > anybody by 8/8, I can jump in.
> > > Dave
> > >
> > >
> > > On Thu, Jul 26, 2018 at 12:22 PM, Mark Bretl 
> wrote:
> > >
> > >> Hi Everyone,
> > >>
> > >> Its that time again to submit a report for the August Board Meeting.
> We
> > >> need to submit a report by August 8th. Would anyone like to volunteer
> to
> > >> write a draft of the report?
> > >>
> > >> Template:
> https://cwiki.apache.org/confluence/display/GEODE/ASF+Board+
> > >> Report
> > >> +Template
> > >>
> > >> Previous Reports: https://whimsy.apache.org/board/minutes/Geode.html
> > >>
> > >> Best regards,
> > >>
> > >> --Mark
> > >>
> > >
> > >
>

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

[Joey McAllister]

+1 for including these. They are documentation-only changes that are
applicable to 1.7.

On Wed, May 23, 2018 at 8:24 AM Karen Miller  wrote:

> 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.apache.org and GDPR

[Joey McAllister]

+1 to removing this. Thanks, Anthony!

On Mon, May 21, 2018 at 3:03 PM Michael Stolz  wrote:

> +1 to remove it
>
> --
> Mike Stolz
> Principal Engineer, GemFire Product Lead
> Mobile: +1-631-835-4771 <(631)%20835-4771>
> Download the GemFire book here.
> <
> https://content.pivotal.io/ebooks/scaling-data-services-with-pivotal-gemfire
> >
>
> On Mon, May 21, 2018 at 11:31 AM, Greg Chase  wrote:
>
> > Part of GDPR: Don’t collect or store data you don’t intend to use.
> >
> > +1 to remove it.
> >
> > This email encrypted by tiny buttons & fat thumbs, beta voice
> recognition,
> > and autocorrect on my iPhone.
> >
> > > On May 21, 2018, at 8:29 AM, Anthony Baker  wrote:
> > >
> > > The geode website uses Google Analytics [1].  IANAL but there are some
> > constraints that will apply when GPDR takes effect [2].  Specifically,
> > users can opt-out of data collection.  Given how little use we’ve made of
> > this data, I think it would be simpler to just remove the GA tracker from
> > our website.
> > >
> > > Thoughts?
> > >
> > >
> > > Anthony
> > >
> > > [1] https://github.com/apache/geode-site/blob/master/
> > website/layouts/header.html#L40  > geode-site/blob/master/website/layouts/header.html#L40>
> > > [2] https://issues.apache.org/jira/browse/MSKINS-143 <
> > https://issues.apache.org/jira/browse/MSKINS-143>
> > >
> >
>

Re: Quarterly report - DRAFT for your review

[Joey McAllister]

Looks good to me, too. Thanks, Dave!

On Tue, May 8, 2018 at 10:41 AM Mark Bretl  wrote:

> Looks good! Thanks Dave!
>
> --Mark
>
> On Tue, May 8, 2018 at 10:13 AM, Dave Barnes  wrote:
>
> > Here's the near-final draft of our quarterly report. Responses received
> by
> > 5pm PDT today (May 8) will be incorporated.
> > Thanks,
> > Dave Barnes
> >
> > ## Description:
> >  - Apache Geode provides a database-like consistency model, reliable
> >transaction processing and a shared-nothing architecture to maintain
> >very low latency performance with high concurrency processing.
> >
> > ## Issues:
> >  - There are no issues requiring board attention at this time.
> >
> > ## Activity:
> >  - Two full product releases, Apache Geode versions 1.5 and 1.6
> >  - Community member Addison Huddy presented "What the Heck is an
> In-Memory
> > Data Grid?" at DataEngConf SF '18
> >  - Launched an investigation into adding PR status updates based on CI
> jobs
> > (see INFRA-16409).
> >  - In connection with SpringOne Platform, Pivotal, Inc., proposed to
> host a
> > Geode community event, prompting a discussion among the PMC regarding
> logo
> > use
> >
> > ## Health report:
> >  - Mailing lists remain active and productive.
> >  - JIRA tickets show that issues continue to be identified and resolved.
> >  - We’re continuing to work on attracting new contributors and making it
> > easier to participate in the community.
> >
> > ## PMC changes:
> >
> >  - Currently 46 PMC members.
> >  - New PMC members:
> > - Dick Cavender was added to the PMC on Tue Feb 20 2018
> > - Lynn Hughes-Godfrey was added to the PMC on Mon Feb 19 2018
> > - Lynn Gallinat was added to the PMC on Mon Feb 19 2018
> >
> > ## Committer base changes:
> >
> >  - Currently 87 committers.
> >  - No new committers added in the last 3 months
> >  - Last committer addition was Michael W. Dodge at Wed Jan 24 2018
> >
> > ## Releases:
> >
> >  - Apache Geode 1.5.0 was released on Fri Apr 06 2018. Highlights
> include:
> >
> > - Support for arithmetic operators in the WHERE clause of OQL queries
> > - Expanded gfsh (cli) functionality in the form of new commands and
> > enhancements to existing commands
> > - REST interface improvements
> > - Improved deadlock prevention
> > - Improved client capabilities, including enhancements to load
> > balancing and subscription behavior
> > - 18 new features
> > - 270 enhancements and improvements
> > - 226 bug fixes
> >
> > A full list of issues that were resolved in Apache Geode 1.5 can be found
> > at
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12318420=12342395
> >
> >  - Apache Geode 1.6.0 was released on Fri May 04 2018 under the watchful
> > eye of Mike Stolz, in his debut as an Apache Geode Release Manager.
> > Highlights include:
> >
> > - Serialization refinements
> > - JDBC connector improvements
> > - gfsh (cli) commands to configure and manage JNDI bindings
> > - Cluster configuration enhancements
> > - 17 new features
> > - 139 enhancements and improvements
> > - 148 bug fixes
> >
> > A full list of issues that were resolved in Apache Geode 1.6 can be found
> > at
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12318420=12342867
> >
> >
> > ## Mailing list activity:
> >
> > Mailing lists have remained active and have maintained consistent usage
> > levels.
> >
> >  - dev@geode.apache.org:
> > - 182 subscribers (up 6 in the last 3 months):
> > - 818 emails sent to list (706 in previous quarter)
> >
> >  - iss...@geode.apache.org:
> > - 54 subscribers (up 0 in the last 3 months):
> > - 7028 emails sent to list (4960 in previous quarter)
> >
> >  - u...@geode.apache.org:
> > - 251 subscribers (up 12 in the last 3 months):
> > - 151 emails sent to list (228 in previous quarter)
> >
> >
> > ## JIRA activity:
> >
> >  - 612 JIRA tickets created in the last 3 months
> >  - 701 JIRA tickets closed/resolved in the last 3 months
> >
>

Re: Geode Website Check For Apache Events Does Not Have Expected Link

[Joey McAllister]

Nice find, Mark.

As much as I would like for that yellow to turn green (and that would be
easy enough to do), in this case, I think the homepage link is correct as
it is and the link checker is performing inaccurately. Perhaps we could
file a ticket with Apache to account for projects that include a link to
the Apache Events page?

On Thu, Apr 12, 2018 at 2:54 PM Mark Bretl  wrote:

> Hi All,
>
> Apache has a tool for checking all TLP websites and our site is all 'green'
> except for the Events check, https://whimsy.apache.org/site/project/geode.
>
> At the bottom/footer of our main page, there is an Apache -> Events link
> which has a HREF value of http://www.apache.org/events/.  The website
> Events check is searching for ^https?://.*apache.org/events/current-event.
>
> The expected link is on the Community page, but I think the crawler is
> finding the link on the main page and stopping. Do we want to update the
> footer or leave it as is?
>
> --Mark
>

Re: [VOTE] Apache Geode 1.5.0.RC2

[Joey McAllister]

Mike: Just for clarification, is yours a +1 for the release or a +1 to
extending the vote?

Thanks,
Joey



On Wed, Apr 4, 2018 at 12:21 PM Dan Smith <dsm...@pivotal.io> wrote:

> +1 to an extension of time
>
> +1 to this release - ran geode-release-check, looks good to me.
>
> -Dan
>
> On Wed, Apr 4, 2018 at 11:20 AM, Michael Stolz <mst...@pivotal.io> wrote:
>
> > +1
> >
> > --
> > Mike Stolz
> >
> > On Apr 4, 2018 2:06 PM, "Joey McAllister" <jmcallis...@pivotal.io>
> wrote:
> >
> > > +1 to Anthony's recommendation of extending the vote by 24 hours, since
> > > some community members might have ignored this one, thinking that the
> > > negative vote would lead to a new release candidate/vote.
> > >
> > >
> > > On Wed, Apr 4, 2018 at 10:59 AM Anthony Baker <aba...@pivotal.io>
> wrote:
> > >
> > > > Bruce updated his vote (retracting the -1) in a different thread.
> That
> > > > leaves us with one vote cast thus far which is not sufficient.  I
> > suggest
> > > > we extend the vote window an extra 24h to allow additional time to
> > review
> > > > and vote.
> > > >
> > > > Anthony
> > > >
> > > >
> > > > > On Apr 2, 2018, at 3:13 PM, Bruce Schuchardt <
> bschucha...@pivotal.io
> > >
> > > > wrote:
> > > > >
> > > > > I vote -1 in light of GEODE-4989 <
> > > > https://issues.apache.org/jira/browse/GEODE-4989>. This issue can
> > cause
> > > > CQ queries to be slow or even hang.  I can see that the serialization
> > > work
> > > > that caused this problem is in the release/1.5.0 branch.
> > > > >
> > > > >
> > > > > On 3/30/18 12:15 PM, Swapnil Bawaskar wrote:
> > > > >> Both issues mentioned in the RC1 vote thread
> > > > >> <
> > > > https://lists.apache.org/thread.html/f5e21be3bb5985836a7931b43d992a
> > > f49fa6d7f079bdfa6aaf0fa0bb@%3Cdev.geode.apache.org%3E
> > > > >
> > > > >> have been resolved.
> > > > >>
> > > > >> This is the second release candidate for Apache Geode, version
> > 1.5.0.
> > > > >> Thanks to all the community members for their contributions to
> this
> > > > >> release!
> > > > >>
> > > > >> *** Please download, test and vote by Wednesday, April 4, 1200 hrs
> > > > >> US Pacific. ***
> > > > >>
> > > > >> It fixes 235 issues. release notes can be found at:
> > > > >>
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12318420=12342395
> > > > >>
> > > > >> Note that we are voting upon the source tags: rel/v1.5.0.RC1
> > > > >> https://github.com/apache/geode/tree/rel/v1.5.0.RC2
> > > > >> https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC2
> > > > >>
> > > > >> Commit ID:
> > > > >> 1be57f3d18e5a97dbcc784d6df7724f5f6ced39b (geode)
> > > > >> 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples)
> > > > >>
> > > > >> Source and binary files:
> > > > >> https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC2
> > > > >>
> > > > >> Maven staging repo:
> > > > >> https://repository.apache.org/content/repositories/
> > > orgapachegeode-1039
> > > > >>
> > > > >>
> > > > >> Geode's KEYS file containing PGP keys we use to sign the release:
> > > > >> https://github.com/apache/geode/blob/develop/KEYS
> > > > >>
> > > > >> Release Signed with Key: pub 4096R/18F902DB 2016-04-07
> > > > >> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
> > > > >>
> > > > >
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Apache Geode 1.5.0.RC2

[Joey McAllister]

+1 to Anthony's recommendation of extending the vote by 24 hours, since
some community members might have ignored this one, thinking that the
negative vote would lead to a new release candidate/vote.


On Wed, Apr 4, 2018 at 10:59 AM Anthony Baker  wrote:

> Bruce updated his vote (retracting the -1) in a different thread.  That
> leaves us with one vote cast thus far which is not sufficient.  I suggest
> we extend the vote window an extra 24h to allow additional time to review
> and vote.
>
> Anthony
>
>
> > On Apr 2, 2018, at 3:13 PM, Bruce Schuchardt 
> wrote:
> >
> > I vote -1 in light of GEODE-4989 <
> https://issues.apache.org/jira/browse/GEODE-4989>. This issue can cause
> CQ queries to be slow or even hang.  I can see that the serialization work
> that caused this problem is in the release/1.5.0 branch.
> >
> >
> > On 3/30/18 12:15 PM, Swapnil Bawaskar wrote:
> >> Both issues mentioned in the RC1 vote thread
> >> <
> https://lists.apache.org/thread.html/f5e21be3bb5985836a7931b43d992af49fa6d7f079bdfa6aaf0fa0bb@%3Cdev.geode.apache.org%3E
> >
> >> have been resolved.
> >>
> >> This is the second release candidate for Apache Geode, version 1.5.0.
> >> Thanks to all the community members for their contributions to this
> >> release!
> >>
> >> *** Please download, test and vote by Wednesday, April 4, 1200 hrs
> >> US Pacific. ***
> >>
> >> It fixes 235 issues. release notes can be found at:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420=12342395
> >>
> >> Note that we are voting upon the source tags: rel/v1.5.0.RC1
> >> https://github.com/apache/geode/tree/rel/v1.5.0.RC2
> >> https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC2
> >>
> >> Commit ID:
> >> 1be57f3d18e5a97dbcc784d6df7724f5f6ced39b (geode)
> >> 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples)
> >>
> >> Source and binary files:
> >> https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC2
> >>
> >> Maven staging repo:
> >> https://repository.apache.org/content/repositories/orgapachegeode-1039
> >>
> >>
> >> Geode's KEYS file containing PGP keys we use to sign the release:
> >> https://github.com/apache/geode/blob/develop/KEYS
> >>
> >> Release Signed with Key: pub 4096R/18F902DB 2016-04-07
> >> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
> >>
> >
>
>

Re: Starter tickets

[Joey McAllister]

+1 to "starter" over "newbie." I think the ++ plan makes sense, too.

Thanks for the initiative on this, Alexander. It seems like a very valuable
effort for the community.

On Fri, Mar 2, 2018 at 1:35 PM Alexander Murmann 
wrote:

> I am glad this already revealed that we aren't consistent in what labels we
> are using. I assume the idea of newbie++ was to facilitate a progression? I
> really like that and would love to keep something like that.
>
> I don't think the term "newbie" is great. To me it has a little bit of a
> negative connotation.
>
> Does anyone have an issue with adopting "starter" and "starter++"
> consistently? I am happy to do the conversion work and make sure the
> communication in the wiki etc. is consistent going forward.
>
> Mike, I agree that there is probably a lot of great work that someone who
> doesn't know the code base well can do in Pulse. I'd suggest that we still
> decide on a case by case basis. A quick glance showed a few bugs that
> probably should be tackled sooner rather than later. I'll take a pass at
> all Pulse related tickets and see if they are a good fit.
>
> On Fri, Mar 2, 2018 at 10:45 AM, Michael Stolz  wrote:
>
> > I'd love to tag all the pulse issues as newbie if we could.
> >
> >
> >
> > On Fri, Mar 2, 2018 at 1:34 PM, Anthony Baker  wrote:
> >
> > > Good idea!  We he have a few other labels relevant to this as well:
> > >
> > > - newbie
> > > - low-hanging-fruit
> > >
> > > Anthony
> > >
> > >
> > > > On Mar 2, 2018, at 10:03 AM, Alexander Murmann 
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I think we could make it easier for people to find tasks that can be
> > > their
> > > > first contribution to Geode. The wiki page on how to contribute
> > > >  >
> > > has a
> > > > list of suggested projects. Most of those are pretty ambitious and
> > likely
> > > > would be overwhelming to first time contributors. There also is a
> link
> > > > to tickets
> > > > labeled with "Starter"
> > > >  > > 3D%20Geode%20AND%20labels%20%3D%20starter%20AND%20status%
> > > 20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29>.
> > > > I think the later is probably a much better angle for someone to
> start
> > > > contributing to Geode. Unfortunately there was less than a handful of
> > > > tickets labeled as starter tickets.
> > > >
> > > > My suggestion is to find tickets that strike a healthy balance
> between
> > > being
> > > >
> > > >   - simple enough that someone new to the code base can realistically
> > > take
> > > >   them on
> > > >   - rewarding enough that someone can feel a sense of accomplishment
> > > after
> > > >   having their PR merged
> > > >   - small enough that it can be accomplished in an evening or at
> most a
> > > >   long weekend
> > > >   - unlikely to result in conflicts with larger efforts that someone
> is
> > > >   already undertaking
> > > >
> > > > It would be great to have a variety of tickets that have different
> > levels
> > > > of complexity and required effort to allow new contributors of
> varying
> > > > experience levels to start contributing meaningfully and maybe even
> > > support
> > > > somewhat of a progression curve for someone who wants to become a
> > regular
> > > > contributor or even committer.
> > > >
> > > > I'd also suggest to not allow the list to grow too large. If the list
> > > gets
> > > > bigger than 20-30 tickets it might get too hard to keep a clear grasp
> > on
> > > it
> > > > and the risk of having tickets that aren't relevant anymore
> increases.
> > > > Nothing would be more frustrating to a new contributor than investing
> > > their
> > > > personal time just to find out that it was wasted. So let's be
> mindful
> > of
> > > > not using this as a dumping ground for everything we'd like to see,
> but
> > > > know we'll never get to.
> > > >
> > > > I already labeled a few more tickets as starter. Please feel free to
> > > > validate that I didn't violate my own suggestions in doing so.
> > > >
> > > > Thoughts?
> > >
> > >
> >
>

Re: ASF Quarterly report - please review by Tuesday Noon

[Joey McAllister]

+1

On Mon, Feb 12, 2018 at 5:05 PM Dan Smith  wrote:

> +1 Looks good to me!
>
> -Dan
>
> On Mon, Feb 12, 2018 at 2:32 PM, Dave Barnes  wrote:
>
> > Please review this report and send me any corrections by Noon on Tuesday,
> > 12/13/18.
> > Thanks,
> > Dave
> >
> > ## Description:
> >  - Apache Geode provides a database-like consistency model, reliable
> >transaction processing and a shared-nothing architecture to maintain
> >very low latency performance with high concurrency processing.
> >
> > ## Issues:
> >  - There are no issues requiring board attention.
> >
> > ## Activity:
> >  - Released Apache Geode 1.4 with 288 resolved tickets, including the
> > following improvements:
> > - Added a JDBC connector
> > - Introduced an improved eviction algorithm
> > - Added Lucene indexing/searching for nested objects
> > - Added new examples
> > - Provided blacklist/whitelist capability for Java serialization
> > - Several additions and improvements to the gfsh CLI utility
> >
> > ## Health report:
> > - We’re continuing to work on attracting new contributors and making it
> > easier
> > to participate in the community.
> > - Mailing list activity is healthy.
> > - Work has started toward the next Geode 1.5.0 release, with a plan to
> > include improvements in usability and security.
> >
> > ## PMC changes:
> >
> >  - Currently 43 PMC members.
> >  - New PMC members:
> > - Michael W. Dodge was added to the PMC on Tue Jan 23 2018
> > - Brian Rowe was added to the PMC on Tue Jan 23 2018
> >
> > ## Committer base changes:
> >
> >  - Currently 88 committers.
> >  - New commmitters:
> > - Michael W. Dodge was added as a committer on Wed Jan 24 2018
> > - Brian Rowe was added as a committer on Wed Jan 24 2018
> >
> > ## Releases:
> >
> >  - 1.4.0 was released on Fri Jan 26 2018, including new features,
> examples,
> > and bug fixes.
> > - Release notes:
> > https://cwiki.apache.org/confluence/display/GEODE/
> > Release+Notes#ReleaseNotes-1.4.0
> > - Release artifacts: http://geode.apache.org/releases/
> > - Release documentation:
> > http://geode.apache.org/docs/guide/14/about_geode.html
> >
> >
> > ## Mailing list activity:
> >
> >  - dev@geode.apache.org:
> > - 176 subscribers (down -2 in the last 3 months):
> > - 734 emails sent to list (1784 in previous quarter)
> >
> >  - iss...@geode.apache.org:
> > - 54 subscribers (down -1 in the last 3 months):
> > - 5677 emails sent to list (4632 in previous quarter)
> >
> >  - u...@geode.apache.org:
> > - 240 subscribers (up 5 in the last 3 months):
> > - 253 emails sent to list (225 in previous quarter)
> >
> >
> > ## JIRA activity:
> >
> >  - 677 JIRA tickets created in the last 3 months
> >  - 495 JIRA tickets closed/resolved in the last 3 months
> >
>

Re: Geode Jira/GitHub Integration configuration changes

[Joey McAllister]

(Er, from JIRA ticket comments, that is.)

On Mon, Dec 18, 2017 at 10:02 AM Joey McAllister <jmcallis...@pivotal.io>
wrote:

> +1 to removing the diffs from JIRA tickets.
>
> On Mon, Dec 18, 2017 at 9:58 AM Dan Smith <dsm...@pivotal.io> wrote:
>
>> Hi Kirk,
>>
>> I think this is will probably require a request to infra. You can file a
>> JIRA with infra assuming we have consensus to get rid of the diffs (huge
>> +1
>> from me:)
>>
>> Also, please don't cross post with private@geode. The private list should
>> *only* be used for things that can't be discussed publicly.
>>
>> -Dan
>>
>> https://www.apache.org/dev/infra-contact
>>
>> On Mon, Dec 18, 2017 at 9:43 AM, Kirk Lund <kl...@apache.org> wrote:
>>
>> > Since we switched to GitBox for Geode, all Pull Requests are resulting
>> in
>> > huge diffs being posted to the comments on Geode Jira tickets. Some of
>> > these are resulting in hangs trying to open certain Jira tickets. I'd
>> like
>> > to determine what our options are for changing how this is configured.
>> >
>> > I looked through all of the options in the administration screens for
>> > Geode Jira but couldn't find anything other than a link to INFRA GitHub
>> > Integration that I don't have permission to access (
>> >
>> https://issues.apache.org/jira/plugins/servlet/project-config/GEODE/fields
>> > -- search down for "GitHub Integration").
>> >
>> > Does anyone know where to change this configuration or is this a request
>> > that needs to go to ASF INFRA?
>> >
>> > Thanks,
>> > Kirk
>> >
>>
>

Re: Geode Jira/GitHub Integration configuration changes

[Joey McAllister]

+1 to removing the diffs from JIRA tickets.

On Mon, Dec 18, 2017 at 9:58 AM Dan Smith  wrote:

> Hi Kirk,
>
> I think this is will probably require a request to infra. You can file a
> JIRA with infra assuming we have consensus to get rid of the diffs (huge +1
> from me:)
>
> Also, please don't cross post with private@geode. The private list should
> *only* be used for things that can't be discussed publicly.
>
> -Dan
>
> https://www.apache.org/dev/infra-contact
>
> On Mon, Dec 18, 2017 at 9:43 AM, Kirk Lund  wrote:
>
> > Since we switched to GitBox for Geode, all Pull Requests are resulting in
> > huge diffs being posted to the comments on Geode Jira tickets. Some of
> > these are resulting in hangs trying to open certain Jira tickets. I'd
> like
> > to determine what our options are for changing how this is configured.
> >
> > I looked through all of the options in the administration screens for
> > Geode Jira but couldn't find anything other than a link to INFRA GitHub
> > Integration that I don't have permission to access (
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/GEODE/fields
> > -- search down for "GitHub Integration").
> >
> > Does anyone know where to change this configuration or is this a request
> > that needs to go to ASF INFRA?
> >
> > Thanks,
> > Kirk
> >
>

[DRAFT] Geode Board Report November 2017

[Joey McAllister]

Hi folks,

Please review the below draft of our report to the board for this past quarter
and offer corrections. As Mark mentioned, we need to submit the draft ASAP,
preferably before the weekend. Please review and comment by 5p Pacific Time
tomorrow (i.e., about 24 hours from now).

I do have one question regarding the mailing list health: Does anyone have
any thoughts about the decline in email count to the Dev list? We have
about half the number of emails to the Dev list as we had in the previous
quarter, and that number also declined between the previous two reports. I
suspect that this might be related to the creation of the Issues email list
(and that the number has now stabilized), but I wanted to put it to the
community.

Thanks!
Joey

-

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

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

## Activity:
- Released Geode 1.3.0 with 371 resolved tickets, including the following
  improvements:
  - Finer-grained security
  - The ability to snapshot multiple regions simultaneously
  - New Geode examples:
- Putting multiple values at once
- Demonstrating Lucene indexing and searching

## Health report:
- We’re continuing to work on attracting new contributors and making it
easier
  to participate in the community.
- Mailing list activity is healthy.
- Work has started toward the next Geode 1.4.0 release, with a plan to
include
  the new client/server protocol.

## PMC changes:
- Currently 41 members
- New PMC members:
  - David Kimura was added to the PMC on Sun Sep 10 2017.
  - Galen O'Sullivan was added to the PMC on Mon Sep 25 2017.
  - Mike Stolz was added to the PMC on Sun Oct 29 2017.
  - Nick Reich was added to the PMC on Thu Oct 19 2017.
  - Patrick Rhomberg was added to the PMC on Tue Oct 31 2017.

## Committer base changes:
- Currently 86 committers.
- New committers:
  - David Kimura was added as a committer on Mon Sep 11 2017.
  - Galen O'Sullivan was added as a committer on Tue Sep 05 2017.
  - Mike Stolz was added as a committer on Sat Oct 21 2017.
  - Nick Reich was added as a committer on Sat Oct 14 2017.
  - Patrick Rhomberg was added as a committer on Wed Nov 01 2017.

## Releases:
- Most recent release was 1.3.0 on Tue Oct 31 2017. Geode 1.3.0 contains a
  number of bug fixes and improvements, including finer-grained security and
  the ability to snapshot multiple regions simultaneously.
  - Release notes:

https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.3.0
  - Release artifacts: http://geode.apache.org/releases/
  - Release documentation:
http://geode.apache.org/docs/guide/13/about_geode.html

## Mailing list activity:
- dev@geode.apache.org:
  - 175 subscribers (up 1 in the last 3 months):
  - 2030 emails sent to list (4170 in previous quarter)

- iss...@geode.apache.org:
  - 55 subscribers (down 1 in the last 3 months):
  - 4883 emails sent to list (3066 in previous quarter)

- u...@geode.apache.org:
  - 234 subscribers (up 2 in the last 3 months):
  - 236 emails sent to list (277 in previous quarter)

## JIRA activity:
- 547 JIRA tickets created in the last 3 months
- 422 JIRA tickets closed/resolved in the last 3 months

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

[Joey McAllister]

+1 to removing the button

On Fri, Sep 29, 2017 at 11:09 AM Michael William Dodge 
wrote:

> +1 to improving the signal-to-noise ratio
>
> > On 29 Sep, 2017, at 11:07, Jason Huynh  wrote:
> >
> > GEODE-3280
>
>

Re: INFRA Jira URL

[Joey McAllister]

I think this is it:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=25=INFRA.
(At least, that's the JIRA link I got from Infra's contact page.)

On Mon, Sep 18, 2017 at 10:17 AM Kirk Lund  wrote:

> Does anyone know the URL for Apache INFRA Jira?
>
> Thanks,
> Kirk
>

Re: Geode sessions at SpringOne Platform conference

[Joey McAllister]

Hi Jag,

Thanks for the pointer to the Geode page for SpringOne. I'd be happy to add
that info to the Events section of the Geode Community page.

Do you have an existing banner image—preferably one comparable in
dimensions to the ApacheCon banner currently on that page, which the
SpringOne banner will replace? If not, do you have the details you'd like
to include?

Best,
Joey

On Thu, Sep 7, 2017 at 10:22 AM Jagdish Mirani  wrote:

> Hello Geode contributors:
> As you most likely already know, we're folding the next Geode Summit into
> the upcoming SpringOne Platform conference. We're working through some
> great session proposals, and we'll keep adding the accepted sessions to the
> Geode page on the SpringOne Platform site.
>
> https://springoneplatform.io/geode
>
> I would like to promote the Geode coverage at this event on the Apache
> Geode site; the most appropriate placement is probably on the community
> page:
> http://geode.apache.org/community/
>
> It would also be great to get a banner
> on the home page, if this is appropriate.
>
> Who can help with editing the Apache Geode site to include this?
>
> --
> Regards
> Jag
>

Re: Gitbox enables the full GitHub workflow

[Joey McAllister]

+1

On Tue, Aug 22, 2017 at 11:28 AM Ken Howe  wrote:

> +1 Yes, let’s make the move
>
> > On Aug 22, 2017, at 11:21 AM, Nabarun Nag  wrote:
> >
> > +1
> >
> > On Tue, Aug 22, 2017 at 11:15 AM Kirk Lund  wrote:
> >
> >> +1 to move all our repos to gitbox
> >>
> >> On Tue, Aug 22, 2017 at 11:08 AM, Jacob Barrett 
> >> wrote:
> >>
> >>> +1
> >>>
> >>> Sent from my iPhone
> >>>
>  On Aug 22, 2017, at 10:49 AM, Jared Stewart 
> >> wrote:
> 
>  +1 for moving the other repos to Gitbox
> 
>  On Aug 22, 2017 10:43 AM, "Anthony Baker"  wrote:
> 
> 
> > On Aug 7, 2017, at 6:09 PM, Roman Shaposhnik 
> >>> wrote:
> >
> > Hi!
> >
> > it has just come to my attention that Gitbox at ASF
> > has been enabling full GitHub workflow (with being
> > able to click Merge this PR button, etc.) for quite
> > some time.
> >
> > This basically allows a project to have GH as a R/W
> > repo as opposed to R/O mirror of what we all currnently
> > have: https://gitbox.apache.org/repos/asf
> >
> > Personally I'm not sure I like GH workflow all that much,
> > but if there's interest -- you can opt-in into Gitbox. Once
> > you do -- your source of truth moves to GH. You can't
> > have it both ways with git-wip-us.apache.org and Gitbox.
> >
> > Thanks,
> > Roman.
> 
>  Now that we’ve got some experience with gitbox on geode-native, are we
>  ready to convert the other repos?
> 
>  - geode
>  - geode-site
>  - geode-examples
> 
>  I think we should.
> 
>  Anthony
> >>>
> >>
>
>

Re: [DRAFT] Geode Board Report August 2017

[Joey McAllister]

Looks good.  Thanks, Dan!

On Wed, Aug 9, 2017 at 2:23 PM Anthony Baker <aba...@pivotal.io> wrote:

> LGTM
>
> > On Aug 9, 2017, at 2:01 PM, Mark Bretl <mbr...@apache.org> wrote:
> >
> > Looks good to me. Thanks Dan for taking the time to create the draft.
> >
> > If there are no issues, then I will post this EOD PST.
> >
> > --Mark
> >
> > On Mon, Aug 7, 2017 at 2:04 PM, Dan Smith <dsm...@pivotal.io> wrote:
> >
> >> Hi folks,
> >>
> >> Please review the below draft for our report to the board for this past
> >> quarter and offer corrections. As Mark mentioned, we need to submit the
> >> draft this Wednesday.
> >>
> >> Thanks!
> >> -Dan
> >>
> >> -
> >>
> >> ## Description:
> >>
> >> - Apache Geode provides a database-like consistency model, reliable
> >> transaction processing and a shared-nothing architecture to maintain
> very
> >> low
> >> latency performance with high concurrency processing.
> >>
> >> ## Issues:
> >>
> >> - There are no issues requiring board attention at this time.
> >>
> >> ## Activity:
> >>
> >> - Geode 1.2 was released with over 300 tickets resolved, including
> >>  - Integration with Apache Lucene is no longer experimental
> >>  - A built in partition resolver
> >>  - Examples bundled with the distribution
> >> - ApacheCon presentation - Building an IoT platform with Apache Apollo
> and
> >> Apache Geode by Swapnil Bawaskar
> >>
> >> ## Health report:
> >>
> >> - We’re continuing to work on attracting new contributors and making it
> >> easier
> >> to participate in the community.
> >> - Mailing list activity is healthy.
> >> - Work has started towards the next Geode release, 1.3.0 including
> >> development of a new client/server protocol.
> >>
> >> ## PMC changes:
> >>
> >> - Currently 36 PMC members (+1 since last report)
> >> - Joey McAllister was added to the PMC on Mon Jul 24 2017
> >>
> >> ## Committer base changes:
> >>
> >> - Currently 81 committers (+2 since last report)
> >> - Joey McAllister was added as a committer on Tue Jul 25 2017
> >> - Deepak Dixit was added as a committer on Thu Jul 13 2017
> >>
> >> ## Releases:
> >>
> >> - 1.2.0 was released on Wed July 17th 2017
> >>
> >> ## Mailing list activity:
> >>
> >> - Mailing lists remain active and we’re seeing continued growth in
> >> subscriber
> >> counts.  Mailing list traffic on dev went down because we redirected
> jira
> >> traffic to iss...@geode.apache.org, but the combined activity
> increased.
> >>
> >> - dev@geode.apache.org:
> >> - 174 subscribers (up 10 in the last 3 months)
> >> - 4264 emails sent in the past 3 months, 7166 in the previous cycle
> >>
> >> - iss...@geode.apache.org:
> >> - 56 subscribers (up 1 in the last 3 months)
> >> - 3183 emails sent in the past 3 months, 0 in the previous cycle
> >>
> >> - u...@geode.apache.org:
> >> - 232 subscribers (up 12 in the last 3 months)
> >> - 286 emails sent in the past 3 months, 202 in the previous cycle
> >>
> >> ## JIRA activity:
> >>
> >> - 513 JIRA tickets created in the last 3 months
> >> - 351 JIRA tickets closed/resolved in the last 3 months
> >>
>
>

Re: New Committer And PMC Member: Joey McAllister

[Joey McAllister]

Thanks, everyone!

[drum solos; throws sticks to Fred]


On Tue, Jul 25, 2017 at 12:36 PM Nitin Lamba <nla...@apache.org> wrote:

> Welcome Joey!
>
> On Tue, Jul 25, 2017 at 12:21 PM, Fred Krone <fkr...@pivotal.io> wrote:
>
> > Drum solo!
> >
> > On Tue, Jul 25, 2017 at 12:05 PM, Anthony Baker <aba...@pivotal.io>
> wrote:
> >
> > > Welcome Joey!
> > >
> > > > On Jul 25, 2017, at 11:58 AM, Mark Bretl <mbr...@apache.org> wrote:
> > > >
> > > > The Apache Geode Project Management Committee has invited Joey
> > > McAllister to
> > > > be committer on the project and join the Geode PMC. We are pleased to
> > > > announce he has accepted.
> > > >
> > > > Please join me in welcoming Joey!
> > > >
> > > > Best regards,
> > > >
> > > > Mark
> > > > On behalf of the Apache Geode PMC
> > >
> > >
> >
>

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

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


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: PING message is "Mischief Managed"

[Joey McAllister]

+ * for "pong."

Alternatively: "Wouldn't you prefer a nice game of chess?"

*[Unicode character U+1F3D3]

On Thu, Jul 13, 2017 at 1:54 PM Michael William Dodge 
wrote:

> +1 for "pong".
>
> > On 13 Jul, 2017, at 13:45, Kirk Lund  wrote:
> >
> > I'm really boring... I would've just had it reply "PONG" ;)
> >
> > On Thu, Jul 13, 2017 at 11:57 AM, John Blum  wrote:
> >
> >> Here you go...
> >>
> >> https://github.com/apache/geode/blob/rel/v1.1.1/geode-
> >> core/src/main/java/org/apache/geode/management/internal/web/shell/
> >> RestHttpOperationInvoker.java#L151-L204
> >>
> >>
> >> On Thu, Jul 13, 2017 at 10:51 AM, John Blum  wrote:
> >>
> >>> Corrections below (apologies)...
> >>>
> >>> On Thu, Jul 13, 2017 at 10:44 AM, John Blum  wrote:
> >>>
>  Yeah, that was my doing. :)
> 
>  I thought it would be more fun to return a special message than the
>  typical "Alive".  "Mischief Managed" comes from *Harry Potter*.
> 
>  This endpoint is of course benign/idempotent and was purely meant to
> >> test
>  the Management REST API's availability, or rather that the
> >> Manage/Locator
>  was still "online".
> 
>  Unlike JMX RMI, HTTP is stateless.  When a JMX RMI connection is made,
> >> it
>  is persistent and constantly "connected", where as each HTTP request
> to
> >> the
>  Management REST API opens and closes a connection.  Therefore, you
> have
> >> no
>  idea whether *Gfsh* is still connected to the Manager between requests
>  unlike the JMX RMI connection.
> 
>  So, I run a background Thread that "polls" this endpoint every 500 ms.
>  It might even test the message; I don't remember.  Once the response
> is
>  anything other than 200 OK, then we know there is a problem and that
> the
>  connection was most likely terminated.
> 
>  Therefore, it keeps the behavior of the HTTP connection between *Gfsh*
>  and the Manager similar to the JMX RMI connection by returning...
> 
>  No longer connected to 10.99.199.10[1099].
> 
>  gfsh>
> 
> 
>  On Thu, Jul 13, 2017 at 10:36 AM, Jacob Barrett 
>  wrote:
> 
> > For the older crowed I would have rather it replied:
> >
> > Ah, I see you have the machine that goes 'ping!'.
> >
> > Sent from my iPhone
> >
> >> On Jul 13, 2017, at 10:23 AM, Jared Stewart 
> > wrote:
> >>
> >> I'm young enough to recognize it as a Harry Potter reference, but I
> > have no
> >> idea what it's doing in our product code.
> >>
> >> - Jared
> >>
> >>> On Jul 13, 2017 10:14 AM, "Kirk Lund"  wrote:
> >>>
> >>> Anyone know why the response to a REST service PING returns
> >> "Mischief
> >>> Managed!?
> >>>
> >>> @RequestMapping(method = {RequestMethod.GET, RequestMethod.HEAD},
> > value =
> >>> "/ping")
> >>> public ResponseEntity ping() {
> >>> return new ResponseEntity("Mischief
> >>> Managed!",
> >>> HttpStatus.OK);
> >>> }
> >>>
> >>> /Users/klund/dev/geode [949]$ git grep
> > 'Mischief
> >>> Managed'
> >>> geode-core/src/main/java/org/apache/geode/management/
> >>> internal/web/controllers/ShellCommandsController.java:
> >>>  return new ResponseEntity("Mischief
> >>> Managed!",
> >>>
> >
> 
> 
> 
>  --
>  -John
>  john.blum10101 (skype)
> 
> >>>
> >>>
> >>>
> >>> --
> >>> -John
> >>> john.blum10101 (skype)
> >>>
> >>
> >>
> >>
> >> --
> >> -John
> >> john.blum10101 (skype)
> >>
>
>

[jira] [Updated] (GEODE-3029) Tomcat Install Documentation has incorrect required JARs

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-3029:
---
Description: 
This page 
(https://geode.apache.org/docs/guide/11/tools_modules/http_session_mgmt/tomcat_installing_the_module.html)
 has the incorrect required JARs needed to install tomcat with geode.

Currently the list is:
antlr jar
fastutil jar
geode-core jar
javax.transaction-api jar
jgroups jar
log4j-api jar
log4j-core jar
log4j-jul jar

The correct list should be:
antlr jar
fastutil jar
geode-core jar
javax.transaction-api jar
jgroups jar
log4j-api jar
log4j-core jar
log4j-jul jar
commons-lang jar
shiro-core jar

  was:
This page 
(http://gemfire.docs.pivotal.io/geode/tools_modules/http_session_mgmt/tomcat_installing_the_module.html)
 has the incorrect required JARs needed to install tomcat with geode.

Currently the list is:
antlr jar
fastutil jar
geode-core jar
javax.transaction-api jar
jgroups jar
log4j-api jar
log4j-core jar
log4j-jul jar

The correct list should be:
antlr jar
fastutil jar
geode-core jar
javax.transaction-api jar
jgroups jar
log4j-api jar
log4j-core jar
log4j-jul jar
commons-lang jar
shiro-core jar


> Tomcat Install Documentation has incorrect required JARs
> 
>
> Key: GEODE-3029
> URL: https://issues.apache.org/jira/browse/GEODE-3029
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: David Anuta
> Fix For: 1.2.0
>
>
> This page 
> (https://geode.apache.org/docs/guide/11/tools_modules/http_session_mgmt/tomcat_installing_the_module.html)
>  has the incorrect required JARs needed to install tomcat with geode.
> Currently the list is:
> antlr jar
> fastutil jar
> geode-core jar
> javax.transaction-api jar
> jgroups jar
> log4j-api jar
> log4j-core jar
> log4j-jul jar
> The correct list should be:
> antlr jar
> fastutil jar
> geode-core jar
> javax.transaction-api jar
> jgroups jar
> log4j-api jar
> log4j-core jar
> log4j-jul jar
> commons-lang jar
> shiro-core jar



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [DISCUSS] Discussions of API changes missing or lost in noise

[Joey McAllister]

+1 to using "[DISCUSS]" in subject lines for this. Great idea, Dan.

+1 also to segregating automated JIRA activity to its own list. (If we do
that, let's remember to add it to the Community web page.)

On Thu, Jun 1, 2017 at 2:09 PM Dan Smith  wrote:

> Hi devs,
>
> This is similar to the discussion John started about keeping track of
> changes to geode. I'm seeing some changes happening to the public API that
> I feel like maybe should have a more visible discussion. For example
> GEODE-2892 (Region.sizeOnServer) or GEODE-3005 (new API for partitioning).
>
> I think we should have a clear policy to send an email with [DISCUSS] in
> the header to mailing list for changes to the public API, behavior, or
> dependencies. Or wiki
> <
> https://cwiki.apache.org/confluence/display/GEODE/Criteria+for+Code+Submissions
> >
> says that changes should be discussed, but it doesn't really specify how.
>
> Part of the issue is that I find it impossible to keep up with the amount
> of JIRA noise on the dev list, so just creating a JIRA is not enough for me
> to notice a new API change. I propose that we segregate all of this
> automated email onto a separate list, either geode-commits or some new
> list. I'd like to segregate anything not directly sent by a human - JIRAs,
> PRs, and reviewboards.
>
> -Dan
>

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.

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


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

[jira] [Updated] (GEODE-2975) Attributes are not validated in lucene xml configuration

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2975:
---
Component/s: docs

> Attributes are not validated in lucene xml configuration
> 
>
> Key: GEODE-2975
> URL: https://issues.apache.org/jira/browse/GEODE-2975
> Project: Geode
>  Issue Type: Bug
>  Components: docs, lucene
>Reporter: Barry Oglesby
> Fix For: 1.2.0
>
>
> No exception is thrown for a lucene xml configuration missing a required 
> attribute.
> No exception is thrown for a lucene xml configuration including an unknown 
> attribute.
> If a {{lucene:field}} element is defined like below, no exception is thrown 
> for the invalid attribute called {{namexx}} and no exceptio is thrown because 
> the required attribute called {{name}} is not included.
> {noformat}
> 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2988) create a security example

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2988:
---
Component/s: docs

> create a security example
> -
>
> Key: GEODE-2988
> URL: https://issues.apache.org/jira/browse/GEODE-2988
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, security
>Reporter: Swapnil Bawaskar
>
> create an example for demonstrating security. The example should show how to 
> leverage the {{security-manager}}, register the {{AuthInitializer}} on the 
> client and have recipes for various roles.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 59562: GEODE-2941 Pulse documentation is outdated

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


On May 25, 2017, 12:45 a.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59562/
> ---
> 
> (Updated May 25, 2017, 12:45 a.m.)
> 
> 
> Review request for geode, Jinmei Liao and Joey McAllister.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2941 Pulse documentation is outdated
> 
> 
> Diffs
> -
> 
>   geode-book/master_middleman/source/subnavs/geode-subnav.erb 
> c97e5ec3ee961c500d0f006f9cb04ec5d569224d 
>   geode-docs/configuring/cluster_config/gfsh_persist.html.md.erb 
> 45f73f9f3ffbb569c554f2c89ad86713af1695e6 
>   geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb 
> 894b9985a24ff9e0775b2fc755ee0b6d1ba15984 
>   geode-docs/managing/management/jmx_manager_node.html.md.erb 
> 97ca066ca581689c87da5fe1d93e38ff4d13f64d 
>   geode-docs/managing/management/management_system_overview.html.md.erb 
> ecf69f5fb104850a54a57eaf69ce6f6a7d78e3bb 
>   geode-docs/managing/management/mm_overview.html.md.erb 
> 89a8df5c2957f23d9cdacffc8a6062ed40cccb47 
>   geode-docs/tools_modules/book_intro.html.md.erb 
> e7390c5d00f6ade80fe3fd01ad9e729bbdd75f11 
>   geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb 
> e2a4edccddb7fa63b060002c243d955a7182ed7d 
>   geode-docs/tools_modules/lucene_integration.html.md.erb 
> e97ce061838228d46568fb80b5799cc361f74148 
>   geode-docs/tools_modules/pulse/chapter_overview.html.md.erb 
> 19de8f1d28f84402d46cb4efdf71bedb720f14a1 
>   geode-docs/tools_modules/pulse/pulse-auth.html.md.erb PRE-CREATION 
>   geode-docs/tools_modules/pulse/pulse-embedded.html.md.erb PRE-CREATION 
>   geode-docs/tools_modules/pulse/pulse-hosted.html.md.erb PRE-CREATION 
>   geode-docs/tools_modules/pulse/pulse-views.html.md.erb PRE-CREATION 
>   geode-docs/tools_modules/pulse/quickstart.html.md.erb 
> 6bcf1dc1d7c3b23c5d70a6c542103faf3970152e 
>   geode-docs/tools_modules/pulse/system_requirements.html.md.erb 
> 05dffe65a1ea67d66040c5ac1f3cde3788a5e10d 
>   geode-docs/tools_modules/redis_adapter.html.md.erb 
> 47da3fcf211e41a374da58f369ac20e346002bb6 
> 
> 
> Diff: https://reviews.apache.org/r/59562/diff/1/
> 
> 
> Testing
> ---
> 
> Compiled user guide (with bookbinder) - no broken links. Selected sections 
> reviewed by developers while in draft form.
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

[jira] [Updated] (GEODE-2933) jmx-manager-hostname-for-clients should be a gfsh option

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2933:
---
Component/s: (was: docs)

> jmx-manager-hostname-for-clients should be a gfsh option
> 
>
> Key: GEODE-2933
> URL: https://issues.apache.org/jira/browse/GEODE-2933
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> When jmx manager is started in the cloud, the command to start the locator so 
> that one can connect gfsh from outside the cloud is:
> {noformat}
> start locator --name=test 
> --J=-Dgemfire.jmx-manager-hostname-for-clients=
> {noformat}
> We should make jmx-manager-hostname-for-clients a top level option to the 
> {{start server}} and {{start locator}} commands.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2963) Document GEODE-2933: Make jmx-manager-hostname-for-clients a top-level option to start server and start locator commands

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2963:
---
Priority: Minor  (was: Major)

> Document GEODE-2933: Make jmx-manager-hostname-for-clients a top-level option 
> to start server and start locator commands
> 
>
> Key: GEODE-2963
> URL: https://issues.apache.org/jira/browse/GEODE-2963
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>    Reporter: Joey McAllister
>Priority: Minor
>
> This is for documenting GEODE-2933 (make jmx-manager-hostname-for-clients a 
> top-level option to the {{start server}} and {{start locator}} commands).
> From GEODE-2933:
> {quote}
> When jmx manager is started in the cloud, the command to start the locator so 
> that one can connect gfsh from outside the cloud is:
> {noformat}
> start locator --name=test 
> --J=-Dgemfire.jmx-manager-hostname-for-clients=
> {noformat}
> We should make jmx-manager-hostname-for-clients a top-level option to the 
> {{start server}} and {{start locator}} commands.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (GEODE-2963) Document GEODE-2933: Make jmx-manager-hostname-for-clients a top-level option to start server and start locator commands

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2963:
--

 Summary: Document GEODE-2933: Make 
jmx-manager-hostname-for-clients a top-level option to start server and start 
locator commands
 Key: GEODE-2963
 URL: https://issues.apache.org/jira/browse/GEODE-2963
 Project: Geode
  Issue Type: Sub-task
  Components: docs
Reporter: Joey McAllister


This is for documenting GEODE-2933 (make jmx-manager-hostname-for-clients a 
top-level option to the {{start server}} and {{start locator}} commands).

>From GEODE-2933:
{quote}
When jmx manager is started in the cloud, the command to start the locator so 
that one can connect gfsh from outside the cloud is:
{noformat}
start locator --name=test 
--J=-Dgemfire.jmx-manager-hostname-for-clients=
{noformat}
We should make jmx-manager-hostname-for-clients a top-level option to the 
{{start server}} and {{start locator}} commands.
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (GEODE-2942) Add Search to Geode User Guide on Website

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2942:
--

 Summary: Add Search to Geode User Guide on Website
 Key: GEODE-2942
 URL: https://issues.apache.org/jira/browse/GEODE-2942
 Project: Geode
  Issue Type: New Feature
  Components: docs
Reporter: Joey McAllister


As a User Guide reader, I want to be able to search through the User Guide on 
the Geode website rather than going to Google.com.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2935) Add Events link to Geode site footer

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2935:
---
Priority: Minor  (was: Major)

> Add Events link to Geode site footer
> 
>
> Key: GEODE-2935
> URL: https://issues.apache.org/jira/browse/GEODE-2935
> Project: Geode
>  Issue Type: Task
>  Components: web-content
>    Reporter: Joey McAllister
>    Assignee: Joey McAllister
>Priority: Minor
>  Labels: website
>
> From [~mbretl]:
> {quote}
> ASF has created a new tool for scanning TLP sites for compliance and other
> requests. The new tool is located at https://whimsy.apache.org/site, with our 
> own Geode report at https://whimsy.apache.org/site/project/geode. The report 
> looks good, with only one missing requirement of an Events page.
> When I searched for 'event' on the [source of the 
> tool|https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob_plain;f=tools/site-scan.rb;hb=HEAD],
>  I found http://www.apache.org/events/README.txt, with more event information.
> However, looking at the code, it is searching for: 'apache.org/events/'. So
> we can either create the link as text or use the image as a link.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Apache TLP Website Link Checks

[Joey McAllister]

I opened GEODE-2935 <https://issues.apache.org/jira/browse/GEODE-2935> and PR
#3 <https://github.com/apache/geode-site/pull/3> to add the link to the
footer and the image/link on the Community page. If anyone has any
questions, please let me know.

If it looks good, feel free to merge it at your convenience.

Thanks!
Joey

On Tue, May 16, 2017 at 5:24 PM Joey McAllister <jmcallis...@pivotal.io>
wrote:

> Thanks, Mark. That's very helpful.
>
> It looks like Apache updates the image to represent whatever the next
> event is (e.g., right now it's ApacheCon). I'd definitely like to add a
> text link to our footer, but it might also be nice to add the image to the
> Events section of the Geode Community page, so there's always something
> Apache-related there, even when we don't have an upcoming Geode event to
> promote.
>
> Does anyone have any thoughts on that?
>
> Best,
> Joey
>
> On Tue, May 16, 2017 at 5:18 PM Mark Bretl <mbr...@apache.org> wrote:
>
>> When I searched for 'event' on the source of the tool, [1], I found the
>> following page, [2], with more event information.
>>
>> However, looking at the code, it is searching for: 'apache.org/events/'.
>> So
>> we can either create the link as text or use the image as a link.
>>
>> --Mark
>>
>> [1]
>>
>> https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob_plain;f=tools/site-scan.rb;hb=HEAD
>> [2] http://www.apache.org/events/README.txt
>>
>>
>> On Tue, May 16, 2017 at 4:45 PM, Joey McAllister <jmcallis...@pivotal.io>
>> wrote:
>>
>> > Hi Mark,
>> >
>> > I think I can swing that.
>> >
>> > It's kind of hard to tell what the requirement for an "Events" link is.
>> The
>> > link-checker you point to links out to a "Required Links" page (
>> > https://www.apache.org/foundation/marks/pmcs#navigation), but there's
>> no
>> > mention of "Events" on there.
>> >
>> > I *think* we just need a link to https://www.apache.org/events/ in the
>> > "Apache" section of our website footer. Does that sound right to you?
>> Or,
>> > does anyone else in the community know whether this would suffice?
>> >
>> > Thanks!
>> > Joey
>> >
>> >
>> >
>> > On Tue, May 16, 2017 at 4:10 PM Mark Bretl <mbr...@apache.org> wrote:
>> >
>> > > Hi,
>> > >
>> > > ASF has created a new tool for scanning TLP sites for compliance and
>> > other
>> > > requests. The new tool is located at [1], with our own Geode report at
>> > [2].
>> > > The report looks good, with only one missing requirement of an Events
>> > page.
>> > >
>> > > Would someone with web skills be able to update our site?
>> > >
>> > > Best regards,
>> > >
>> > > --Mark
>> > >
>> > > [1] https://whimsy.apache.org/site
>> > > [2] https://whimsy.apache.org/site/project/geode
>> > >
>> >
>>
>

[jira] [Assigned] (GEODE-2935) Add Events link to Geode site footer

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister reassigned GEODE-2935:
--

Assignee: Joey McAllister

> Add Events link to Geode site footer
> 
>
> Key: GEODE-2935
> URL: https://issues.apache.org/jira/browse/GEODE-2935
> Project: Geode
>  Issue Type: Task
>  Components: web-content
>    Reporter: Joey McAllister
>    Assignee: Joey McAllister
>
> From [~mbretl]:
> {quote}
> ASF has created a new tool for scanning TLP sites for compliance and other
> requests. The new tool is located at https://whimsy.apache.org/site, with our 
> own Geode report at https://whimsy.apache.org/site/project/geode. The report 
> looks good, with only one missing requirement of an Events page.
> When I searched for 'event' on the [source of the 
> tool|https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob_plain;f=tools/site-scan.rb;hb=HEAD],
>  I found http://www.apache.org/events/README.txt, with more event information.
> However, looking at the code, it is searching for: 'apache.org/events/'. So
> we can either create the link as text or use the image as a link.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (GEODE-2935) Add Events link to Geode site footer

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2935:
--

 Summary: Add Events link to Geode site footer
 Key: GEODE-2935
 URL: https://issues.apache.org/jira/browse/GEODE-2935
 Project: Geode
  Issue Type: Task
  Components: web-content
Reporter: Joey McAllister


>From [~mbretl]:
{quote}
ASF has created a new tool for scanning TLP sites for compliance and other
requests. The new tool is located at https://whimsy.apache.org/site, with our 
own Geode report at https://whimsy.apache.org/site/project/geode. The report 
looks good, with only one missing requirement of an Events page.

When I searched for 'event' on the [source of the 
tool|https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob_plain;f=tools/site-scan.rb;hb=HEAD],
 I found http://www.apache.org/events/README.txt, with more event information.

However, looking at the code, it is searching for: 'apache.org/events/'. So
we can either create the link as text or use the image as a link.
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Apache TLP Website Link Checks

[Joey McAllister]

Thanks, Mark. That's very helpful.

It looks like Apache updates the image to represent whatever the next event
is (e.g., right now it's ApacheCon). I'd definitely like to add a text link
to our footer, but it might also be nice to add the image to the Events
section of the Geode Community page, so there's always something
Apache-related there, even when we don't have an upcoming Geode event to
promote.

Does anyone have any thoughts on that?

Best,
Joey

On Tue, May 16, 2017 at 5:18 PM Mark Bretl <mbr...@apache.org> wrote:

> When I searched for 'event' on the source of the tool, [1], I found the
> following page, [2], with more event information.
>
> However, looking at the code, it is searching for: 'apache.org/events/'.
> So
> we can either create the link as text or use the image as a link.
>
> --Mark
>
> [1]
>
> https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob_plain;f=tools/site-scan.rb;hb=HEAD
> [2] http://www.apache.org/events/README.txt
>
>
> On Tue, May 16, 2017 at 4:45 PM, Joey McAllister <jmcallis...@pivotal.io>
> wrote:
>
> > Hi Mark,
> >
> > I think I can swing that.
> >
> > It's kind of hard to tell what the requirement for an "Events" link is.
> The
> > link-checker you point to links out to a "Required Links" page (
> > https://www.apache.org/foundation/marks/pmcs#navigation), but there's no
> > mention of "Events" on there.
> >
> > I *think* we just need a link to https://www.apache.org/events/ in the
> > "Apache" section of our website footer. Does that sound right to you? Or,
> > does anyone else in the community know whether this would suffice?
> >
> > Thanks!
> > Joey
> >
> >
> >
> > On Tue, May 16, 2017 at 4:10 PM Mark Bretl <mbr...@apache.org> wrote:
> >
> > > Hi,
> > >
> > > ASF has created a new tool for scanning TLP sites for compliance and
> > other
> > > requests. The new tool is located at [1], with our own Geode report at
> > [2].
> > > The report looks good, with only one missing requirement of an Events
> > page.
> > >
> > > Would someone with web skills be able to update our site?
> > >
> > > Best regards,
> > >
> > > --Mark
> > >
> > > [1] https://whimsy.apache.org/site
> > > [2] https://whimsy.apache.org/site/project/geode
> > >
> >
>

Re: Apache TLP Website Link Checks

[Joey McAllister]

Hi Mark,

I think I can swing that.

It's kind of hard to tell what the requirement for an "Events" link is. The
link-checker you point to links out to a "Required Links" page (
https://www.apache.org/foundation/marks/pmcs#navigation), but there's no
mention of "Events" on there.

I *think* we just need a link to https://www.apache.org/events/ in the
"Apache" section of our website footer. Does that sound right to you? Or,
does anyone else in the community know whether this would suffice?

Thanks!
Joey



On Tue, May 16, 2017 at 4:10 PM Mark Bretl  wrote:

> Hi,
>
> ASF has created a new tool for scanning TLP sites for compliance and other
> requests. The new tool is located at [1], with our own Geode report at [2].
> The report looks good, with only one missing requirement of an Events page.
>
> Would someone with web skills be able to update our site?
>
> Best regards,
>
> --Mark
>
> [1] https://whimsy.apache.org/site
> [2] https://whimsy.apache.org/site/project/geode
>

[jira] [Updated] (GEODE-2924) move resources from DATA to CLUSTER

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2924:
---
Component/s: (was: docs)

> move resources from DATA to CLUSTER
> ---
>
> Key: GEODE-2924
> URL: https://issues.apache.org/jira/browse/GEODE-2924
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Swapnil Bawaskar
>
> As discussed in this proposal 
> https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security, the 
> only resource on DATA should be region, we should move:
> 1. pdx to CLUSTER:MANAGE
> 2. import cluster-configuration to CLUSTER:MANAGE
> 3. LockServiceMXBean.becomeLockGrantorto CLUSTER:MANAGE
> 4. list regions   to CLUSTER:READ



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2919) Provide finer grained security

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2919:
---
Component/s: docs

> Provide finer grained security
> --
>
> Key: GEODE-2919
> URL: https://issues.apache.org/jira/browse/GEODE-2919
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, security
>Reporter: Swapnil Bawaskar
>
> In our current security model, a user with DATA:MANAGE can create regions, 
> create disk stores, WAN gateways etc. I think this is a very wide scope, 
> because an administrator may want to give create region privilege to a 
> developer, but not necessarily give them the ability to create disk stores or 
> send the data in that region over WAN. I propose that we refine the security 
> model to make it finer grained.
> Please see this discussion on the mailing list: 
> https://lists.apache.org/thread.html/f96842276e93d8a6c3080ad3982c72431d62d1e7c717ebbc50941968@%3Cdev.geode.apache.org%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2924) move resources from DATA to CLUSTER

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2924:
---
Component/s: docs

> move resources from DATA to CLUSTER
> ---
>
> Key: GEODE-2924
> URL: https://issues.apache.org/jira/browse/GEODE-2924
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, security
>Reporter: Swapnil Bawaskar
>
> As discussed in this proposal 
> https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security, the 
> only resource on DATA should be region, we should move:
> 1. pdx to CLUSTER:MANAGE
> 2. import cluster-configuration to CLUSTER:MANAGE
> 3. LockServiceMXBean.becomeLockGrantorto CLUSTER:MANAGE
> 4. list regions   to CLUSTER:READ



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2554) Geode incubator docs are still up

[Joey McAllister (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001646#comment-16001646
 ] 

Joey McAllister commented on GEODE-2554:


I think the only thing left to do for this ticket is to follow Anthony's advice 
to "override the install directive to prevent it from trying to run gradlew 
assemble." Can someone with Gradle Wrapper knowledge help with that?

> Geode incubator docs are still up
> -
>
> Key: GEODE-2554
> URL: https://issues.apache.org/jira/browse/GEODE-2554
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Galen O'Sullivan
>Assignee: Joey McAllister
>Priority: Minor
> Fix For: 1.2.0
>
>
> Search engines still direct users to the Geode incubating docs, which are at:
> https://geode.apache.org/docs/guide/basic_config/data_regions/managing_data_regions.html
> The most recent docs have an 11 in the URL:
> https://geode.apache.org/docs/guide/11/basic_config/data_regions/managing_data_regions.html
> The old docs should either be taken down, or the path made to refer to 
> whatever the latest docs are. That way visitors won't get stuck on an ever 
> increasingly stale docs site.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


On May 5, 2017, 10:32 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59034/
> ---
> 
> (Updated May 5, 2017, 10:32 p.m.)
> 
> 
> Review request for geode, Hitesh Khamesra, Joey McAllister, and Pulkit 
> Chandra.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2352 Document that REST API requires two properties
> 
> 
> Diffs
> -
> 
>   geode-docs/rest_apps/chapter_overview.html.md.erb 
> 5e48675b7eba37ae3f6cd078111c0acf09d9ae68 
>   geode-docs/rest_apps/rest_prereqs.html.md.erb 
> 935f94b2caf83478bd0ac97dc797ccdcee695b8c 
>   geode-docs/rest_apps/setup_config.html.md.erb 
> 71c50f53dbc080f9d973b268eade9cb03c05e746 
> 
> 
> Diff: https://reviews.apache.org/r/59034/diff/1/
> 
> 
> Testing
> ---
> 
> The two properties, `http-service-bind-address` and `http-service-port`, are 
> not *mandatory* as stated in the ticket, but if allowed to default, they may 
> not be publicly visible. So we'll say they're optional, but that it's *good 
> practice* to specify them for visibility.
> This checkin also picks up some other corrections regarding API library name 
> and some format fixes.
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

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

[Joey McAllister]

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


Fix it, then Ship it!




Fix it, then ship it.


geode-docs/basic_config/config_concepts/distributed_system_member_configuration.html.md.erb
Lines 54 (patched)
<https://reviews.apache.org/r/59027/#comment247157>

I think this "remote" is still referring to this contextual definition of 
the word, right? If so, it should go in quotes, too.



geode-docs/managing/monitor_tune/udp_communication.html.md.erb
Lines 44 (patched)
<https://reviews.apache.org/r/59027/#comment247158>

hyphenate "flow-control protocol"


- Joey McAllister


On May 5, 2017, 3:49 p.m., Dave Barnes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59027/
> ---
> 
> (Updated May 5, 2017, 3:49 p.m.)
> 
> 
> Review request for geode, Joey McAllister and Udo Kohlmeyer.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-1996 Confusing references to "multicast" for locators ports
> 
> 
> Diffs
> -
> 
>   
> geode-docs/basic_config/config_concepts/distributed_system_member_configuration.html.md.erb
>  a06a8c81cd12260f7384a202a4a0d5643806a367 
>   geode-docs/configuring/running/firewalls_ports.html.md.erb 
> 11e4554887cbc845b881ad61959d2a4345bb0c8a 
>   
> geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
>  77fd42b9c043b613c8dcf68feda0bd49d482cd1a 
>   
> geode-docs/managing/monitor_tune/socket_communication_ephemeral_tcp_port_limits.html.md.erb
>  3df570a3859f1b49874f682b9639e642584666c2 
>   
> geode-docs/managing/monitor_tune/socket_communication_have_enough_sockets.html.md.erb
>  a075e08533e74ae986db9efde552c392cd5cce2c 
>   
> geode-docs/managing/monitor_tune/socket_communication_setting_socket_buffer_sizes.html.md.erb
>  41884a2ecc21f607a91eb8910b001be77aa1ad6a 
>   
> geode-docs/managing/monitor_tune/socket_communication_tcpip_p2p_handshake_timeouts.html.md.erb
>  486c337092382f9bde702e677ba1122583cff440 
>   geode-docs/managing/monitor_tune/sockets_and_gateways.html.md.erb 
> ca20bf81dbccaad1beaa52b064db1e1644de86e6 
>   geode-docs/managing/monitor_tune/udp_communication.html.md.erb 
> 4a5d3c0bf8f24275a4040e8f0f1926a06e990b7f 
>   geode-docs/reference/statistics/statistics_list.html.md.erb 
> 7f7b76f79e944ffc495f8974712b1c53b9863a55 
>   geode-docs/tools_modules/gfsh/command-pages/connect.html.md.erb 
> c83d2ffe92c7784b5f41b63e879a3199a26ee88a 
> 
> 
> Diff: https://reviews.apache.org/r/59027/diff/1/
> 
> 
> Testing
> ---
> 
> Corrected two references to the locator's "multicast port" as described in 
> the JIRA ticket. Searched the entire user guide, found no other occurrences. 
> In the process, corrected some typos and formatting issues, which are 
> included in this checkin to save the overhead of creating a separate ticket 
> and review cycle.
> 
> 
> Thanks,
> 
> Dave Barnes
> 
>

[jira] [Created] (GEODE-2855) Document Rename Execution.withArgs to Execution.setArguments

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2855:
--

 Summary: Document Rename Execution.withArgs to 
Execution.setArguments
 Key: GEODE-2855
 URL: https://issues.apache.org/jira/browse/GEODE-2855
 Project: Geode
  Issue Type: Sub-task
  Components: docs
Reporter: Joey McAllister
 Fix For: 1.2.0


FunctionContext has a getArguments method. withArgs should be renamed to match.

See https://issues.apache.org/jira/browse/GEODE-728



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2554) Geode incubator docs are still up

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2554:
---
Priority: Minor  (was: Major)

> Geode incubator docs are still up
> -
>
> Key: GEODE-2554
> URL: https://issues.apache.org/jira/browse/GEODE-2554
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Galen O'Sullivan
>    Assignee: Joey McAllister
>Priority: Minor
> Fix For: 1.2.0
>
>
> Search engines still direct users to the Geode incubating docs, which are at:
> https://geode.apache.org/docs/guide/basic_config/data_regions/managing_data_regions.html
> The most recent docs have an 11 in the URL:
> https://geode.apache.org/docs/guide/11/basic_config/data_regions/managing_data_regions.html
> The old docs should either be taken down, or the path made to refer to 
> whatever the latest docs are. That way visitors won't get stuck on an ever 
> increasingly stale docs site.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-1897) Users should be able to configure eviction through gfsh

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-1897:
---
Component/s: docs

> Users should be able to configure eviction through gfsh
> ---
>
> Key: GEODE-1897
> URL: https://issues.apache.org/jira/browse/GEODE-1897
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>
> While creating a region in gfsh, users should be able to configure eviction 
> for that region.
> All three modes of eviction should be supported:
> 1. Eviction driven by the resource manager:
> {noformat}
> gfsh>create region --name=myRegion --type=REPLICATE --eviction-enabled
> {noformat}
> 2. eviction driven by entry count in the region:
> {noformat}
> gfsh>create region --name=myRegion --type=REPLICATE 
> --eviction-entry-count=1000
> {noformat}
> 3. eviction driven by bytes used:
> {noformat}
> gfsh>create region --name=myRegion --type=REPLICATE --eviction-max-memory=100m
> {noformat}
> And also specify the eviction action as
> {noformat}
> --eviction-action=overflow-to-disk or
> --eviction-action=destroy
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2668) Add gfsh command to destroy gateway receiver

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2668:
---
Component/s: docs

> Add gfsh command to destroy gateway receiver
> 
>
> Key: GEODE-2668
> URL: https://issues.apache.org/jira/browse/GEODE-2668
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>
> Currently, there is a {{create gateway-receiver}} command, but no 
> corresponding destroy command.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2819) HTTP status code 414 is not documented

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2819:
---
Component/s: docs

> HTTP status code 414 is not documented
> --
>
> Key: GEODE-2819
> URL: https://issues.apache.org/jira/browse/GEODE-2819
> Project: Geode
>  Issue Type: Bug
>  Components: docs, rest (dev)
>Reporter: Michael Dodge
>
> Whilst consuming the REST API to do a "put all", we built a URI that is too 
> long and thus got a 414 HTTP status code. The documentation that we are using 
> (https://geode.apache.org/docs/guide/11/rest_apps/put_multiple_values_for_keys.html)
>  does not specify what constitutes "too long" and does not include 414 in the 
> Error Codes table at the bottom of the page. The former would be nice; the 
> latter seems necessary.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (GEODE-2103) start locator command should include --http-service-port and --http-service-bind-address

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister reopened GEODE-2103:

  Assignee: Joey McAllister  (was: Deepak Dixit)

Needs documentation updates for gfsh Commands > Start Server and Start Locator 
sections.

> start locator command should include --http-service-port and 
> --http-service-bind-address
> 
>
> Key: GEODE-2103
> URL: https://issues.apache.org/jira/browse/GEODE-2103
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, management
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>Assignee: Joey McAllister
> Fix For: 1.2.0
>
>
> To facilitate starting the Admin REST API on a Locator, start locator command 
> should include --http-service-port and --http-service-bind-address.
> Workaround is to specify these configuration properties with --J:
> --J=-Dgemfire.http-service-port=
> --J=-Dgemfire.http-service-bind-address=



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Googling Apache Geode docs results in urls Not Found

[Joey McAllister]

I've re-opened GEODE-2554 to address the redirects.

On Thu, Apr 13, 2017 at 12:43 PM Swapnil Bawaskar 
wrote:

> It's not just google, we also point users to the docs in forums, on user
> list etc. So, these links should never be broken.
> We put the javadocs, under "latest" for example
> /releases/latest/javadoc/index.html, so the link always stays current. Can
> we do something similar for the user guide as well?
>
>
>
> On Thu, Apr 13, 2017 at 12:28 PM Kirk Lund  wrote:
>
> > The old URLs should probably redirect to the greatest version number
> then,
> > right?
> >
> > Either way, we have broken URLs showing up at the top of our google
> > searches. There must be a way of telling Google to flush these out or
> > otherwise fix them.
> >
> > On Thu, Apr 13, 2017 at 12:05 PM, Michael Stolz 
> wrote:
> >
> > > On further inspection, this is due to the versioning that was added in
> > > /docs/guide.
> > > There is now a /docs/guide/10 and a /docs/guide/11 each of which
> > contains a
> > > "configuring" folder a "tools_modules" folder, etc.
> > >
> > > --
> > > Mike Stolz
> > > Principal Engineer, GemFire Product Manager
> > > Mobile: +1-631-835-4771 <(631)%20835-4771> <(631)%20835-4771>
> > >
> > > On Thu, Apr 13, 2017 at 1:40 PM, Kirk Lund  wrote:
> > >
> > > > If I google for something like "apache geode pulse Log-File-Location"
> > > then
> > > > the top few search results are broken. Is this expected or temporary?
> > > >
> > > > https://geode.apache.org/docs/guide/configuring/running/
> > > > running_the_locator.html
> > > >
> > > > Not Found
> > > > The requested URL
> /docs/guide/configuring/running/running_the_locator.
> > > html
> > > > was not found on this server.
> > > >
> > > > https://geode.apache.org/docs/guide/configuring/running/
> > > > running_the_cacheserver.html
> > > >
> > > > Not Found
> > > > The requested URL
> > > > /docs/guide/configuring/running/running_the_cacheserver.html was not
> > > found
> > > > on this server.
> > > >
> > > > https://geode.apache.org/docs/guide/tools_modules/gfsh/
> > > > configuring_gfsh.html
> > > >
> > > > Not Found
> > > > The requested URL
> /docs/guide/tools_modules/gfsh/configuring_gfsh.html
> > > was
> > > > not found on this server.
> > > >
> > > > 
> > > >
> > >
> >
>

[jira] [Reopened] (GEODE-2554) Geode incubator docs are still up

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister reopened GEODE-2554:

  Assignee: Joey McAllister  (was: Dave Barnes)

Reopening to address redirects.

> Geode incubator docs are still up
> -
>
> Key: GEODE-2554
> URL: https://issues.apache.org/jira/browse/GEODE-2554
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Galen O'Sullivan
>    Assignee: Joey McAllister
> Fix For: 1.2.0
>
>
> Search engines still direct users to the Geode incubating docs, which are at:
> https://geode.apache.org/docs/guide/basic_config/data_regions/managing_data_regions.html
> The most recent docs have an 11 in the URL:
> https://geode.apache.org/docs/guide/11/basic_config/data_regions/managing_data_regions.html
> The old docs should either be taken down, or the path made to refer to 
> whatever the latest docs are. That way visitors won't get stuck on an ever 
> increasingly stale docs site.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (GEODE-2777) Change version number from 1.1 to 1.2 in docs

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2777:
--

 Summary: Change version number from 1.1 to 1.2 in docs
 Key: GEODE-2777
 URL: https://issues.apache.org/jira/browse/GEODE-2777
 Project: Geode
  Issue Type: Task
  Components: docs
Reporter: Joey McAllister
 Fix For: 1.2.0


On the `develop` branch, change any reference to v1.1 to be v1.2 in the 
`geode-docs` and `geode-book` directories.

In the `geode-book` directory, make sure to change the hrefs in the subnav from 
`/11/` to `/12/` and make relevant version changes to the `config.yml` file.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-230) Remove deprecated AttributesFactory

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-230:
--
Component/s: docs

> Remove deprecated AttributesFactory
> ---
>
> Key: GEODE-230
> URL: https://issues.apache.org/jira/browse/GEODE-230
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Darrel Schneider
>
> Should AttributesFactory be remove since it has been deprecated since 6.5.
> In that release we started telling customers to use Cache.createRegionFactory 
> or ClientCache.createClientRegionFactory.
> However here are a couple of reasons why we might not want to get rid of 
> AttributesFactory:
> - The corresponding PartitionAttributesFactory is not deprecated.
> - We have had customers request that it not be deprecated so that they have a 
> way to create a RegionAttributes on a client, send it to the server in a 
> function, and have the function create a region using the un-deprecated 
> Cache.createRegionFactory(RegionAttributes).
> We could argue that Cache.createRegionFactory(RegionAttributes) is not 
> deprecated so that given an existing region you could get its 
> RegionAttributes by calling Region.getAttributes. But it seems reasonable to 
> want to be able to create a RegionAttributes (and its nested 
> PartitionAttributes) without needing to create the region in the same jvm 
> that is creating the attributes.
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (GEODE-2769) Document how to remove all cache listeners

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2769:
--

 Summary: Document how to remove all cache listeners
 Key: GEODE-2769
 URL: https://issues.apache.org/jira/browse/GEODE-2769
 Project: Geode
  Issue Type: Sub-task
  Components: docs
Reporter: Joey McAllister


GEODE-2236 describes how to remove all cache listeners using a gfsh command. 
This should be documented in the user guide.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-288) Remove deprecated Admin API

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-288:
--
Component/s: (was: docs)

> Remove deprecated Admin API
> ---
>
> Key: GEODE-288
> URL: https://issues.apache.org/jira/browse/GEODE-288
> Project: Geode
>  Issue Type: Sub-task
>  Components: jmx
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> The Admin API (com.gemstone.gemfire.admin) and old JMX Agent have been 
> deprecated since GemFire 7.0. The Admin API was retired in favor of using the 
> new Management JMX API (com.gemstone.gemfire.management) and GFSH.
> #1) move some Admin classes used internally by non-Admin code:
> move com.gemstone.gemfire.admin.BackupStatus
> move com.gemstone.gemfire.admin.OperationCancelledException
> move com.gemstone.gemfire.admin.RegionNotFoundException
> move 
> com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.backupAllMembers
> move 
> com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.compactAllDiskStores
> move com.gemstone.gemfire.admin.internal.FinishBackupRequest
> move com.gemstone.gemfire.admin.internal.FlushToDiskRequest
> move com.gemstone.gemfire.admin.internal.InetAddressUtil
> move com.gemstone.gemfire.admin.internal.PrepareBackupRequest
> #2) move com.gemstone.gemfire.admin to 
> com.gemstone.gemfire.internal.admin.api (temporarily)
> #3) remove com.gemstone.gemfire.cache.* usage of admin
> #4) remove com.gemstone.gemfire.distributed.* usage of admin
> #5) remove com.gemstone.gemfire.internal.* usage of admin (except for 
> internal.admin.*)
> #6) remove com.gemstone.gemfire.management.* usage of admin
> #7) remove com.gemstone.gemfire.internal.admin.api if possible
> #8) remove unused classes from com.gemstone.gemfire.internal.admin.*
> Breakdown by package and class:
> com.gemstone.gemfire
>   --change DataSerializer to use moved RegionNotFoundException
> com.gemstone.gemfire.cache
> com.gemstone.gemfire.cache.persistence
> com.gemstone.gemfire.cache.util
>   --remove com.gemstone.gemfire.cache.util.UniversalMembershipListenerAdapter
> com.gemstone.gemfire.distributed
>   --remove Admin API from javadocs in Locator and DistributedSystem
> com.gemstone.gemfire.distributed.internal
>   --remove 
> com.gemstone.gemfire.distributed.internal.DistributionManager.createHealthMonitor
>   --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitor
>   --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitorImpl
>   --change 
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.hasAlertListenerFor
>  to not use AlertLevel
> com.gemstone.gemfire.internal
>   --remove DSFIDFactory support for admin messages
>   --remove com.gemstone.gemfire.admin.jmx.internal.AgentLauncher from 
> GemFireUtilLauncher
>   --change MigrationServer to use moved InetAddressUtil
>   --change SocketCreator to use moved InetAddressUtil
>   --remove SystemAdmin.backup
>   --remove SystemAdmin.compactAllDiskStores
>   --remove SystemAdmin.shutDownAll
>   --remove SystemAdmin.listMissingDiskStores
>   --remove SystemAdmin.revokeMissingDiskStores
> com.gemstone.gemfire.internal.cache
>   --replace use of com.gemstone.gemfire.admin.OperationCancelledException
>   --remove use of 
> com.gemstone.gemfire.admin.internal.SystemMemberCacheEventProcessor
> com.gemstone.gemfire.internal.cache.partitioned
>   --replace use of com.gemstone.gemfire.admin.OperationCancelledException
> com.gemstone.gemfire.internal.cache.snapshot
>   --replace use of com.gemstone.gemfire.admin.RegionNotFoundException
> com.gemstone.gemfire.internal.tools.gfsh.app.command.task
>   --reimplement PartitionedRegionAttributeTask
> com.gemstone.gemfire.internal.tools.gfsh.util
>   --reimplement RegionUtil
> com.gemstone.gemfire.management.internal.beans
>   --change DistributedSystemBridge to use moved classes
> com.gemstone.gemfire.management.internal.cli.commands
>   --change DiskStoreCommands to use moved classes
>   



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEODE-2554) Geode incubator docs are still up

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister reassigned GEODE-2554:
--

Assignee: (was: Joey McAllister)

> Geode incubator docs are still up
> -
>
> Key: GEODE-2554
> URL: https://issues.apache.org/jira/browse/GEODE-2554
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Galen O'Sullivan
>
> Search engines still direct users to the Geode incubating docs, which are at:
> https://geode.apache.org/docs/guide/basic_config/data_regions/managing_data_regions.html
> The most recent docs have an 11 in the URL:
> https://geode.apache.org/docs/guide/11/basic_config/data_regions/managing_data_regions.html
> The old docs should either be taken down, or the path made to refer to 
> whatever the latest docs are. That way visitors won't get stuck on an ever 
> increasingly stale docs site.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: New Committer And PMC Member: Ernest Burghardt

[Joey McAllister]

Woot! Congrats, Ernie!

On Fri, Mar 24, 2017 at 3:03 PM Anthony Baker  wrote:

> The Apache Geode Project Management Committee has invited Ernest
> Burghardt to be committer on the project and join the Geode PMC. We
> are pleased to announce he has accepted.
>
> Please join me in welcoming Ernie!
>
> Thanks,
>
> Anthony
> On behalf of the Apache Geode PMC
>

[jira] [Updated] (GEODE-2480) Need to specify correct version of CMake required for building Native Client

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2480:
---
Component/s: (was: docs)

> Need to specify correct version of CMake required for building Native Client
> 
>
> Key: GEODE-2480
> URL: https://issues.apache.org/jira/browse/GEODE-2480
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Akihiro Kitada
>
> According to the following doc, the version of CMake required for building 
> Native Client is *4.3* or newer.
> https://github.com/apache/geode-native/blob/develop/BUILDING.md
> However, the latest stable version of CMake is 3.7.2 as of now. Please 
> specify the correct version of CMake (it could be "*3.4* or newer" ?).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: for discussion: separate website into its own repo

[Joey McAllister]

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

Re: Requesting more JIRA permission

[Joey McAllister]

+1

On Wed, Feb 15, 2017 at 4:36 PM Swapnil Bawaskar 
wrote:

> +1
>
> On Wed, Feb 15, 2017 at 4:29 PM Jared Stewart  wrote:
>
> > +1
> >
> > > On Feb 15, 2017, at 4:27 PM, Michael William Dodge 
> > wrote:
> > >
> > > +1
> > >
> > >> On 15 Feb, 2017, at 16:17, Addison Huddy  wrote:
> > >>
> > >> Hello Apache Geode Community,
> > >>
> > >> I'm writing to request a higher level of permission on JIRA tickets in
> > an
> > >> effort to increase organization and clarity within our community.
> > >>
> > >> As we grow our community and focus our mutual development efforts, it
> is
> > >> important to stay organized. For example:
> > >>
> > >>  - how we organize jira's and sub-jiras
> > >>  - Updating the status of a ticket
> > >>  - What we call the ticket so that it is informative
> > >>
> > >> In my daily work on Geode at Pivotal Inc, I find myself wanting to
> > organize
> > >> things within the community, but don't have the permissions to edit
> > tickets
> > >> besides by own.
> > >>
> > >> I fully recognize that with more ticket permissions comes a greater
> > >> responsibility to communicate with the community and uphold our
> > democratic
> > >> model.  I will make sure to keep and promote these values.
> > >>
> > >> *Please +1 this request if you agree to increase my JIRA permissions
> so
> > I
> > >> can edit JIRAs.*
> > >>
> > >> Thanks,
> > >> Addison
> > >
> >
> >
>

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

[Joey McAllister]

That's correct, Dan. Regardless of what goes out in this build, we can
update the website docs to include these fixes before we announce the new
release.

On Fri, Feb 10, 2017 at 3:21 PM Dan Smith  wrote:

> I don't think we should be too concerned about incubating reference in
> BUILDING.md or those docker files.
>
> The docs are a little more concerning, but I think what's probably more
> important is fixing the manual that's up on the the website. As far as I
> know building and updating the manual is a manual process and not tied to
> the release. Or has that changed? I don't see anything in a release steps
> about that.
>
> -Dan
>
> On Fri, Feb 10, 2017 at 1:59 PM, Galen M O'Sullivan  >
> wrote:
>
> > Good catch, Ken. It looks like the Dockerfile and Docker scripts refer to
> > 'incubat*', and a few places in the docs do as well.
> >
> > On Fri, Feb 10, 2017 at 1:35 PM, Kenneth Howe  wrote:
> >
> > > +0
> > > I’m not going to give an outright down-vote, but BUILDING.md needs to
> be
> > > updated to refer to the correct versions.
> > >
> > > The build steps show the expected response to
> > >   gfsh version
> > > to be "v1.0.0-incubating”
> > >
> > > It’s not great to show the wrong version, but since this is the first
> > > release since graduation showing an incorrect “incubating” version tag
> is
> > > particularly disturbing. I’d hate to confuse any new users kicking the
> > > tires on geode now that it’s an Apache TLP.
> > >
> > > Ken
> > >
> > > > On Feb 9, 2017, at 12:55 PM, Hitesh Khamesra
> > 
> > > wrote:
> > > >
> > > > All,
> > > >
> > > > This is the second release candidate of the first release for Apache
> > > Geode, version 1.1.0.
> > > > Thanks to all the community members.
> > > >
> > > > It fixes the following issues:
> > > >https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12318420=12338352
> > > >
> > > >
> > > > *** Please download, test and vote by Tuesday, February 14, 0800 hrs
> US
> > > Pacific.
> > > >
> > > > Note that we are voting upon the source (tag):
> > > >rel/v1.1.0.RC2
> > > >https://git-wip-us.apache.org/repos/asf?p=geode.git;a=tag;h=
> > > refs/tags/rel/v1.1.0.RC2
> > > >
> > > > Commit ID: 2286fd064a52173eab8fdcfadfb89a01e81ef728
> > > >
> > > > Source and binary files:
> > > >https://dist.apache.org/repos/dist/dev/geode/1.1.0.RC2/
> > > >
> > > > Maven staging repo:
> > > >https://repository.apache.org/content/repositories/
> > > orgapachegeode-1016/
> > > >
> > > > Geode's KEYS file containing PGP keys we use to sign the release:
> > > >https://github.com/apache/geode/blob/release/1.1.0/KEYS
> > > >
> > > > pub   4096R/AC6AB8ED 2017-01-18
> > > >   Key fingerprint = 048F B40F AD7D 9C15 54AD  D447 2CA9 90A2 AC6A
> > > B8ED
> > > >
> > > > Thanks,
> > > > Hitesh
> > >
> > >
> >
>

Re: [GitHub] geode pull request #380: GEODE-2409: Beautify readme

[Joey McAllister]

+1 - Looks great, Jared!

On Wed, Feb 1, 2017 at 11:34 AM jaredjstewart  wrote:

> GitHub user jaredjstewart opened a pull request:
>
> https://github.com/apache/geode/pull/380
>
> GEODE-2409: Beautify readme
>
>  - Add Apache Geode banner image
>  - Add badges for the latest version in Maven Central and for the
> Apache 2.0 license
>  - Improve formatting for the table of contents
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/jaredjstewart/geode GEODE-2409
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/geode/pull/380.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 #380
>
> 
> commit e178898c776bae920e5ccedf4b700b6b3989eb86
> Author: Jared Stewart 
> Date:   2017-02-01T19:30:50Z
>
> GEODE-2409: Beautify readme
>
> 
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

[jira] [Updated] (GEODE-2267) Add gfsh command to export all cluster artifacts

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2267:
---
Component/s: (was: docs)

> Add gfsh command to export all cluster artifacts
> 
>
> Key: GEODE-2267
> URL: https://issues.apache.org/jira/browse/GEODE-2267
> Project: Geode
>  Issue Type: New Feature
>  Components: configuration, gfsh
>Reporter: Diane Hardman
>  Labels: ExportClusterArtifacts, export, gfsh, logging, statistics
>
> We would like a single gfsh command to collect and export all logfiles and 
> stat files into a single package. This package (zipfile) can then be saved 
> and attached to emails and Jira tickets to help evaluate the Geode cluster 
> status.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Assigned] (GEODE-2300) Document default names for start locator/server

[Joey McAllister]

+1

On Wed, Jan 25, 2017 at 4:51 PM Dave Barnes (JIRA) <j...@apache.org> wrote:

>
>  [
> https://issues.apache.org/jira/browse/GEODE-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Dave Barnes reassigned GEODE-2300:
> --
>
> Assignee: Dave Barnes
>
> > Document default names for start locator/server
> > ---
> >
> > Key: GEODE-2300
> > URL: https://issues.apache.org/jira/browse/GEODE-2300
> > Project: Geode
> >  Issue Type: Sub-task
> >  Components: docs
> >Reporter: Joey McAllister
> >Assignee: Dave Barnes
> > Fix For: 1.1.0
> >
> >
> > Documentation for GEODE-182
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

[jira] [Updated] (GEODE-2282) Provide ability to sort field while creating pdxType for jSON document(Need to document system property)

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2282:
---
Assignee: (was: Joey McAllister)

> Provide ability to sort field while creating pdxType for jSON document(Need 
> to document system property)
> 
>
> Key: GEODE-2282
> URL: https://issues.apache.org/jira/browse/GEODE-2282
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Hitesh Khamesra
> Fix For: 1.1.0
>
>
> There is the possibility that same JSON document can create multiple pdxType 
> ids, if different JSON docs contain same fields in different order. Thus sort 
> those field while creating the pdxType id. Introduce system property to 
> enable this feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-2353) Verify no clear-text passwords in documentation

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2353:
--

 Summary: Verify no clear-text passwords in documentation
 Key: GEODE-2353
 URL: https://issues.apache.org/jira/browse/GEODE-2353
 Project: Geode
  Issue Type: Sub-task
  Components: docs
Reporter: Joey McAllister
 Fix For: 1.1.0


Find locations in the manual where notes were made that the password is 
recorded or available in clear text, and remove them. GEODE-2119 ticket fixed 
all of them. Passwords are no longer seen in clear text.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-2300) Document default names for start locator/server

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2300:
---
Fix Version/s: 1.1.0

> Document default names for start locator/server
> ---
>
> Key: GEODE-2300
> URL: https://issues.apache.org/jira/browse/GEODE-2300
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>    Reporter: Joey McAllister
> Fix For: 1.1.0
>
>
> Documentation for GEODE-182



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Native Client Directory Structure

[Joey McAllister]

+1 to the separate repo.

I think it also makes sense—especially with independent release
schedules—to keep the client documentation source in the client repo and
build it as its own User Guide, which we can host in its own section on
geode.apache.org/docs/.

On Mon, Jan 16, 2017 at 12:14 PM Udo Kohlmeyer 
wrote:

+1 to separate client repos. Or at least some ability to independently
version client code for releases.

--Udo


On 1/16/17 11:56, Jacob Barrett wrote:
> +1 for separate repo for sub-projects that would or could likely release
> independently of the core project. I see this applying to most clients,
> .net, c++, python, etc. It also cleanly separates out the build process
> which is quite different between these projects. The native clients in
> particular are dependent a on bunch of toolchains that aren't part of the
> standard core developer's toolbox. Even if released together under the
> umbrella of the Geode product it may still make sense to let them evolve
> independently in their own repos to isolate the concerns between the
> sources.
>
>
>
> On Mon, Jan 16, 2017 at 11:52 AM Anthony Baker  wrote:
>
>> I’m cautiously in favor of this idea.  Allowing independent parts (geode,
>> geode-examples, geode-native) to progress and release at their own pace
>> seems like a good thing.
>>
>>  From a release perspective, I think each repo would have separate vote
>> threads and a section on our release page:
>> http://geode.apache.org/releases/
>>
>> Anthony
>>
>>> On Jan 16, 2017, at 11:24 AM, Jacob Barrett  wrote:
>>>
>>> I would love a separate repo. Someone told me that wasn't an option. If
>>> it's an option the let's make it so.
>>>
>>> On Mon, Jan 16, 2017 at 11:20 AM Mark Bretl  wrote:
>>>
 Jake,

 Having all the clients in the repository is nice, however, has there
>> been
 thought to have them in their own repository? Now that we are a TLP, we
>> do
 have that capability, as seen with the 'geode-examples' repository.

 --Mark

 On Mon, Jan 16, 2017 at 10:38 AM, Udo Kohlmeyer 
 wrote:
>>

Re: [GitHub] geode pull request #334: Feature/geode 2031

[Joey McAllister]

Thanks, Karen. Let me know if you have any questions.

On Mon, Jan 16, 2017 at 11:56 AM Karen Miller  wrote:

> I'm going to pull this in and then update Geode web page.
>
>
> On Wed, Jan 11, 2017 at 4:50 PM, joeymcallister 
> wrote:
>
> > Github user joeymcallister commented on a diff in the pull request:
> >
> > https://github.com/apache/geode/pull/334#discussion_r95706396
> >
> > --- Diff: geode-book/README.md ---
> > @@ -63,30 +63,19 @@ For Geode, a preconfigured **book** is provided
> in
> > the directory `{geode-project
> >
> > You can now view the local documentation at <
> http://localhost:9292
> > >.
> >
> > -## Embedding the User Guide in the Geode Website
> > +## Publishing the User Guide to the Geode Website
> >
> > -Once you have reviewed your local build of the User Guide, you can
> > embed it in the Apache Geode website by doing the following:
> > +Once you have reviewed your local build of the User Guide, you can
> > move it in the Apache Geode website by doing the following:
> > --- End diff --
> >
> > Good catch. Thank you!
> >
> >
> > ---
> > If your project is set up for it, you can reply to this email and have
> your
> > reply appear on GitHub as well. If your project does not have this
> feature
> > enabled and wishes so, or if the feature is enabled but not working,
> please
> > contact infrastructure at infrastruct...@apache.org or file a JIRA
> ticket
> > with INFRA.
> > ---
> >
>

[jira] [Updated] (GEODE-2300) Document default names for start locator/server

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2300:
---
Issue Type: Sub-task  (was: Task)
Parent: GEODE-182

> Document default names for start locator/server
> ---
>
> Key: GEODE-2300
> URL: https://issues.apache.org/jira/browse/GEODE-2300
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>    Reporter: Joey McAllister
>
> Documentation for GEODE-182



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-2300) Document default names for start locator/server

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2300:
--

 Summary: Document default names for start locator/server
 Key: GEODE-2300
 URL: https://issues.apache.org/jira/browse/GEODE-2300
 Project: Geode
  Issue Type: Task
  Components: docs
Reporter: Joey McAllister


Documentation for GEODE-182



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Hosted API docs update?

[Joey McAllister]

My pull request  (for GEODE-2031) changes the Docs page to include more
than just the most recent release of the User Guide (e.g., when we release
Apache Geode 1.1., the User Guide for Apache Geode 1.0 will still be
available from the Docs page). Do we also want to archive the API
documentation, so the Apache Geode 1.0 APIs are still available when we
push Apache Geode 1.1?

On Fri, Jan 13, 2017 at 10:30 AM Dave Barnes <dbar...@pivotal.io> wrote:

My message crossed paths with Swapnil's. I think what Sai noticed was that
the title of the API docs still says "incubating", which I find to be true
of the "latest" release to which Swap points. So I think there's still a
need for a freshly-generated set of Javadocs.


On Fri, Jan 13, 2017 at 10:25 AM, Dave Barnes <dbar...@pivotal.io> wrote:

> Hi Sai,
> I filed a JIRA ticket on this a couple of weeks ago: GEODE-2264.
> First obstacle I encountered was that the Gradle builds that update
> Javadocs do so component-by-component, so task number 1 would be to create
> a single Geode-wide Javadoc tree. Once that's in place, it's just a matter
> of updating the website. (The website procedure is in the midst of a
change
> - Joey McAllister has a PR pending on the subject.)
> -Dave
>
> On Fri, Jan 13, 2017 at 10:05 AM, Sai Boorlagadda <
> sai.boorlaga...@gmail.com> wrote:
>
>> Any pointers on how to update hosted API documentation?
>> http://geode.apache.org/releases/latest/javadoc/index.html
>>
>> Sai
>>
>
>

Apache Geode JIRA maintenance

[Joey McAllister]

FYI:

"update: issues.a.o is currently rebuilding Jira indexes and will be
unavailable until it's completed. ETA is 4 hours"
10:27 AM PT - 11 Jan 2017
https://twitter.com/infrabot/status/819249283618766848

[jira] [Updated] (GEODE-2031) Host documentation for releases

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2031:
---
Priority: Minor  (was: Major)

> Host documentation for releases
> ---
>
> Key: GEODE-2031
> URL: https://issues.apache.org/jira/browse/GEODE-2031
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Anthony Baker
>    Assignee: Joey McAllister
>Priority: Minor
> Fix For: 1.1.0
>
>
> Currently we overwrite documentation hosted on geode.apache.org with every 
> release.  We should allow a user to browse the documentation (user guide + 
> javadocs) for past releases, not just the most recent release.
> Improvement:
> 1) The documentation page always points to the docs for the latest release.
> 2) There is a documentation link associated with each release just like we do 
> release links for source and binary artifacts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: dev e-mail archives down?

[Joey McAllister]

It's up for me now, Mike. Is it still down for you, or was it just a hiccup?

On Tue, Jan 10, 2017 at 8:47 AM Michael Stolz  wrote:

> I tried to click on the link for the dev archives which sent me to this
> url:
>
> http://markmail.org/search/?q=list%3Aorg.apache.geode.dev+order%3Adate-backward
> but that site is not reachable.
>
> It actually appears that markmail.org itself is unreachable.
>

Re: The next release (v1.1.0)

[Joey McAllister]

Re: 2) I'll take a look at GEODE-2031, versioning the documentation.

On Mon, Jan 9, 2017 at 9:50 AM Anthony Baker  wrote:

> Updates:
>
> 1) I did a first round of changes on GEODE-2142, should be enough for
> v1.1.0.
> 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
> 3) Are there other open issues that should be included in the release?
> 4) Last call for a release manager…  :-)
>
> Thanks,
> Anthony
>
>
> > On Jan 6, 2017, at 10:13 AM, Anthony Baker  wrote:
> >
> > Our last release was on October 25.  I think we’re past due for another
> one!  We’ve had lots of great contributions since 1.0.0-incubating and now
> that we’re are a top-level project we can drop the “-incubating” qualifier.
> >
> > I reviewed our open JIRA issues and would like to include the following
> in the release:
> >
> > GEODE-2142 - JSON license incompatibility
> >   We can update the NOTICE files and leave the JSON dependency alone
> (as long as we do another release before April 30).
> >
> > GEODE-1965 - backwards compatibility tests
> >   I’d like to make sure we haven’t broken anything since our last
> release.
> >
> > GEODE-2031 - versioned documentation
> >   Seems relatively straightforward?
> >
> > The remaining issues that are tagged with v1.1.0 [1] could be pushed to
> a following release IMO.  Thoughts?
> >
> > Regarding the release manager, I can do the dirty work if no one else
> wants to volunteer :-)
> >
> > Anthony
> >
> > [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> >> On Nov 21, 2016, at 9:26 AM, Anthony Baker  wrote:
> >>
> >> Now that graduation is done (!!), we need to organize our next
> release.  I propose we focus on completing the transition to TLP and
> cleaning up “incubating" references.  The sequence would look something
> like this:
> >>
> >> 1) Transition the git repo, mailing lists, etc.
> >> 2) Update incubating references in source, docs, website, wiki, …
> >> 3) Do a release.
> >>
> >> Thoughts?
> >>
> >> We need a release manager.  Any volunteers?
> >>
> >> Also, we need to rename the JIRA version from 1.1.0-incubating to
> 1.1.0.  Can someone with JIRA karma help?
> >>
> >> Anthony
> >>
> >
>
>

[jira] [Updated] (GEODE-2281) can not create redis server as the document describle

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2281:
---
Component/s: docs

> can not create redis server  as the document describle
> --
>
> Key: GEODE-2281
> URL: https://issues.apache.org/jira/browse/GEODE-2281
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: netroby
>
> gfsh> start server --name=server1 --redis-bind-address=localhost
>  --redis-port=11211 --J=-Dgemfireredis.regiontype=PARTITION_PERSISTENT
> Starting a Geode Server in 
> /home/huzhifeng/workspace/geode-demo/apache-geode-1.0.0-incubating/server1...
> The Cache Server process terminated unexpectedly with exit status 1. Please 
> refer to the log file in 
> /home/huzhifeng/workspace/geode-demo/apache-geode-1.0.0-incubating/server1 
> for full details.
> Exception in thread "main" java.lang.RuntimeException: An IO error occurred 
> while starting a Server in 
> /home/huzhifeng/workspace/geode-demo/apache-geode-1.0.0-incubating/server1 on 
> 172.17.0.1[40404]: Network is unreachable; port (40404) is not available on 
> localhost.
> at 
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:735)
> at 
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:633)
> at 
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:184)
> Caused by: java.net.BindException: Network is unreachable; port (40404) is 
> not available on localhost.
> at 
> org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:127)
> at 
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:688)
> ... 2 more
> http://geode.apache.org/docs/guide/tools_modules/redis_adapter.html
> I download the latest geode binary distribute



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: geode-examples vs geode/geode-examples

[Joey McAllister]

+1 to moving the existing examples from the module to the new repo and then
editing/replacing them as appropriate.

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
>

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

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


On Dec. 29, 2016, 11:58 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55093/
> ---
> 
> (Updated Dec. 29, 2016, 11:58 p.m.)
> 
> 
> 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
> 
>

[jira] [Updated] (GEODE-2256) Create Colocation Example

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2256:
---
Priority: Minor  (was: Major)

> Create Colocation Example
> -
>
> Key: GEODE-2256
> URL: https://issues.apache.org/jira/browse/GEODE-2256
> Project: Geode
>  Issue Type: New Feature
>  Components: docs
>    Reporter: Joey McAllister
>Priority: Minor
>
> Mike Stolz recommended on the Geode User list that "We should make a generic 
> implementation of what Udo described here as part of the Geode examples. It's 
> such a frequently used pattern."
> Here is the original request from Amit Pandey:
> {quote}
> I saw that in order to co locate different caches  you can use 
> "colocated-with" attribute.
> However how does Spring or Geode determine (based on which attributes ) that 
> they will be collocated.  Lets say two regions containing Customer and 
> Account needs to be collocated. I want to use the accountPK present in both 
> classes for collocation and not on other attributes which might have the same 
> name (to give an artificial example lets say there is a "status" attribute 
> which is Y in both but which I dont want to be used for determining 
> collocation.  
> {quote}
> And here is Udo's response:
> {quote}
> Colocation works by making sure that the same buckets are placed on the
> same server. It works in a parent-child relationship. Where RegionB is
> colocated with RegionA.
> For colocation to work you either need to use the same key or a
> PartitionResolver. A PartitionResolver is a custom impl that provides
> the mechanism, that determines what bucket each entry is put into, a way
> to make sure that entries for RegionB get the same bucket as the
> colocated entry in RegionA.
> Be very careful that the PartitionResolver uses the key only and not the
> value.
> In your case I'm sure that an Account would have reference to its
> parent, the customer. So I would use the customerKey for the colocation.
> Remember that keys can be "complex". i.e Have an accountID and a
> customerID. If you make the complex object have it's hashCode and equals
> point at the accountID then it will behave the same way as you would if
> you only used the accountID. Then, with the customerID being present in
> the complex accountID, you could then have a partitionResolver on the
> the Accounts region that would return the customerID (which would then
> be the same key that you used for the customer in your Customer region).
> Which means any account that is entered will be colocated with its
> customer information.
> In short, if you make sure that the mechanism that determines the bucket
> number always returns the same bucket number for colocated objects,
> related data will be stored on the same server.
> http://geode.apache.org/docs/guide/developing/partitioned_regions/using_custom_partition_resolvers.html
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-2256) Create Colocation Example

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-2256:
--

 Summary: Create Colocation Example
 Key: GEODE-2256
 URL: https://issues.apache.org/jira/browse/GEODE-2256
 Project: Geode
  Issue Type: New Feature
  Components: docs
Reporter: Joey McAllister


Mike Stolz recommended on the Geode User list that "We should make a generic 
implementation of what Udo described here as part of the Geode examples. It's 
such a frequently used pattern."

Here is the original request from Amit Pandey:
{quote}
I saw that in order to co locate different caches  you can use "colocated-with" 
attribute.

However how does Spring or Geode determine (based on which attributes ) that 
they will be collocated.  Lets say two regions containing Customer and Account 
needs to be collocated. I want to use the accountPK present in both classes for 
collocation and not on other attributes which might have the same name (to give 
an artificial example lets say there is a "status" attribute which is Y in both 
but which I dont want to be used for determining collocation.  
{quote}

And here is Udo's response:

{quote}
Colocation works by making sure that the same buckets are placed on the
same server. It works in a parent-child relationship. Where RegionB is
colocated with RegionA.

For colocation to work you either need to use the same key or a
PartitionResolver. A PartitionResolver is a custom impl that provides
the mechanism, that determines what bucket each entry is put into, a way
to make sure that entries for RegionB get the same bucket as the
colocated entry in RegionA.

Be very careful that the PartitionResolver uses the key only and not the
value.

In your case I'm sure that an Account would have reference to its
parent, the customer. So I would use the customerKey for the colocation.
Remember that keys can be "complex". i.e Have an accountID and a
customerID. If you make the complex object have it's hashCode and equals
point at the accountID then it will behave the same way as you would if
you only used the accountID. Then, with the customerID being present in
the complex accountID, you could then have a partitionResolver on the
the Accounts region that would return the customerID (which would then
be the same key that you used for the customer in your Customer region).
Which means any account that is entered will be colocated with its
customer information.

In short, if you make sure that the mechanism that determines the bucket
number always returns the same bucket number for colocated objects,
related data will be stored on the same server.

http://geode.apache.org/docs/guide/developing/partitioned_regions/using_custom_partition_resolvers.html
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


On Dec. 27, 2016, 11:04 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55059/
> ---
> 
> (Updated Dec. 27, 2016, 11:04 p.m.)
> 
> 
> 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
> 
>

[jira] [Resolved] (GEODE-2134) Doc update of schema location

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister resolved GEODE-2134.

   Resolution: Duplicate
Fix Version/s: 1.1.0

Resolved in GEODE-2135 (https://issues.apache.org/jira/browse/GEODE-2135)

> Doc update of schema location 
> --
>
> Key: GEODE-2134
> URL: https://issues.apache.org/jira/browse/GEODE-2134
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Karen Smoler Miller
> Fix For: 1.1.0
>
>
> Throughout the documentation, update the schema location to be
> {{http://geode.apache.org/schema/cache/cache-1.0.xsd}}
> Incorrect location uses {{geode.incubator.apache.org}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-2138) gfsh 'start' reports 'GemFire Version'

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-2138:
---
Component/s: (was: docs)

> gfsh 'start' reports 'GemFire Version'
> --
>
> Key: GEODE-2138
> URL: https://issues.apache.org/jira/browse/GEODE-2138
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Dave Barnes
>Assignee: Nilkanth Patel
>Priority: Minor
>
> The gfsh 'start locator' and 'start server' commands report 'GemFire version' 
> followed by a Geode version string. For example:
> $ start locator --name=locator1
> Starting a Geode Locator in /Users/dbarnes/my_geode/locator1...
> ...
> Locator in /Users/dbarnes/my_geode/locator1 on 192.168.1.80[10334] as 
> locator1 is currently online.
> Process ID: 1327
> Uptime: 4 seconds
> GemFire Version: 1.1.0-SNAPSHOT



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-536) Remove i18n code

[Joey McAllister (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783357#comment-15783357
 ] 

Joey McAllister commented on GEODE-536:
---

Found no "i18n" references in user guide, and so removed `docs` component.

> Remove i18n code
> 
>
> Key: GEODE-536
> URL: https://issues.apache.org/jira/browse/GEODE-536
> Project: Geode
>  Issue Type: Task
>  Components: logging
>Reporter: Roman Shtykh
>Priority: Minor
>
> i18n is not needed. No plans to support it so far.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-536) Remove i18n code

[Joey McAllister (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joey McAllister updated GEODE-536:
--
Component/s: (was: docs)

> Remove i18n code
> 
>
> Key: GEODE-536
> URL: https://issues.apache.org/jira/browse/GEODE-536
> Project: Geode
>  Issue Type: Task
>  Components: logging
>Reporter: Roman Shtykh
>Priority: Minor
>
> i18n is not needed. No plans to support it so far.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


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 54499: GEODE-2092 Update docs with security examples location

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


On Dec. 7, 2016, 8:59 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54499/
> ---
> 
> (Updated Dec. 7, 2016, 8:59 p.m.)
> 
> 
> 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 54385: GEODE-2180 Autoreconnect with API configuration detail

[Joey McAllister]

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


Fix it, then Ship it!




Fix, then ship!


geode-docs/managing/autoreconnect/member-reconnect.html.md.erb (line 27)
<https://reviews.apache.org/r/54385/#comment228712>

This seems a little awkward. Perhaps:

> "and, by default, automatically restarts into"



geode-docs/managing/autoreconnect/member-reconnect.html.md.erb (line 46)
<https://reviews.apache.org/r/54385/#comment228715>

by setting the property to



geode-docs/managing/autoreconnect/member-reconnect.html.md.erb (line 52)
<https://reviews.apache.org/r/54385/#comment228716>

    setting the property to


- Joey McAllister


On Dec. 5, 2016, 6:57 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54385/
> ---
> 
> (Updated Dec. 5, 2016, 6:57 p.m.)
> 
> 
> Review request for geode, Bruce Schuchardt, Dave Barnes, Joey McAllister, and 
> Kirk Lund.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Autoreconnect assumes valid XML configuration (from the
> default use of the cluster config svc).  That doesn't
> work if the cache is configured using API calls.  So,
> document this, and suggest disabling either default use
> of autoreconnect or default use of the cluster configuration
> service.
> 
> 
> Diffs
> -
> 
>   geode-docs/managing/autoreconnect/member-reconnect.html.md.erb 
> 916d301a523f052efe83c33fa318898bc75273e5 
> 
> Diff: https://reviews.apache.org/r/54385/diff/
> 
> 
> Testing
> ---
> 
> gradle rat check passes
> 
> Book builds with no broken links.
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

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

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


On Dec. 3, 2016, 4:33 p.m., Anthony Baker wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54321/
> ---
> 
> (Updated Dec. 3, 2016, 4:33 p.m.)
> 
> 
> Review request for geode, Dave Barnes, Dick Cavender, Joey McAllister, Karen 
> Miller, Mark Bretl, and Dan Smith.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> - Remove DISCLAIMER files
> - Remove "(incubating)" from project name references
> - Remove .incubator from website references
> 
> GEODE-2156: Update mailing list references
> 
> 
> GEODE-2156: Remove incubating references from the website
> 
> 
> GEODE-2156: Update repo references
> 
> 
> GEODE-2156: Fix documentation link
> 
> 
> GEODE-2156: Cleaned up nav bar links
> 
> 
> GEODE-2156: Replace incubator egg with ASF feather logo
> 
> 
> Diffs
> -
> 
>   .travis.yml e61cde51b8bee2667a6c2b1ab49c69ea20b440fe 
>   BUILDING.md 5e1e7933c59ea66211cf290191ab1f8cef8b2afd 
>   DISCLAIMER PRE-CREATION 
>   NOTICE 4801b2aedf4f254c85cba9f27d2f99d2ca2e046b 
>   README.md 955d45f4f5dd4b95f84dd89d7fcf1108678c5ae8 
>   dev-tools/docker/base/Dockerfile 1cce0ddb0d29c9e188d27481c82123e357c5b685 
>   dev-tools/docker/compile/Dockerfile 
> 6ae343a70eccf7cc4b303228118cee0b8579e79a 
>   dev-tools/docker/docs/Dockerfile 8ce7397efb584ceb3ef032d26f13795e328971fc 
>   docker/Dockerfile a42b47a3328dfff981786ce113f927888e45763a 
>   geode-assembly/src/main/dist/DISCLAIMER PRE-CREATION 
>   geode-assembly/src/main/dist/NOTICE 
> 83d0f3313a01881c9c651077036c17f962cd38b9 
>   geode-book/README.md d69354bce6fa684d635b1c03643638c7dee33251 
>   geode-book/config.yml bbc8ccc2bdffdc5a16134993ebd0683ba71e6d11 
>   geode-book/redirects.rb 81f27c834f78a5b188bb5556bfc93645fbe73262 
>   
> geode-core/src/main/java/org/apache/geode/cache/partition/PartitionListenerAdapter.java
>  b56cdf3547811cbae0b3716b83c4d2fe56b51541 
>   
> geode-core/src/main/java/org/apache/geode/internal/i18n/LocalizedStrings.java 
> 59231232bb85df22e3ca30b1bec338ef0ae033cb 
>   geode-docs/about_geode.html.md.erb 0d7f9b8d9ebe80d8b6a904e584fb76ba9fa6e66b 
>   geode-docs/getting_started/installation/install_standalone.html.md.erb 
> 9a1987e0de5b5f821d0dfc55a113e39fe80f65db 
>   geode-examples/README.md 62666035ab1bde5f9d5548e887e0133f006c2ef9 
>   geode-pulse/src/main/webapp/DataBrowser.html 
> a01df6b280decf8acd96ff6ad2f7a494a53ae682 
>   geode-pulse/src/main/webapp/Login.html 
> f093e38082a1b58a81ba936582599d28e3d2e585 
>   geode-pulse/src/main/webapp/META-INF/NOTICE 
> 706eda265cf0b54c73d01df85c0a79bde9082d8a 
>   geode-pulse/src/main/webapp/MemberDetails.html 
> bc946da8b175d23d9eba529663e1bb86c036079b 
>   geode-pulse/src/main/webapp/QueryStatistics.html 
> 543e003a0b0c447e3fe8d8e6e44d0329a168b029 
>   geode-pulse/src/main/webapp/clusterDetail.html 
> b1fc1e0a24821e40bd08a62ad53b0324102ac03c 
>   geode-pulse/src/main/webapp/regionDetail.html 
> 711ef31bd6f22636420cccd20308b4f7ac7cc769 
>   geode-site/website/README.md 56b6aeb4ab34359ffd771ce21609c3f403397dd5 
>   geode-site/website/content/community/index.html 
> 34e085c77e8803bfe7e6ac621b2b149f8c46b653 
>   geode-site/website/content/docs/index.html 
> 0a475f95b3425624b8478ca4ce55c946140b4cb3 
>   geode-site/website/content/img/asf_logo.png PRE-CREATION 
>   geode-site/website/content/img/egg-logo.png 
> 2169a2a36c49c42a2e771c0b785787eb4784d870 
>   geode-site/website/content/index.html 
> 55311d77aafa7e9065e27130b8662987b90e2563 
>   geode-site/website/content/releases/index.html 
> de0335d6bc0edd299edf44b28cdddf7f33fa15c1 
>   geode-site/website/layouts/footer.html 
> 4877109cbd3599dff81d4d5d69a6ab1c9c73d982 
>   geode-site/website/layouts/header.html 
> 618d33d43506ed6a75326998193af224c2ba6a05 
>   geode-spark-connector/doc/2_quick.md 
> 8c2fe4cf61a20fdd930cfd61e0c5df2ed505e456 
>   geode-web-api/src/main/webapp/META-INF/NOTICE 
> 21082b6de4fbd7ba4ec4bcb61e9e1bfda5ac162a 
>   geode-web/src/main/webapp/META-INF/NOTICE 
> 8c6e1d7faf3188599305f44c44318f6e6cfd00e6 
>   gradle.properties 164d482161b59534fd91bc14c7773140fbec279e 
>   gradle/publish.gradle af5ee13a2eb6f6532a0e7c73bfb2591dfde60b30 
>   gradle/sonar.gradle 32f18834b054436d29f1b4ca52c145c35b808c60 
> 
> Diff: https://reviews.apache.org/r/54321/diff/
> 
> 
> Testing
> ---
> 
> I'm holding this until the infrastructure changes are ready.
> 
> 
> Thanks,
> 
> Anthony Baker
> 
>

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

[Joey McAllister]

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


Ship it!




Ship It!

- Joey McAllister


On Dec. 2, 2016, 5:46 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54315/
> ---
> 
> (Updated Dec. 2, 2016, 5:46 p.m.)
> 
> 
> 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
> 
>