Re: [DISCUSS] Predictable minor release cadence

ree with Robert that we should release based on features that go > > in. > > > > > > > > I am not sure if Apache Kafka & Spark are a good reference for GEODE. > > > > These tools were evolving rapidly in the last couple of years and > > > frequ

Re: November 2018 Board Report Volunteer

I volunteer as tribute On Nov 7, 2018 12:42, "Anthony Baker" wrote: We need to prepare a report for the ASF Board by Nov 14. Any volunteers to write up a draft? You can review the last report [1] and use the report generator [2] to auto-fill some sections (if you have committer status).

Re: [DISCUSS] Disable merge for failing pull requests

+1 On Fri, Nov 9, 2018, 12:55 Dan Smith Hi all, > > Kirks emails reminded me - I think we are at the point now with our PR > checks where we should not be merging anything to develop that doesn't pass > all of the PR checks. > > I propose we disable the merge button unless a PR is passing all of

Re: Is concourse down?

Does github say it merges cleanly? I thought their messaging was pretty clear On Nov 12, 2018 17:19, "Alexander Murmann" wrote: I wonder if we somehow could find a way to make the error message clearer. Since it didn't merge cleanly, there is action I need to take as the committer. However, I

Re: November 2018 Board Report Volunteer

Yes, it's my first task this morning On Nov 13, 2018 07:02, "Anthony Baker" wrote: Are you able to send out a draft for review today? > On Nov 7, 2018, at 12:43 PM, Robert Houghton wrote: > > I volunteer as tribute > > On Nov 7, 2018 12:42, "Anthony Baker&q

Re: November 2018 Board Report Volunteer

Here is a draft of the GEODE report. Please comment or amend so that we can submit to Apache. Thank you, -Robert Houghton ## Description: Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency

November 2018 Board Report Final Draft

on Sat Sep 01 2018 > >- Alexander Murmann was added as a committer on Sat Sep 08 2018 > >- Blake Bender was added as a committer on Sat Sep 01 2018 > >- Helena Bales was added as a committer on Sat Sep 01 2018 > >- Ivan Godwin was added as a committer on Sat Sep

Re: [DISCUSS] Predictable minor release cadence

I have found it refreshing that the geode released cadence has been based on features being done, rather than a set schedule. I come from an environment where we had quarterly releases and monthly patches to all supported previous releases, and I can tell you that it became a grind. That being

Re: [DISCUSS] permit-reflect vs --add-opens for Java 11 support

I vote for #1, with #4 as a stopgap Isn't a goal of Java 11 support in Geode that we can use the new Java modules system? If so, let's actually try and get there. I think stability would actually improve by using public API instead of internals, and performance fears are just that: fears, until

Re: [Discuss] Transitive dependencies and internal .pom changes

