Beam High Priority Issue Report (39)

2023-08-08 Thread beamactions
This is your daily summary of Beam's current high priority issues that may need attention. See https://beam.apache.org/contribute/issue-priorities for the meaning and expectations around issue priorities. Unassigned P1 Issues: https://github.com/apache/beam/issues/27892 [Bug]: ignoreUnknow

Re: [VOTE] Vendored Dependency guava 32.1.2-jre Release

2023-08-08 Thread Hong Liang
+1 (non-binding) - Verified 512 checksum of released artifacts - Reviewed test PR and found that the two failing CI tests are due to unrelated issues Thanks for driving this, Yi Hu! Regards, Hong On Thu, Aug 3, 2023 at 8:02 PM Yi Hu via dev wrote: > Hi everyone, > > > Please review the releas

Beam Metrics Report (2023-08-08)

2023-08-08 Thread Apache Jenkins Server
ERROR: File 'src/.test-infra/jenkins/metrics_report/beam-metrics_report.html' does not exist

[RESULT] [VOTE] Vendored Dependency guava 32.1.2-jre Release

2023-08-08 Thread Yi Hu via dev
I'm happy to announce that we have unanimously approved this release. There are 5 approving votes, 3 of which are binding: * Chamikara Jayalath * Ahmet Altay * Robert Bradshaw There are no disapproving votes. Thanks everyone! -- Yi Hu, (he/him/his) Software Engineer

Re: [RESULT] [VOTE] Vendored Dependency guava 32.1.2-jre Release

2023-08-08 Thread Yi Hu via dev
Hi, Could a PMC member please help me finalize the source release? That is copy https://dist.apache.org/repos/dist/dev/beam/vendor/guava-32_1_2-jre/ into https://dist.apache.org/repos/dist/release/beam/vendor/guava-32_1_2-jre using svn. Thanks! Regards, Yi On Tue, Aug 8, 2023 at 9:01 AM Yi Hu w

[Discuss] Get rid of OWNERS files

2023-08-08 Thread Danny McCormick via dev
Hey everyone, I'd like to propose getting rid of OWNERS files from the Beam repo. Right now, I don't think they are serving a meaningful purpose: - Many OWNERS files are outdated and point to people who are no longer actively involved in the project (examples: 1

Re: [Discuss] Get rid of OWNERS files

2023-08-08 Thread XQ Hu via dev
+1. On Tue, Aug 8, 2023 at 10:55 AM Danny McCormick via dev wrote: > Hey everyone, I'd like to propose getting rid of OWNERS files from the > Beam repo. Right now, I don't think they are serving a meaningful purpose: > > - Many OWNERS files are outdated and point to people who are no longer > ac

Re: [Discuss] Get rid of OWNERS files

2023-08-08 Thread Kerry Donny-Clark via dev
Thanks Danny! I agree. OWNERS causes unnecessary friction, and doesn't provide value. Kerry On Tue, Aug 8, 2023 at 10:55 AM Danny McCormick via dev wrote: > Hey everyone, I'd like to propose getting rid of OWNERS files from the > Beam repo. Right now, I don't think they are serving a meaningful

Re: [Discuss] Get rid of OWNERS files

2023-08-08 Thread Alexey Romanenko
I’m generally agree with this (initially that was a good intention imho) but what could be an alternative for this? Review bot also may assign reviewers that are no longer active on the project. — Alexey > On 8 Aug 2023, at 16:55, Danny McCormick via dev wrote: > > Hey everyone, I'd like to

Re: [Discuss] Get rid of OWNERS files

2023-08-08 Thread Robert Burke
Either we keep OWNERS and have the review bot use them, or we remove them and use the reviews bot config as the single source of truth. The bot is less likely to go out of date since it's at least active in how it behaves. I agree it doesn't necessarily solve the problem of things getting out of d

Re: [Discuss] Get rid of OWNERS files

2023-08-08 Thread Danny McCormick via dev
> I’m generally agree with this (initially that was a good intention imho) but what could be an alternative for this? Review bot also may assign reviewers that are no longer active on the project. I propose that the reviewer bot be the full replacement, and I agree with Robert's comments about it

Re: [RESULT] [VOTE] Vendored Dependency guava 32.1.2-jre Release

2023-08-08 Thread Yi Hu via dev
Hi everyone, The vendored guava 32.1.2-jre is now released, and beam is switched to use this version [1]. If you have working pull requests that have called vendor guava directly (Java SDK), it may need to rebase the PR branch onto the latest master branch, and switch `guava.v26_0_jre` namespace t