[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #84 was SUCCESSFUL (with 1182 tests). Change made by John Blum .

2015-10-02 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #84 was successful. --- Scheduled with changes by John Blum . 1186 tests in total. https://build.spring.io/browse

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

2015-10-02 Thread jun aoki
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/ --- (Updated Oct. 3, 2015, 2:19 a.m.) Review request for geode. Bugs: GEODE-60

Review Request 38971: GEODE-77 health-monitor and manager-shutdown improvements

2015-10-02 Thread Bruce Schuchardt
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38971/ --- Review request for geode, anilkumar gingade, Jason Huynh, Jianxia Chen, and Lynn

Re: Review Request 35541: GEODE-60 Geode build environment within Docker to enable anybody and on any OS and any environment can build Geode as long as there is Docker

2015-10-02 Thread jun aoki
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35541/ --- (Updated Oct. 2, 2015, 9:28 p.m.) Review request for geode. Bugs: GEODE-60

Re: Incubator PMC/Board report for Oct 2015 ([ppmc])

2015-10-02 Thread Kirk Lund
We previously discussed (and decided) on this this list to stay on monthly reporting even though we're officially quarterly. -Kirk On Fri, Oct 2, 2015 at 1:14 PM, Niall Pemberton wrote: > On Thu, Oct 1, 2015 at 4:59 PM, Anthony Baker wrote: > > > Any volunteers for the report this month? Or

Re: Incubator PMC/Board report for Oct 2015 ([ppmc])

2015-10-02 Thread Niall Pemberton
On Thu, Oct 1, 2015 at 4:59 PM, Anthony Baker wrote: > Any volunteers for the report this month? Or are we one the quarter > schedule now? > You are on a quarterly schedule now - but that includes October (January, April, July, October) so - you need to prepare one http://incubator.apache.org

Re: ASF Jira Project Roles and Groups

2015-10-02 Thread Kirk Lund
I agree. And if the log files and stat files are valuable for working on the bug shouldn't we make those available via a comment on a Jira ticket? Even if some application that uses Geode isn't open sourced, but we have logs and stats for it and that application hit a Geode bug for which we file a

Re: ASF Jira Project Roles and Groups

2015-10-02 Thread Dan Smith
I agree with Anthony. There shouldn't be anything in geode that can't be picked up and worked on by any member of the community. Having bugs that can only be worked on by employees of Pivotal is contrary to being an open community. -Dan On Fri, Oct 2, 2015 at 10:54 AM, Kirk Lund wrote: > I'm al

Re: ASF Jira Project Roles and Groups

2015-10-02 Thread Kirk Lund
I'm all for making test results external as well. Can we open up our servers so that the public can view our buglogs directories? That way we can post comments pointing those invaluable results! If not then we need to replicate every ticket internally which is a terrible idea. -Kirk On Fri, Oct

Re: ASF Jira Project Roles and Groups

2015-10-02 Thread Anthony Baker
My belief is that Apache (and thus Geode) is an open community and everything about Geode should be open and collaborative. Private comments on JIRA’s would distort that principle IMO. Perhaps we can find a way over time to make internal test results and data less internal :-) Anthony > On

Re: Review Request 38912: GEODE-77 fixes for network failure handling & miscellaneous unit test failures

2015-10-02 Thread Bruce Schuchardt
> On Oct. 1, 2015, 1:30 a.m., anilkumar gingade wrote: > > gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/InternalDistributedSystem.java, > > line 1327 > > > > > > we are passing the same valu

ASF Jira Project Roles and Groups

2015-10-02 Thread Kirk Lund
If I pull up a Jira ticket such as: https://issues.apache.org/jira/browse/GEODE-189 I can add a comment or edit an existing comment and I notice there's an option for locking the comment so that it's only readable by a specified Project Role or Group. At present there is only one Project Role "C

Build failed in Jenkins: Geode-nightly #233

2015-10-02 Thread Apache Jenkins Server
See Changes: [dschneider] GEODE-379: fix spelling of entry-time-to-live-expiration-action option -- [...truncated 166 lines...]