-in documentation is here [ https://github.com/nebula-plugins/gradle-lint-plugin/wiki/Unused-Dependency-Rule ] Thank you, -Robert Houghton On Fri, Sep 28, 2018 at 10:18 AM Bill Burcham wrote: > From the PR, Anthony, it seems to me that Patrick is proposing that each > build.gradle be explicit about ment

Re: Questions about Poms and Publishing

Thanks John. Do you foresee the native Gradle DSL https://docs.gradle.org/current/userguide/managing_transitive_dependencies.html as an *eventual* replacement for the dependency-management-plugin you reference? On Tue, Nov 13, 2018 at 9:09 AM John Blum wrote: > If you'd like Maven

Re: Preventing new build warnings

Would a middle-ground be to add a warning-count check to the pull-request pipeline, which would then be reflected to the GitHub PR? On Tue, Jan 15, 2019 at 2:09 PM Udo Kohlmeyer wrote: > So, to reduce the number of new warnings, are we then going to > standardize on JDK versions? i.e, we only

Re: [VOTE] Apache Geode 1.8.0 RC1

+1. Thanks Owen On Mon, Dec 3, 2018, 10:07 Owen Nichols > 2. No zip file for the geode, just .tgz. > > I believe this was changed a few months ago to simplify our build and > release process. Distributing as both .zip and .tgz is a relic of a time > before WinZip, WinRar, 7-Zip, and most other

Re: Jira write access

rhoughton On Mon, Nov 19, 2018 at 2:54 PM Dan Smith wrote: > What's your jira user name? > > -Dan > > On Mon, Nov 19, 2018 at 1:39 PM Robert Houghton > wrote: > > > Hi all. I have a few opened Geode JIRA issues that I would like to be > able > > to delegate

Jira write access

Hi all. I have a few opened Geode JIRA issues that I would like to be able to delegate and work on, but I don't have access to the 'assign' or 'resolve' actions. Can I get access? Thank you, -Robert Houghton

Re: Jira write access

Thanks On Nov 19, 2018 15:07, "Dan Smith" wrote: Ok, you should have access now. -Dan On Mon, Nov 19, 2018 at 3:03 PM Robert Houghton wrote: > rhoughton > > On Mon, Nov 19, 2018 at 2:54 PM Dan Smith wrote: > > > What's your jira user name? > > > > -

Re: Avoiding Unpredictability in Our DUnit Testing Rules

Great find, Patrick. I hope this shakes out some of the test bugs! On Wed, Nov 21, 2018, 10:34 Patrick Rhomberg tl;dr: Use JUnit RuleChain. > > > Hello all! > > Several [1] of our test @Rule classes make use of the fact that our DUnit > VMs Host is statically accessible to affect every test

Re: [Geode Build] Are the idea and eclipse plugins being used by anyone?

@upthewaterspout The plugin generates .iml, .ipr files used by old versions of IntelliJ. The plugin does not give a way to create or modify the currently-used XML files that live inside of the /.idea directory. +1 to removal of the idea plugin. On Wed, Apr 3, 2019 at 3:22 PM Dan Smith wrote: >

Re: geode-all-bom-1.9.0.jar

Geode-dependency-bom works for me On Fri, Mar 29, 2019, 18:23 Jacob Barrett wrote: > It’s not API so it can be changed later right? > > It’s not intended for general direct consumption. The client BOM is. We > can define future BOMs for consumptions. > > -jake > > > > On Mar 29, 2019, at 5:42

Re: geode-all-bom-1.9.0.jar

A) Geode-all-bom contains the dependency versions for our projects. B) maybe not needed, since the dependencies nate already present... On Tue, Mar 26, 2019, 16:09 Anthony Baker wrote: > I’m curious: > > - Why do all subprojects declare a dependency on > project(':boms:geode-all-bom’)) ? > -

Re: [DISCUSS] removal of geode-json module

sure vaadin and geose-json are VERY similar... On Fri, Mar 15, 2019, 16:32 Dan Smith wrote: > Here's the original legal ticket - > https://issues.apache.org/jira/browse/LEGAL-349. It does seem kinda fuzzy. > > What error are you getting if you remove geode-json? I don't see org.json > anywhere

Re: Adding integrationTest src set to geode-dunit

Can I work with you on this tomorrow? On Thu, Feb 7, 2019, 15:09 Kirk Lund wrote: > The usual geode src sets like integrationTest don't already exist in some > modules such as geode-dunit. > > I'm trying to write a new IntegrationTest but simply creating the > directories and placing a new

Re: Adding integrationTest src set to geode-dunit

If i'm not responsive, it because family stuff came up. But i can definitely do this on Monday On Fri, Feb 8, 2019 at 9:45 AM Kirk Lund wrote: > Yep, I'll ping you later this afternoon to see if you're free. Thanks! > > On Thu, Feb 7, 2019 at 4:11 PM Robert Houghton > wrote: >

Re: [DISCUSS] is it time to make Windows tests gating?

They are also as red as the day is long... On Wed, May 15, 2019, 18:28 Owen Nichols wrote: > For a very long time we’ve had Windows tests in the main pipeline (hidden > away, not in the default view), but the pipeline proceeds to publish > regardless of whether Windows tests fail or even run at

Re: what is the best way to update a geode pull request

I really don't like force-push to PRs after comments have been made. At least GitHub shows that the force-push occured now, but that still blocks us from seeing the incremental change. For needing to update a PR due to develop having progressed, I recommend using `git merge origin/develop `

Re: [DISCUSS] changing geode 32-bit counter stats to 64-bit

+1 to @Udo Kohlmeyer comment. If the memory has been used, might as well allow us to query the values On Fri, Jun 7, 2019 at 2:18 PM Udo Kohlmeyer wrote: > +1, if the LongAdders have already added and the additional memory usage > has already been dealt with, then adding the accessors does not

Re: [DISCUSS] reduce PR checks to JDK11 only

The PR pipeline should be a timely test, but also sane and helpful. Maybe making the JDK8 Unit tests (but not the integration, etc) part of PR is a good compromise in that sense. On Sun, May 19, 2019 at 2:20 AM Owen Nichols wrote: > Correct, analyze-serializables test is currently skipped under

Re: Remove mavenLocal from Geode gradle files

Jake, my understanding is that benchmarks does not need geode to be able to pull resources from Maven local. Benchmarks is an external wrapper that executes geode commands, right? On Wed, May 8, 2019, 12:12 Jacob Barrett wrote: > Maven local is necessary for some of our other build processes

Re: Need help: Jetty dunit tests blocking creation of geode-log4j

If the distributedTest jobs are swapping then we have a bigger problem than just this test. We can crank down on the number of parallel jobs and see if that relieves the memory pressure, or we can check for machine types with more memory. I can look at this on Monday, or maybe ping @Sean Goller

Re: [VOTE] Apache Geode 1.9.1.RC3

Hi Jens, Does this issue appear in 1.10.0.RC1? On Tue, Sep 3, 2019, 13:03 Jens Deppe wrote: > TL;DR: +0 > > When using gfsh over http, the following exception occurs: > > (1) Executing - connect --url=https://localhost:7070/geode-mgmt/v1 > >

Re: [VOTE] Apache Geode 1.10.0.RC1

+1 to bringing the build-from-source name to 1.10 -1 to RC1 until then On Fri, Sep 6, 2019, 14:21 Owen Nichols wrote: > Hi Anthony, thank you for bringing your concern. > > If there is consensus from the Geode community that your proposed fix > satisfies the “critical fixes” rule, I will be

Re: [VOTE] Apache Geode 1.9.1.RC3

+1 given the pre-existence of threw class path bug, and it's fix in 1.10 On Wed, Sep 4, 2019, 11:26 Jens Deppe wrote: > No, It's fixed in 1.10.x. > > On Wed, Sep 4, 2019 at 10:16 AM Robert Houghton > wrote: > > > Hi Jens, > > > > Does this issue appear in

Re: ./gradlew test no longer runs/reruns tests?

We added a property to force test reruns specifically, but I can't remember it off hand. More generally, is a gradle option to rerun all tasks (but this takes longer) '--rerun-tasks'. On Wed, Aug 7, 2019, 10:09 Kirk Lund wrote: > I used to use "./gradlew test" to run or rerun unit tests but it

Re: Lingering Geode 1.10.0 release issues

Did the 'merge release branch into master and develop' go smoothly? On Fri, Sep 27, 2019 at 9:27 AM Dick Cavender wrote: > If you try and brew update to Geode 1.10.0 you won't get it until our > 1.10.0 homebrew PR > gets > through their

Re: [DISCUSS] GEODE-7241 - make Jar not War?

I am unclear on the consensus of this thread. On Wed, Sep 25, 2019 at 12:55 PM John Blum wrote: > @Jake - Ah, indeed it was https://en.wikipedia.org/wiki/Gwar. I never > heard of them until now. Gotta love the 80s Rock/Heavy Metal Era. > > On Wed, Sep 25, 2019 at 12:22 PM Jacob Barrett >

Re: ***UNCHECKED*** Re: ClassNotFoundException: LogService

Kirk, will you craft a Jira about this for the "Build" component, and assign it to me? On Mon, Nov 4, 2019, 09:30 Kirk Lund wrote: > If it is picking up an old version of geode then it's doing so because we > use old versions for upgrade/backwards testing. The only old versions of > the jars I

Re: unable to push

Was there a pull request for this SHA? On Thu, Oct 31, 2019, 16:36 Bruce Schuchardt wrote: > I just completed GEODE-7358 and was prevented from pushing from the > command-line. The Merge button on github worked, but why can't I have > command-line control of the process? I don't like giving

Re: [DISCUSS] is overriding a PR check ever justified?

Any committer has the 'status' permission on apache/geode.git. Some API tokens have it as well. Its curl + github API reasoning to do this. On Wed, Oct 30, 2019 at 2:02 PM Jason Huynh wrote: > If we are going to allow overrides, then maybe what Owen is describing > should occur. Make a request

Re: [DISCUSS] how to record 1.9.2 release on master

I think we should look at other examples of git-flow merge practices for this kind of thing. We can't be the only project that does this. But I vote for a merge commit On Tue, Nov 12, 2019, 16:20 Owen Nichols wrote: > It’s been a few weeks since 1.9.2 release was announced, and there is >

Concourse `geode-build-version` is not being incremented

Sometime around when we created a release branch for v1.11.0, and bumped develop to v1.12.0, the semver resource stopped incrementing our SNAPSHOT number. The 1.11 main pipeline is stuck at 1.11.0 (the initial version) instead of having continued on from 1.11.0-SNAPSHOT.303 The develop main

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

+1 Do we want to restart from my lazy POC from a few months ago? On Fri, Nov 22, 2019, 08:40 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

[VOTE] Fix bad-merge of GEODE-7488

I was overzealous in a merge to Geode, and got us into a chicken-and-egg issue for PRs and reverts. Calling a vote to override the GitHub merge button restriction via commiter privileges, to merge the fix in https://github.com/apache/geode/pull/4360

Re: PR jobs failing to start

This was me. I merged a CI change that was missing an SSH option flag. We need to override the PR merge check to fix. I have paused PR jobs until then. On Fri, Nov 22, 2019 at 11:52 AM Kirk Lund wrote: > FYI: Looks like all PR test and build jobs are failing with: > > Warning: Permanently added

Re: [DISCUSS] is overriding a PR check ever justified?

Answering here, because it was asked: @nnag This commit was allowed to merge because we test 'geode' code in the PR pipeline, but we do not test the CI structure and scripts. This is to protect the infrastructure from being hijacked to do things like mine bitcoin, operate as a botnet, etc. The CI

Re: [VOTE] Release candidate for Apache Geode version 1.11.0.RC3.

@udo, if one needs to use a strong word like 'offender', then the offender is the one using an internal API. Geode is under no obligation to maintain or "fix" these for any project. Is there a Jira, github issue, or pull-request to promote the internal class to the public space? Is there a

Re: PR Checks issues?

We could have the content of the PR jobs check that actual sources changed, before doing any real 'work' or 'validation' of the change. If the patch is only CI or readme (not docs, those get compiled) then we can exit with a clean state. Saves time, and money! If the issue is the lack of

Re: [DISCUSS] Blocking merge button in PR

@Udo Kohlmeyer What, if anything, do you propose we do to help keep our project building and running cleanly that does not force punitive or coercive behavior on our developers? "Naming names" or "shaming" are not popular choices, and everyone on the comitters list *should* follow procedure, but

Re: Deprecate SystemFailure Class

+1. On Mon, Oct 28, 2019 at 12:11 PM Bill Burcham wrote: > The SystemFailure class is a clearing house for detecting and attempting to > mitigate SystemFailure exceptions e.g. VirtualMachineError and > OutOfMemoryError. > > This class should not exist. SystemFailure exceptions should be allowed

Re: What tomcat8 is Geode using?

Hi Kirk, Looking at extensions/geode-modules-tomcat8, that version (8.5.34) is what we are compiling and testing against in this module. On Thu, Oct 24, 2019 at 10:55 AM Kirk Lund wrote: > What actual artifacts does this refer to in DependencyConstraints.groovy? > >

[DISCUSS] GEODE-7241 - make Jar not War?

I am working on the change to get the geode-web and geode-web-api war artifacts published instead of the jars. I have found the geode-web-management project is also producing a war artifact, in addition to a jar. Do we want it to be published as well? What is the criterion we use to decide? I

Re: [VOTE] Apache Geode 1.10.0.RC2

Udo, is there a Jira about this issue? Since this is not a new issue in 1.10 (as you say, it is the case in 1.8, 1.9, 1.9.1) is it really a -1 ? On Tue, Sep 24, 2019 at 12:01 PM Udo Kohlmeyer wrote: > Given that 1.8, 1.9 are currently publishing the jar's to the maven > central, instead of

Re: [DISCUSS] GEODE-7241 - make Jar not War?

The geode-pulse module also builds a war, but does not publish it. Is this an oversight, or by design? On Tue, Sep 24, 2019 at 3:34 PM Robert Houghton wrote: > I am working on the change to get the geode-web and geode-web-api war > artifacts published instead of the jars. I have

Re: [Announce] Release branch 1.9.2 created

I'm about to merge the war pr into develop. On Fri, Oct 4, 2019, 06:47 Jens Deppe wrote: > Hello Geode Dev Community, > > We have created a new release branch for Apache Geode 1.9.2 - > "release/1.9.2" > > > This branch currently includes the following commits: > > > GEODE-7124: Fixing tests

Re: [DISCUSS] GEODE-7241 - make Jar not War?

I'd like to see > this included too. > > --Jens > > On Mon, Sep 30, 2019 at 12:35 PM Udo Kohlmeyer wrote: > > > @Robert, I think the consensus is that WAR is the correct option. > > > > So unless someone objects, GEODE-7241 is a GO! > > > > --Udo >

Re: [PROPOSAL] eliminate file count loophole in PR StressNewTest

Yes, as it should On Sat, Feb 29, 2020, 12:25 Dan Smith wrote: > Doesn't the build fail when concourse times out? > > -Dan > > On Fri, Feb 28, 2020, 1:37 PM Donal Evans wrote: > > > +1 > > > > If the original reason for the 25 file limit was to prevent StressNewTest > > taking too long, then

Re: Old geode-benchmark PRs

@Alberto I like this idea. The link between Jira and the GitHub PR will be a nice breadcrumb to follow going forward as well, assuming the PRs are correctly labeled for cross-linking to occur. On Thu, Jan 23, 2020 at 8:05 AM Alberto Bustamante Reyes wrote: > What about closing the PRs and

Re: StressNewTest timeout exceeded

How did you change its timeout? On Wed, Feb 5, 2020, 07:27 Owen Nichols wrote: > Hi Mario, I’ve re-triggered your PR check with a longer timeout, since I > think you are only about an hour over the current timeout of 6 hours for > StressNewTest. > > > On Feb 5, 2020, at 5:10 AM, Mario Kevo

Re: Odg: acceptance test task failing?

------- > *Šalje:* Robert Houghton > *Poslano:* 17. veljače 2020. 16:02 > *Prima:* dev@geode.apache.org > *Predmet:* Re: acceptance test task failing? > > The test has been erroring consistently on develop since > > https://github.com/apache/geode/commit/1a0d9769e48

Re: acceptance test task failing?

The test has been erroring consistently on develop since https://github.com/apache/geode/commit/1a0d9769e482f49e0c725c0d6adc75d324f88958 On Mon, Feb 17, 2020, 06:39 Alberto Bustamante Reyes wrote: > Hi, > > After just changing some typos on a PR, I got errors on >

Re: [PROPOSAL] include GEODE-7796 in Release 1.12.0

+1 On Tue, Feb 18, 2020, 12:49 Bruce Schuchardt wrote: > This fix addresses the inability of a Locator to properly reconnect to the > cluster after being kicked out. Instead of rejoining or shutting down the > Locator gets into a state where it no longer tries to reboot location > services and

Re: Redis PubSubTest started failing

We don't even have windows unit tests for PRs. Walk before we run... On Wed, Feb 19, 2020, 09:00 Owen Nichols wrote: > Perhaps also worth considering: can we get WindowsStressNew added to the PR > checks? > > On Wed, Feb 19, 2020 at 8:50 AM Udo Kohlmeyer wrote: > > > Is this something that can

Re: RFC - Logging to Standard Out

+1 On Wed, Jan 8, 2020, 12:39 Jacob Barrett wrote: > Please see RFC for Logging to Standard Out. > > https://cwiki.apache.org/confluence/display/GEODE/Logging+to+Standard+Out > > > > Please comment by 1/21/2020. > >

Re: [DISCUSS] include geode-benchmarks in 1.12 release

Let's not vote until there is a call to vote, folks... On Thu, Jan 16, 2020, 18:31 Jacob Barrett wrote: > I would characterize my vote as 0. I really don’t care either way. Just > sharing I think they have no value in a release. > > > On Jan 16, 2020, at 6:08 PM, Owen Nichols wrote: > > > >

Re: [DISCUSS] Proposal to require linear commit history on develop

@onichols Correction: The 'git-flow' workflow that Geode follows is to merge a release commit to master and to develop. On Thu, Dec 19, 2019 at 4:51 PM Owen Nichols wrote: > Dan, to address some of your concerns: > > This proposal is to block merge commit on develop only. The release > process

Re: [DISCUSS] abandon branch protection rules

@Jacob Barrett I have some ideas on this. Want to look at in on Thursday with me? On Sat, Dec 28, 2019 at 5:28 AM Jacob Barrett wrote: > Let’s find a way to get the ci, docs, and other directories not effected > by tests out of this testing hold. > > > On Dec 27, 2019, at 3:23 PM, Nabarun Nag

Re: [PROPOSAL] eliminate file count loophole in PR StressNewTest

es. > > > > There’s currently no good data to predict how long StressNew will take, > it > > just depends on the mix of tests touched. I am aware of at least 4 cases > > (with less than 25 files) where the timeout was hit. In two of those > cases > > we re-ran wi

Re: [Discuss] Cache.close synchronous is not synchronous, but code still expects it to be....

The time out is increased in the shared Jinja variables file On Thu, Apr 16, 2020, 10:48 Kirk Lund wrote: > I revived my branch by rebasing it on develop and filed a new draft PR: > > https://github.com/apache/geode/pull/4963 > > Unfortunately, IntegrationTest exceeds timeout every time I

Re: [PROPOSAL]: GEODE-7940 to support/1.12

Conditional +1 from me too, pending a few days on develop with happy results :) Thanks Juan! On Fri, Apr 17, 2020 at 1:41 AM Ju@N wrote: > Hello devs, > > I'd like to propose bringing *GEODE-7940 [1]* to the *support/1.12* branch. > The bug is not new, seems quite old actually, but still seems

