Re: [DISCUSS] Move geode to the attic

Once moved to the attic, it sounds like: * The geode github repo would become read-only (but remain world-readable in perpetuity). * Geode would no longer be available for download on the geode download site or mirrors (but still available in releases tab in github). * Geode maven

[ANNOUNCE] Apache Geode 1.15.1

and documentation can be found at the project website: https://geode.apache.org/releases/ https://geode.apache.org/docs/guide/115/about_geode.html We would like to thank all the contributors that made the release possible. Regards, Mario Kevo and Owen Nichols on behalf of the Apache Geode team

Re: [RESULT][VOTE] Apache Geode 1.15.1.RC1

Sure thing, I will sign the v1.15.1 tag. All other release artifacts will be what was voted on (those created and signed by Mario). Expect release announcement later today. From: Anthony Baker Date: Monday, October 10, 2022 at 11:30 AM To: dev@geode.apache.org Cc: Owen Nichols Subject

Re: Release manager permissions

Hi Mario, a basic concourse installation[1] needs a database (e.g. Postgres), the concourse web service, and 1 or more concourse workers. A secrets store like Vault is also recommended. These don’t have to be especially beefy (if hosting in GCP, something like gcp n2-standard-4 is fine).

Re: Release manager permissions

Hi Mario, you won’t need any Concourse permissions for Geode 1.15.x patch release(s) in the next two months, as the relevant “main”[1] and “rc”[2] pipelines already exist (just skip the deploy_rc_pipeline step). [1]

Re: CODEOWNERS? (was Re: Pending PR reviews)

+1 In the case where someone isn’t sure who might be good to request a review from, GitHub seems to now have a reviewer-recommendation feature based on who has recently touched the files in the PR. Non-committers can always email the dev list if help is needed. From: Patrick Johnson Date:

[ANNOUNCE] Apache Geode 1.15.0

#ReleaseNotes-1.15.0 Release artifacts and documentation can be found at the project website: https://geode.apache.org/releases/ https://geode.apache.org/docs/guide/115/about_geode.html We would like to thank all the contributors that made the release possible. Regards, Owen Nichols on behalf

Re: [VOTE] Apache Geode 1.15.0.RC1

3 PMC members with +1 votes and has the required majority of +1 votes. Apache Geode 1.15.0.RC1 has passed the vote and we will finalize the release shortly. Thanks everyone for the great work! -Owen Nichols Geode 1.15.0 Release Manager From: Bill Burcham Date: Friday, June 17, 2022 at 2:35 PM

[VOTE] Apache Geode 1.15.0.RC1

/blob/develop/KEYS Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.15.0.RC1 -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1138 build runAll Regards -Owen Nichols 1.15.0 Geode Release Manager

Re: [PROPOSAL] Relocate Geode Docs from code repo to seperate repo

The Geode project comprises several repos already, include geode, geode-examples, geode-benchmarks, geode-native, and geode-kafka-connector, and geode-site, so it’s not unreasonable to add another. However, we still release all at the same time, so any “code freeze” applies equally to all

Re: [PROPOSAL] re-cut support/1.15

, in addition to adding one of the labels above, please also email the dev list, otherwise I will soon begin preparing RC1 for voting next week. -1.15.0 Release Manager From: Owen Nichols Date: Monday, May 9, 2022 at 10:31 AM To: dev@geode.apache.org Subject: Re: [PROPOSAL] re-cut support/1.15

Re: [PROPOSAL] re-cut support/1.15

Hello Geode Community, counting the labels in Jira I see: May 6: 1 needsTriage and 2 blocks-1.15.0. May 20: 0 needsTriage and 3 blocks-1.15.0. Looks like some progress. Please continue to use the above labels to raise any issues. -1.15.0 Release Manager From: Owen Nichols Date: Monday, May

Re: [PROPOSAL] re-cut support/1.15

locks-1.15.0" label in Jira. From: Owen Nichols Date: Friday, May 6, 2022 at 10:47 AM To: dev@geode.apache.org Subject: Re: [PROPOSAL] re-cut support/1.15 Great news! I would be delighted to continue as Release Manager for 1.15.0. To track progress toward code-complete, I will monitor the &q

Re: [PROPOSAL] re-cut support/1.15

