Re: Include GEODE-7776 in release 1.12
Ernie- Can you please cherry-pick GEODE-7776 to release/1.12.0? On Tue, Feb 11, 2020 at 11:45 AM Jinmei Liao wrote: > +1 > > On Tue, Feb 11, 2020, 11:39 AM Udo Kohlmeyer wrote: > > > +1 > > > > On 2/11/20 11:23 AM, Dick Cavender wrote: > > > This regression was introduced when the geode-gfsh subproject was > > recently > > > added. While not obvious this created a critical build / runtime cycle > > > between geode-core and geode-gfsh that causes some tools/IDEs, that > don't > > > cope well with circular dependencies, to fail. Additionally no previous > > > Geode releases have shipped with known circular dependencies. > > > > > > commit 7ab2713d6c9d2d09a986513aaa18b333951fe61e > > > Author: Robert Houghton > > > Date: Mon Feb 10 13:18:34 2020 -0800 > > > > > > GEODE-7776 - Proposed changes to remove build cycle (#4679) > > > > > > * Proposed changes to remove build cycle > > > > > > * Fix expected pom, and delete commented dependency > > > > > >
Re: Include GEODE-7776 in release 1.12
There appears to be consensus that this is a critical fix. The following commit has been brought into release/1.12 as the critical fix for GEODE-7776: git cherry-pick -x 7ab2713d6c9d2d09a986513aaa18b333951fe61e GEODE- has been marked as 'resolved in' 1.12. Regards EB On Wed, Feb 12, 2020 at 10:37 AM Dick Cavender wrote: > Ernie- Can you please cherry-pick GEODE-7776 to release/1.12.0? > > > On Tue, Feb 11, 2020 at 11:45 AM Jinmei Liao wrote: > >> +1 >> >> On Tue, Feb 11, 2020, 11:39 AM Udo Kohlmeyer wrote: >> >> > +1 >> > >> > On 2/11/20 11:23 AM, Dick Cavender wrote: >> > > This regression was introduced when the geode-gfsh subproject was >> > recently >> > > added. While not obvious this created a critical build / runtime cycle >> > > between geode-core and geode-gfsh that causes some tools/IDEs, that >> don't >> > > cope well with circular dependencies, to fail. Additionally no >> previous >> > > Geode releases have shipped with known circular dependencies. >> > > >> > > commit 7ab2713d6c9d2d09a986513aaa18b333951fe61e >> > > Author: Robert Houghton >> > > Date: Mon Feb 10 13:18:34 2020 -0800 >> > > >> > > GEODE-7776 - Proposed changes to remove build cycle (#4679) >> > > >> > > * Proposed changes to remove build cycle >> > > >> > > * Fix expected pom, and delete commented dependency >> > > >> > >> >
Feb 2020 Apache Geode quarterly report
I've submitted our quarterly report. The ASF requests that we no longer email the board with the report as part of the process. So, this email is a copy of the report that I submitted. Karen ## Description: Apache Geode is a data management platform that provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high concurrency processing. ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Geode was founded 2016-11-15 (3 years ago) There are currently 107 committers and 52 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Bill Burcham on 2019-09-08. - Aaron Lindsey was added as committer on 2019-12-16 - Benjamin Ross was added as committer on 2019-12-06 - Donal Evans was added as committer on 2019-11-22 ## Project Activity: 1.11.0 was released on 2019-12-31. We are well on our way to a 1.12.0 release. Two areas of focus on our code base have been toward fixing tests marked as flaky, and introducing the ability to specify (authorize) access to data when querying a dataset (see https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security ). ## Community Health: The community is actively contributing to the Apache Geode code base. In the past quarter: - 393 emails sent to dev@geode.apache.org - 315 issues opened in JIRA - 288 issues closed in JIRA - 379 PRs opened on GitHub - 396 PRs closed on GitHub - 563 commits by 57 code contributors
[Question] I had a PR that didn't run a StressNewTestOpenJDK11(really), but passed?
Hi, Why is that? It gave the error message in the log of " 17:26:13 66 changed tests 17:26:13 66 is too many changed tests to stress test. Allowing this job to pass without stress testing.” I didn’t touch 66 files. I touched 5 classes. It maybe that there are 66 tests therein, but if that is the bar, StressNewTest is not very useful. I never have one new @Test that needs stress testing, I have been refactoring whole classes. This seems like a bug. Thanks, Mark