Re: Reconfiguring our notifications and more

+1 On Tue, Apr 21, 2020, 08:54 Anthony Baker wrote: > I’d like a quick round of feedback so we can stop the dev@ spamming [1]. > > ASF has implemented a cool way to give projects control of lots of things > [2]. In short, you provide a .asf.yml in each and every GitHub repo to > control lots

Re: [PROPOSAL] eliminate file count loophole in PR StressNewTest

t; 46 is too many changed tests to stress test. Allowing this job to > > pass > > >>>>> without stress testing. (build 6244) > > >>>>> 46 is too many changed tests to stress test. Allowing this job to > > pass > > >>>>> without stress testing. (build 6

Re: RFC: Add C Bindings to Geode Native Client

+1 YES. Having a set of clean C headers also allows for using a broad set of code generators for additional languages (Swig, for example). On Tue, Mar 24, 2020 at 2:20 PM Blake Bender wrote: > Hello everyone, > > We'd like to add C bindings to the native client, in preparation for the >

Re: RFC: Add C Bindings to Geode Native Client

Quick note: ccache is a C/C++ compiler cache. Examples using 'ccache' as the name are confusing. On Tue, Mar 31, 2020 at 3:56 PM Jacob Barrett wrote: > > > > On Mar 31, 2020, at 3:06 PM, Blake Bender wrote: > > > > We in this instance means the native client team. As far as specific > >

Re: [ANNOUNCE] Github Wiki and Issus are now activated on geode-kafka-connector

Woo! Now I just need to find an issue to file or something important to document in the wiki... Thanks, Naba! On Tue, Mar 24, 2020 at 1:42 PM Nabarun Nag wrote: > Hi, > > Issues are wiki pages are now active on the geode-kafka-connector > repository. Thank you all for the kind votes. > >

Re: [DISCUSS] Publish Builds, not Snapshots

wrote: > Do we know if this is an issue that other open source projects have dealt > with? And if so, is this proposed solution similar to what they might have > done to remedy it? > ____ > From: Robert Houghton > Sent: Monday, April 27, 2020

Re: [DISCUSS] Publish Builds, not Snapshots

ild the /develop branch and run `gfsh version` what will it print? > > If I build the soon-to-be /release/1.13 branch and run `gfsh version` what > will it print? > > Anthony > > > On 4/27/20, 4:32 PM, "Robert Houghton" wrote: > > The artifact would cha

Re: [DISCUSS] should we add some Windows PR checks?

I would like to *not* include them, until they can take advantage of our run-in-docker behavior, and not be dog slow. Plus, they are *very* expensive instances. On Mon, Apr 27, 2020 at 1:25 PM Donal Evans wrote: > Having just hit this issue myself, and seen it crop up a few times when I > was

Re: geodeOldVersionInstalls

Pretty sure it is generated by Gradle in geode-assembly On Tue, Apr 28, 2020, 16:09 Kirk Lund wrote: > Does anyone know how geodeOldVersionInstalls.txt gets created? > > When I try to run > TomcatSessionBackwardsCompatibilityTomcat8WithOldModuleCanDoPutsTest > locally, it fails with the

Re: [VOTE] Using Github issues and wiki for geode-kafka-connector project

Looks like we can use the `.asf.yml` file in our repositories to enable `issues` and `wiki` behavior ourselves if we decide we like the feature :) On Fri, Apr 24, 2020 at 7:46 AM Dave Barnes wrote: > +1 > I like the look of the samples. > I also want to echo Anthony and Blake: Accessibility is