. Would you be willing to resume release manager duties? @Everyone - please chime in if you have in-progress work that you want to ship with 1.15 (ideally this is labeled in JIRA with “blocks-1.15.0”). Thanks, Anthony > On Mar 16, 2022, at 2:12 PM, Owen Nichols wrote: > > Seven we

Re: [PROPOSAL] re-cut support/1.15

with “blocks-1.15.0”). Thanks, Anthony > On Mar 16, 2022, at 2:12 PM, Owen Nichols wrote: > > Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 > a few weeks ago. I wonder if perhaps we cut the release branch prematurely? > I propose that we aband

Re: [PROPOSAL] RFC for migrating from springfox to springdoc

It would be great to make the switch to springdoc. If you are willing, go for it! Slightly outside the scope of this RFC: Swagger was added as part of the @Experimental manageability REST API [1] and is used to generate API docs for each minor [2]. It looks like the API hasn’t changed much

Re: [discuss] Future of the geode-redis module

Well said, Donal. As a past Release Manager, geode-for-redis impacted release timelines for 1.13, 1.14, and most recently 1.15. I support this proposal in hopes that refocusing on core Geode makes future releases a little more predictable. Now might also be a good time to review other

Re: [PROPOSAL] annul support/1.15

PM To: dev@geode.apache.org Subject: Re: [PROPOSAL] annul support/1.15 +1 From: Owen Nichols Sent: Wednesday, March 16, 2022 2:12 PM To: geode Subject: [PROPOSAL] annul support/1.15 Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5

[PROPOSAL] annul support/1.15

Seven weeks after cutting support/1.15, Jira now shows 11 blockers, up from 5 a few weeks ago. I wonder if perhaps we cut the release branch prematurely? I propose that we abandon this branch and focus on getting develop closer to what we want to ship, then discuss re-cutting the branch. If

Re: Commit message review opt-in

message review opt-in Can we please agree to send requests for inclusion directly to onich...@vmware.com<mailto:onich...@vmware.com> rather than back to this thread. On Mar 4, 2022, at 1:09 PM, Owen Nichols mailto:onich...@vmware.com>> wrote: Thanks Udo, I have added kohlmu-pivotal

Re: Commit message review opt-in

on “noise” if that is your concern. From: Jacob Barrett Date: Friday, March 4, 2022 at 1:26 PM To: dev@geode.apache.org Subject: Re: Commit message review opt-in > On Mar 4, 2022, at 1:22 PM, Owen Nichols wrote: > > Unfortunately, I cannot add anyone to the opt-in list without

Re: Commit message review opt-in

for inclusion directly to onich...@vmware.com<mailto:onich...@vmware.com> rather than back to this thread. On Mar 4, 2022, at 1:09 PM, Owen Nichols mailto:onich...@vmware.com>> wrote: Thanks Udo, I have added kohlmu-pivotal as requested, for non-draft PRs only. From: Udo Kohlme

Re: Commit message review opt-in

Thanks Udo, I have added kohlmu-pivotal as requested, for non-draft PRs only. From: Udo Kohlmeyer Date: Friday, March 4, 2022 at 1:03 PM To: dev@geode.apache.org Subject: Re: Commit message review opt-in I’ll opt-in please. --Udo From: Owen Nichols Date: Saturday, February 26, 2022 at 10:44

Re: Commit message review opt-in

Thanks Kirk, I have added you as requested. From: Kirk Lund Date: Thursday, March 3, 2022 at 10:18 AM To: dev@geode.apache.org Subject: Re: Commit message review opt-in I'd like to opt-in for this Owen. Thanks! -Kirk On Fri, Feb 25, 2022 at 3:43 PM Owen Nichols wrote: > If you recei

Re: Commit message review opt-in

Thanks Eric, I have added you as requested. From: Eric Zoerner Date: Thursday, March 3, 2022 at 12:00 PM To: Owen Nichols Cc: dev@geode.apache.org Subject: Re: Commit message review opt-in I would like to opt-in. GitHub user name is ezoerner, and yes include draft PRs From: Owen Nichols

1.15.0 release status update

