Re: [Discuss] Idea to increase RC voting participation

I'd probably vote to include both the issue filer and the contributor. It is pretty equally straightforward - one way to do this would be using all issues related to that release's milestone and extracting the issue author and the issue closer. This does leave out the (unfortunately sizable) set

Beam High Priority Issue Report (46)

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/29099 [Bug]: FnAPI Java

Re: [YAML] Aggregations

+1 on your proposal. On Fri, Oct 20, 2023 at 4:59 PM Robert Bradshaw via dev wrote: > On Fri, Oct 20, 2023 at 11:35 AM Kenneth Knowles wrote: > > > > A couple other bits on having an expression language: > > > > - You already have Python lambdas at places, right? so that's quite a > lot more

Re: [Discuss] Idea to increase RC voting participation

+1. This is a great idea to try. @Danny McCormick FYI as our next release manager. On Wed, Oct 18, 2023 at 2:30 PM Johanna Öjeling via dev wrote: > When I have contributed to Apache Airflow, they have tagged all > contributors concerned in a GitHub issue when the RC is available and asked > us

Re: [PYTHON] partitioner utilities?

+1 on this idea. Thanks! On Thu, Oct 19, 2023 at 3:40 PM Joey Tran wrote: > Yeah, I already implemented these partitioners for my use case (I just > pasted the classnames/docstrings for them) and I used both combiners.Top > and combiners.Sample. > > In fact, before writing these partitioners I

Re: [Discuss] Idea to increase RC voting participation

So to summarize, I think there's broad consensus (or at least lazy consensus) around the following: - (1) Updating our release email/guidelines to be more specific about what we mean by release validation/how to be helpful during this process. This includes both encouraging validation within each

Re: [PYTHON] partitioner utilities?

PR for top: https://github.com/apache/beam/pull/29106 On Mon, Oct 23, 2023 at 10:11 AM XQ Hu via dev wrote: > +1 on this idea. Thanks! > > On Thu, Oct 19, 2023 at 3:40 PM Joey Tran > wrote: > >> Yeah, I already implemented these partitioners for my use case (I just >> pasted the

Re: [Discuss] Idea to increase RC voting participation

Thanks for summarizing. For (1), I will send out this Google doc around the time of the next release where we can crowdsource ways to test the RC. I think it'd be valuable to approach a guide like this to be

Re: [Discuss] Idea to increase RC voting participation

On Mon, Oct 23, 2023 at 7:26 AM Danny McCormick via dev wrote: > So to summarize, I think there's broad consensus (or at least lazy > consensus) around the following: > > - (1) Updating our release email/guidelines to be more specific about what > we mean by release validation/how to be helpful

Re: [Discuss] Idea to increase RC voting participation

Yes that's a good point to include also those who created the issue. On Mon, Oct 23, 2023, 19:18 Robert Bradshaw via dev wrote: > On Mon, Oct 23, 2023 at 7:26 AM Danny McCormick via dev < > dev@beam.apache.org> wrote: > >> So to summarize, I think there's broad consensus (or at least lazy >>