Re: [DISCUSS] Publish Builds, not Snapshots

How would it get bumped? > > > > Would a release manager end up using just 1.13.0? Hoping for yes :-) > > > > Anthony > > > >> On Apr 28, 2020, at 9:24 AM, Robert Houghton > wrote: > >> > >> @anthony > >> /develop would say 1.13.0

Re: [DISCUSS] etiquette around breaking the pipeline

I am very pro-revert for breaking changes. The Benchmark or Windows tests being a culprit is unfortunate, since the PR pipeline cannot tell us about those, but thats the cost of our excellence :) On Wed, Apr 29, 2020 at 4:06 PM Owen Nichols wrote: > There are many ways a commit can break the

[DISCUSS] Publish Builds, not Snapshots

hed. Discrete, numbered builds do not. Downstream consumers can use greedy version specifiers to get their current behavior of "latest". Gradle: 'org.apache.geode:geode-core:1.13.0+' Maven: 'org.apache.geode' 'geode-core' '[1.13.0,1.14.0)' What do you all think? Di

Re: [DISCUSS] Publish Builds, not Snapshots

ss of whether we > use -SNAPSHOT or -build.123 … we should replace the 24hr trigger with a > maven-resource trigger (nulldriver, linkyard, or similar) > > > On Apr 27, 2020, at 4:34 PM, Robert Houghton > wrote: > > > > @Owen: What geode-examples is doing, is a pe