One month after cutting support/1.15, Jira shows 5 blockers remaining [1]. Great work, keep those bug reports and fixes coming! This week I will be conducting a practice exercise of creating a 1.15.0.RC0 to test release scripts and pipelines. Please ignore this RC0 tag (no need to review or

Commit message review opt-in

If you received an automated-looking PR review comment from onichols-pivotal in the past few weeks without consent, I apologize and have withdrawn it. If you would like to continue receiving these automated reviews, you may opt-in by emailing me your github username (also let me know if you

1.15.0 release status update

After cutting the support/1.15 branch a few weeks ago, Jira [1] shows we are down to 3 blockers. Great work, keep those fixes (and bug reports) coming! Information about upcoming releases [2] and tips for backporting [3] can now be found in the wiki. PSA: When using a search engine to quickly

Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th

- 1.12.6 was released on 2021-12-11 > > - 1.13.5 was released on 2021-12-11 > > - 1.14.1 was released on 2021-12-11 > > > > From: Owen Nichols > Sent: Tuesday, February 1, 2022 12:39 PM > To: dev@geode.apache.org > Subject: Re: [DRA

Re: [DISCUSS] Testing and voting on release candidates

Thanks for putting together this script, Dan. It's always humbling to discover ways that a user's environment can differ from the tightly-controlled conditions of CI. I've noticed we've shipped quite a few releases recently with the bare minimum of votes. I hope this will encourage more

Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th

1.12.8 seems to be missing from the list of releases. Also consider bragging about Geode’s turnaround time from CvE disclosure to patch release…only one other ASF project got theirs out faster than we did. --- Sent from Workspace ONE Boxer On January 31,

Re: Geode Jira Access Request

Hi Steve, apache ID “ssienkowski” should be assignable to GEODE Jira tickets now. From: Steve Sienkowski Reply-To: "dev@geode.apache.org" Date: Monday, January 31, 2022 at 2:19 PM To: "dev@geode.apache.org" Subject: Geode Jira Access Request Hi team, Could someone help me get the proper

Re: Changes made after 1.15 release branch is cut (SHA# 8f7193c827ee3198ae374101221c02039c70a561)

Date: Thu Jan 27 11:23:29 2022 +0100 GEODE-9972: eliminate overnight step from release process (#7280) commit bbe12c3217aa351422f3a61aa9a2cd1546a7b5db Author: Owen Nichols <34043438+onichols-pivo...@users.noreply.github.com> CommitDate: Thu Jan 27 00:03:08 2022 -0800 Rev

Re: Proposal: Cut 1.15 release branch from SHA 8f7193c827ee3198ae374101221c02039c70a561

f these changes limit themselves to a single line. ________ From: Owen Nichols Sent: Tuesday, January 25, 2022 20:18 To: dev@geode.apache.org Subject: Re: Proposal: Cut 1.15 release branch from SHA 8f7193c827ee3198

Re: Proposal: Cut 1.15 release branch from SHA 8f7193c827ee3198ae374101221c02039c70a561

Even a small change can have subtle but important effects only discovered after a long time, so leaning on commit-size as a proxy for risk may only serve to create a false sense of security. Also to consider, having a large refactor on develop but not support/1.15 will increase backporting

Re: Proposal: Cutting 1.15 Release branch Tuesday, 25 January

@Raymond any update on who will cut the branch and what time today? On 1/20/22, 5:20 PM, "Owen Nichols" wrote: +1 @Raymond are you volunteering as Release Manager or asking for a volunteer? If the role is still open, I'd be happy to volunteer. On 1/20/22, 2:18 PM

Re: Proposal: Cutting 1.15 Release branch Tuesday, 25 January

+1 @Raymond are you volunteering as Release Manager or asking for a volunteer? If the role is still open, I'd be happy to volunteer. On 1/20/22, 2:18 PM, "Raymond Ingles" wrote: Hello Geode Dev Community, We have a proposal to cut the 1.15 release branch this coming Tuesday, the

Re: [DISCUSS] proposal to pare down old-version testing

o upgrade the Geode server cluster compared to potentially many, many client applications. Supporting older client versions gives users time to upgrade, quicker access to bug fixes, and helps avoids downtime. +1 Anthony > On Dec 22, 2021, at 7:13 PM, Owen Nichols wro

Re: [VOTE] - Apache Geode Kafka Connector 1.1.0 - Take 2

Quibbles: - artifact naming does not follow standard naming convention of THING-VERSION.tgz and THING-VERSION-src.tgz (also Geode decided to stop distributing .zip files years ago) - not based on the latest Geode 1.12 patch. I would like to see Geode 1.12.8 picked up once it's available later

[DISCUSS] proposal to pare down old-version testing

Since adopting our N-2 support policy, the list of released versions in /settings.gradle has ballooned to over 30 entries [1]. CI tests use this list to confirm that we don’t break rolling upgrade ability or compatibility with older clients, but some of these tests don’t seem to scale well:

[ANNOUNCE] Apache Geode 1.12.7, 1.13.6, and 1.14.2

://geode.apache.org/docs/guide/112/about_geode.html https://geode.apache.org/docs/guide/113/about_geode.html https://geode.apache.org/docs/guide/114/about_geode.html We would like to thank all the contributors that made these releases possible. Regards, Owen Nichols on behalf of the Apache Geode team

Re: [DISCUSS] Adding LTGM as gating PR checks

Requiring LGTM looks good to me. It does not seem to have a high rate of false-positives like some other linters, but if we are making it gating, what would the process look like to override a false-positive? On 12/16/21, 10:37 AM, "Anthony Baker" wrote: Thanks Robert, I think this is

Re: [VOTE] Apache Geode 1.14.2.RC1

* Build from source * WAN clusters with SSL * puts/gets * validate data integrity after rolling restart. Regards Nabarun Nag From: Owen Nichols Sent: Tuesday, December 14, 2021 6:19 PM To: dev@geode.apache.org

Re: [VOTE] Apache Geode 1.12.7.RC1

ng restart. Regards Nabarun Nag From: Owen Nichols Sent: Tuesday, December 14, 2021 6:19 PM To: dev@geode.apache.org Subject: [Suspected Spam] [VOTE] Apache Geode 1.12.7.RC1 Hello Geode Dev Community, This is a release candidate

Re: [VOTE] Apache Geode 1.13.6.RC1

e: +1 verified signatures verified passing pipeline started a small cluster and ran some operations and Pulse From: Owen Nichols Sent: Tuesday, December 14, 2021 18:19 To: dev@geode.apache.org Subject: [Suspected Spam] [VO

[VOTE] Apache Geode 1.14.2.RC1

geode-examples: ./gradlew -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.14.2.RC1 -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1122 build runAll Regards Owen Nichols

[VOTE] Apache Geode 1.12.7.RC1

geode-examples: ./gradlew -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.12.7.RC1 -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1120 build runAll Regards Owen Nichols

[VOTE] Apache Geode 1.13.6.RC1

geode-examples: ./gradlew -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.13.6.RC1 -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1121 build runAll Regards Owen Nichols

[ANNOUNCE] Apache Geode 1.12.6, 1.13.5, and 1.14.1

/ The release documentation is available at: https://geode.apache.org/docs/guide/112/about_geode.html https://geode.apache.org/docs/guide/113/about_geode.html https://geode.apache.org/docs/guide/114/about_geode.html We would like to thank all the contributors that made the release possible. Regards, Owen

Re: [VOTE] Apache Geode 1.14.1.RC2

rom source * WAN clusters with SSL * puts/gets * validate data integrity after rolling restart. Regards Nabarun Nag From: Owen Nichols Sent: Friday, December 10, 2021 2:09 PM To: dev@geode.apache.org Subject: [Susp

Re: [VOTE] Apache Geode 1.13.5.RC2

s with SSL * puts/gets * validate data integrity after rolling restart. Regards Nabarun Nag From: Owen Nichols Sent: Friday, December 10, 2021 2:09 PM To: dev@geode.apache.org Subject: [Suspected Spam] [VOTE] Apache Ge

Re: [VOTE] Apache Geode 1.12.6.RC2

h commands. --Jens From: Owen Nichols Date: Friday, December 10, 2021 at 2:09 PM To: dev@geode.apache.org Subject: [Suspected Spam] [VOTE] Apache Geode 1.12.6.RC2 Hello Geode Dev Community, This is a release candidate for Apache Geode version 1.12.6.RC2. Tha

[VOTE] Apache Geode 1.13.5.RC2

/KEYS Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.13.5.RC2 -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1117 build runAll Regards Owen Nichols

[VOTE] Apache Geode 1.12.6.RC2

/KEYS Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.12.6.RC2 -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1119 build runAll Regards Owen Nichols

[VOTE] Apache Geode 1.14.1.RC2

/KEYS Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.14.1.RC2 -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1118 build runAll Regards Owen Nichols

Re: [DISCUSS] batch patch release voting

e case… Then maybe every release has to be voted on, no bulk/batch allowed, as every release has to be verified separately. Which, just means that bulk announcements is the only thing that makes sense… From: Owen Nichols Date: Friday, December 3, 2021 at 10:39 AM To: dev@geode.apache.org Subje

Re: [DISCUSS] batch patch release voting

older/newer minor versions) From: Owen Nichols Date: Friday, December 3, 2021 at 9:56 AM To: dev@geode.apache.org Subject: Re: [DISCUSS] batch patch release voting It doesn’t really make a lot of sense to release a fix in a 1.12 patch separately without later patches. Doing so would send the con

Re: [DISCUSS] batch patch release voting

4 once the issue is fixed? From: Owen Nichols Sent: Wednesday, December 1, 2021 11:45 AM To: dev@geode.apache.org Subject: [DISCUSS] batch patch release voting Geode's N-2 support policy can lead to "waves" of patch releases. For example, 1.12.6, 1.13.5 an

[DISCUSS] batch patch release voting

Geode's N-2 support policy can lead to "waves" of patch releases. For example, 1.12.6, 1.13.5 and 1.14.1 are all likely this month, with many of the same fixes in each. Some open source projects group waves of patch releases into a single announcement. It might be nice to do this for Geode.

Re: API check error when adding a new method to a public interface

Adding a new method to a public interface breaks anyone else implementing that interface, for example Spring. Adding a new method with a default implementation (except in the case where it is purely a composure of existing methods) isn't great either, you would probably have to throw

Re: @TestOnly or @VisibleForTesting

@VisibileForTesting is bad. It does NOT tell you if the method SHOULD HAVE BEEN private, or package-private, or protected, so there is no way to reconstruct the originally-intended code if the annotation is ever removed. It also prevents the exposed methods from being named in a way that

Re: @TestOnly or @VisibleForTesting

It would be really great if there were java tooling to actually compile separate production binaries and test binaries based on annotations like this, rather than having to ship methods that were only exposed for testing. If such a preprocessor does exist, @TestOnly provides a stronger,

[PSA] best way to push a tag

Preferred: git push origin Thar be dragons: git push --tags

[DISCUSS] Geode 1.14.0 retrospective

With Geode 1.14 now released, please reflect on what went well and what we could do differently next time. I’ll start… Went well: patch releases allowed us to continue delivering quarterly bugfixes while spacing out bigger changes. Went well: "blocks-x.y.z" Jira label made it easy to track

Re: [jira] [Commented] (GEODE-6402) Create a DOAP file for the Apache Geode project

rat versions before 0.14 (not yet released, despite a fix for this bug being committed in May 2019) do not recognize the https variant of the Apache license url, so change line 10 to http://www.apache.org/licenses/LICENSE-2.0 On 9/1/21, 3:26 PM, "Dave Barnes" wrote: Why does this file,

Re: Annual branch cleanup Aug 17

Liao" wrote: Please leave the feature branch “expireAuthentication”, The RFC is in: https://cwiki.apache.org/confluence/display/GEODE/On+Demand+Geode+Authentication+Expiration+and+Re-authentication From: Owen Nichols Date: Sunday, August 1, 2021 at 1:01 AM To: dev@geode.

Re: Proposal - unprotect develop branch of geode-native

For this situation in Geode repo, in addition to Squash, we also allow Rebase. This would allow you to put both commits in the same PR to pass checks, but still apply them to develop as separate commits. On 8/17/21, 2:20 PM, "Blake Bender" wrote: Hello everyone, Today I once again

Re: Annual branch cleanup Aug 17

people. Thanks, -Dan From: Owen Nichols Sent: Sunday, August 1, 2021 1:01 AM To: dev@geode.apache.org Subject: Annual branch cleanup Aug 17 Reminder to use your personal fork whenever possible. If you do create a branch in the geode repo, please clean it up pr

Annual branch cleanup Aug 17

Reminder to use your personal fork whenever possible. If you do create a branch in the geode repo, please clean it up promptly. An easy way to check is https://github.com/apache/geode/branches/yours I propose to delete the branches listed below on August 17 at 3pm. If there’s any branch you

[ANNOUNCE] Apache Geode 1.12.3

. Regards, Owen Nichols on behalf of the Apache Geode team

Re: [VOTE] Apache Geode 1.12.3.RC3

the requirements of at least 3 PMC members with +1 votes and has the required majority of +1 votes. Apache Geode 1.12.3.RC3 has passed the vote and we will finalize the release shortly. Thanks everyone for the great work! -Owen Nichols On 6/30/21, 2:52 PM, "Dick Cavender" wrote:

Re: [DISCUSS] Backporting to support branches

Hi Naba, is it still the case that only you will merge the PRs to support/1.14? Or can committers merge their own 1.14 PRs anytime after you have approved the PR? I sometimes forget to create my PRs in Draft mode, and may still be running additional tests, so I'd prefer not to have anyone but

Re: Fw: [DISCUSS] Rebase and Squash Options on Github develop

o room for mistakes to occur. I would like to propose to that we set the GitHub setting on develop PR to rebase and squash buttons. Please do note that this is reversible and can be changed back, hence there is no harm in trying it out. Regards Nabarun Nag From

[VOTE] Apache Geode 1.12.3.RC3

/repositories/orgapachegeode-1084 build runAll Regards Owen Nichols

[ANNOUNCE] Apache Geode 1.13.3

artifacts can be downloaded from the project website: http://geode.apache.org/releases/ The release documentation is available at: http://geode.apache.org/docs/guide/113/about_geode.html We would like to thank all the contributors that made the release possible. Regards, Owen Nichols on behalf

Re: [VOTE] Apache Geode 1.13.3.RC2

of at least 3 PMC members with +1 votes and has the required majority of +1 votes. Apache Geode 1.13.3.RC2 has passed the vote and we will finalize the release shortly. Thanks everyone for the great work! -Owen Nichols On 6/24/21, 3:31 PM, "Dick Cavender" wrote: +1 Bu

[VOTE] Apache Geode 1.13.3.RC2

/KEYS Command to run geode-examples: ./gradlew -PgeodeReleaseUrl=https://dist.apache.org/repos/dist/dev/geode/1.13.3.RC2 -PgeodeRepositoryUrl=https://repository.apache.org/content/repositories/orgapachegeode-1086 build runAll Regards Owen Nichols

Re: [VOTE] Apache Geode 1.13.3.RC1

* Rebalance operations during upgrades. Regards, Nabarun ____ From: Owen Nichols Sent: Monday, June 21, 2021 11:02 AM To: dev@geode.apache.org Subject: [Suspected Spam] [VOTE] Apache Geode 1.13.3.RC1

[VOTE] Apache Geode 1.13.3.RC1

build runAll Regards Owen Nichols

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

1 at 2:11 PM Anthony Baker wrote: > If we have consensus, no need to VOTE. > > > On Jun 9, 2021, at 12:52 PM, Owen Nichols wrote: > > > > Ok, I'm on board with changing stress-new-test from a required PR check > to non-required. It's simple, cod

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

If we have consensus, no need to VOTE. > On Jun 9, 2021, at 12:52 PM, Owen Nichols wrote: > > Ok, I'm on board with changing stress-new-test from a required PR check to non-required. It's simple, codeowners still have the final say, and it neatly avoids the whole topic of overr

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

ith Kirk's original desire to remote stress-new-test as a requirement. All others would remain. Thanks, Mark On 6/9/21, 11:39 AM, "Owen Nichols" wrote: The concern of holding the discussion via PR comments, rather than the dev list, is just that many people will be ex

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

ommitter’s justification, and decide whether to override the failures. In this scenario, the extra burden on code owners arises only at the committer’s request. Dale From: Owen Nichols Date: Wednesday, June 9, 2021 at 11:15 AM To: dev@geode.apache.org Subject: Re: [DISCU

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

owner can request a change or decide to let it go. I think that is sufficient all things considered. Thanks, Mark On 6/9/21, 10:43 AM, "Owen Nichols" wrote: I feel that a traditional [DISCUSS] and [VOTE] on the dev list would be sufficient and proper to grant approval f

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

I feel that a traditional [DISCUSS] and [VOTE] on the dev list would be sufficient and proper to grant approval for an override. Any PR already needs approval from 1 codeowner per area to merge, so codeowners already have a little more say because they hold veto power over the PR. In terms of

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

Thanks Kirk for tackling some of our flakiest tests! I agree, we don't want to discourage anyone interested in paying down tech debt. The Geode community has spoken clearly against bypassing or weakening required PR checks, so relaxing requirements in general might be a tough sell, but I'm

[FYI] PR checks

Concourse job names have been changed to lowercase for conformity[1]. If your PR shows required checks with a status of "Expected -- Waiting for status to be reported", please push another commit. [1] https://concourse-ci.org/config-basics.html#schema.identifier

Re: Reminder to use draft mode

Much less for an ‘external’ contributor to make decisions on our behalf. Has some situation arisen that is driving this? It feels like there is some underlying issue that isn’t being fully communicated. --Jens From: Owen Nichols Date: Thursday, May 6, 2021 at 9:12 AM To: dev@geode.

Re: Reminder to use draft mode

A PR in "Draft" mode simply conveys that at least one more commit is coming before it will be "done". Reviewers generously volunteer their time to look at your PR, and are welcome to look at it while in draft mode if they wish, but if they are quite busy, some may prefer to wait until the PR

Reminder to use draft mode

Please keep your PR in draft mode anytime it is not ready to be reviewed. This includes if you have received request for changes, or if any PR checks are not passing. If you’re reviewing someone’s PR, and notice any checks not passing or you are requesting changes, please also click “Convert

[ANNOUNCE] Apache Geode 1.12.2

-1.12.2 The release artifacts can be downloaded from the project website: https://geode.apache.org/releases/ The release documentation is available at: https://geode.apache.org/docs/guide/112/about_geode.html We would like to thank all the contributors that made the release possible. Regards, Owen

Re: [VOTE] Requiring final keyword on every parameter and local variable

like to study it and do some perf testing on it before supporting it for Geode though. In general, I don't like generated code and it looks like at least some of the features involve generated code -- that's the only potential downside for me. -Kirk On Mon, Apr 19, 2021 at 12:5

Re: [VOTE] Apache Geode 1.12.2.RC1

the requirements of at least 3 PMC members with +1 votes and has the required majority of +1 votes. Apache Geode 1.12.2 has passed the vote and I will finalize the release shortly. Thanks everyone for the great work! -Owen Nichols On 4/21/21, 10:19 AM, "Nabarun Nag" wrote:

Re: [VOTE] Requiring final keyword on every parameter and local variable

Any interest in adopting https://projectlombok.org in Geode? Lombok allow a more readable "val" vs "var" syntax instead of "final" vs "" which could make it easier to do the right thing without "increasing visual noise". On 4/19/21, 12:40 PM, "Dale Emery" wrote: My test for whether

[VOTE] Apache Geode 1.12.2.RC1

://repository.apache.org/content/repositories/orgapachegeode-1080 build runAll Regards Owen Nichols

Re: CODEWATCHERS file effects

r rule: # geode-core/**/org/apache/geode/internal/cache/tier/** > https://github.com/apache/geode/pull/6116 #you are listed as a reviewer because you approved this PR. You were never requested via CODEWATCHERS. ____ From: Owen Nichols Sent: Wednesday, M

Re: CODEWATCHERS file effects

Hi Alberto, is there a specific PR you feel you were added to in error? I spot-checked #6179 and there was one test change in geode-wan so that one seems correct. I am looking for a solution to avoid adding watchers to draft PRs until they are taken out of draft mode, but it's non-trivial

Re: [DISCUSS] Cutting a Geode 1.14.0 release branch

Weeks since support/1.14 cut: 5 Changes backported this week: 7 Blockers we are still waiting on: 8 As of today I am no longer serving as Geode 1.14 Release Manager. Please volunteer if you would like to take over. On 3/12/21, 3:09 PM, "Owen Nichols" wrote: Weeks since su

Re: CODEOWNERS vs CODEWATCHERS

to add contributors to the CODEWATCHERS file? Or is it strictly necessary to be a committer? BR/ Alberto B. ____ De: Owen Nichols Enviado: viernes, 12 de marzo de 2021 23:38 Para: dev@geode.apache.org Asunto: CODEOWNERS vs CODEWATCHERS The

Re: [Proposal] Backport GEODE-9032 to support/1.14

Thanks, this seems related to GEODE-9029 which was already proposed and approved, I assume this is follow-up. Added to blocker board. On 3/18/21, 12:00 PM, "Hale Bales" wrote: Hello, I am putting forward the proposal to backport GEODE-9032 (support SLOWLOG command) to

  1   2   3   4   5   6   >