Re: [DISCUSS] Publish Builds, not Snapshots

unfortunate that the Maven version coordinate > is ugly. Aside from that I am totally onboard. Yay for reproducible builds > and predictable downstream builds! > >> > >> With SNAPSHOTS in a repo the repository automatically prunes back old > builds. Do we have any c

Re: [DISCUSS] Publish Builds, not Snapshots

m totally onboard. Yay for reproducible builds > and predictable downstream builds! > > > > With SNAPSHOTS in a repo the repository automatically prunes back old > builds. Do we have any concerns about having a plethora of builds filling > up this new pre-release repository? > > &g

[PROPOSAL] Merge PR 5103 (GEODE-8083) to support/1.13

This is a squash of GEODE-8083 and 8087, to bring the Java API comparison jobs from Gradle and Concourse to the support branch. Currently runs cleanly from my terminal, and has been green on develop for a week or so. @Dave Barnes , as release manager, what say you?

Re: [PROPOSAL] Merge PR 5103 (GEODE-8083) to support/1.13

Thanks all. On Wed, May 13, 2020 at 8:34 AM Joris Melchior wrote: > +1 > > From: Robert Houghton > Sent: May 12, 2020 18:57 > To: dev@geode.apache.org ; Dave Barnes (Pivotal) < > dbar...@pivotal.io> > Subject: [PROPOSAL] Merge PR 5

Re: [DISCUSS] Publish Builds, not Snapshots

be great to bring this change > to develop. Assuming it goes smoothly on develop, would you envision > backporting to support/1.13 and support/1.12 as well? > > > On Apr 30, 2020, at 8:38 PM, Robert Houghton > wrote: > > > > I don't read any strong negatives to this

Re: Proposal to bring GEODE-8016 to support branches

Yes please! +1 On Mon, May 11, 2020 at 2:46 AM Darrel Schneider wrote: > +1 > > On Sun, May 10, 2020 at 10:05 PM Dick Cavender > wrote: > > > +1 > > > > On Sat, May 9, 2020 at 6:42 PM Owen Nichols wrote: > > > > > Last week develop was successfully migrated from publishing -SNAPSHOT > to > >

[DISCUSS] enable GitHub PR blocking on API breaking changes

We have enabled this job on the develop and support 1.13 branches, and it is going well. I would like this to be a blocking job for our pull requests. Are there any issues around this test that we want to address, or reasons to *not* have it be a blocking job in the PR pipeline? To seed the

Re: [DISCUSS] enable GitHub PR blocking on API breaking changes

Support seems to be unanimously good, and folks voted in this thread. I'm going to make the ASF-INFRA request. On Fri, May 15, 2020 at 11:47 AM Anthony Baker wrote: > Barry and I tossed up a draft PR to fix a problem in session state > replication with Tomcat. If we can get this completed I’d

Re: [DISCUSS] enable GitHub PR blocking on API breaking changes

Please refer to https://issues.apache.org/jira/browse/INFRA-20270 On Fri, May 15, 2020 at 2:58 PM Robert Houghton wrote: > Support seems to be unanimously good, and folks voted in this thread. I'm > going to make the ASF-INFRA request. > > On Fri, May 15, 2020 at 11:47 AM Anthony

Re: [DISCUSS] enable GitHub PR blocking on API breaking changes

INFRA has added the status to the required list for merging PRs to geode/develop. Thanks everyone. On Fri, May 15, 2020 at 3:03 PM Robert Houghton wrote: > Please refer to https://issues.apache.org/jira/browse/INFRA-20270 > > On Fri, May 15, 2020 at 2:58 PM Robert Houghton

Re: Update of SSLParameterExtension interface

There is an opportunity to take @Jacob Barrett s advice on using a real configuration class instead of an opaque 'Properties' class here. See https://github.com/apache/geode/pull/5115, where we test the API breaking change with an exemption file. On Thu, May 7, 2020 at 8:52 AM Jacob Barrett

Re: [DISCUSS] enable GitHub PR blocking on API breaking changes

gt; cases. > > For example, how would it handle the removal of a deprecated method from > an > > API? It's not something that happens often, but it will happen eventually > > (I would hope). > > > > On Wed, May 13, 2020 at 2:32 PM Robert Houghton > > wrote: >

Re: Welcome!

And thank goodness! Plenty of work to share around. Welcome! On Fri, Mar 20, 2020, 17:21 Anthony Baker wrote: > Over the last few months the Geode PMC has invited the following > people as new committers and PMC members. We’ve been remiss in > officially recognizing your new status, but

Re: [VOTE] Using Github issues and wiki for geode-kafka-connector project

+1! On Sat, Mar 21, 2020, 17:17 Nabarun Nag wrote: > Hello team, > > We are planning to experiment with using Github issues and wiki for the > Apache project *Geode-Kafka-Connector. *(not Apache Geode project). Please > do give your vote on this as we need to send the vote link to infra to >

API check results

compatibility? Thanks for any guidance, -Robert Houghton

Re: Discussion - Change Public API Before Initial Release

+1 On Fri, May 8, 2020, 18:26 Jacob Barrett wrote: > Hey Ya’ll, > > We have a new API going into 1.13 that has an inconsistency I want to > address before we are stuck with it. The class SniSocketFactory should be > renamed SniProxySocketFactory. The class in question produces objects of > type

Re: [Suspected Spam] Access to Geode concourse pipeline

Hi Sara. This got thrown into my junk list (thanks, Outlook). I’ll get on this. From: Sarah Abbey Date: Wednesday, September 30, 2020 at 9:07 AM To: dev@geode.apache.org Subject: [Suspected Spam] Access to Geode concourse pipeline Hello! I would like to request access to the Geode concourse

Re: Please give me access to debug concourse runs

Hi! I'll set that up first thing tomorrow On Aug 18, 2020 16:49, Darrel Schneider wrote: I would like to use "fly" to login to concourse and look at some test runs that are hanging. Could I be given access please? Thanks

  1   2   >