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/26264 [Bug]: Elevated ser
> On 17 Apr 2023, at 21:14, Robert Burke wrote:
>
> +1 on how to iterate without a Beam 3.0
>
> Often that just means, write the new thing, "support both for a while",make
> it clear how to migrate to the new thing, and the next Major Version just
> drops everything that doesn't cut the musta
While this thread is beginning to move off topic, I think any real Beam 3.0
effort largely should start with "what we know we're going to keep", and
what else a refined/simplified surface looks like for each SDK. But I'm
sure there's some known things to cut too.
And that's ignoring any real break
Hey everyone, I put up a small design doc proposing a user experience for
adding DLQ and pre/post processing map operation support to RunInference.
I'd appreciate any thoughts or comments.
https://docs.google.com/document/d/1hr1SaWraneB9dYSFyGA99JT44oKgGNhT70wz99lmdEU/edit?usp=sharing
Thanks,
Dan
Quick update for everyone, the initial release blockers on the 2.47.0
milestone have been resolved and the RC1 commit has been tagged. I'll be
working on getting RC1 artifacts built now.
On Thu, Apr 13, 2023 at 12:22 PM Ahmet Altay wrote:
> Sounds good. Thank you. And if you need help please rea
Thank you for the update Jack!
On Tue, Apr 18, 2023 at 11:23 AM Jack McCluskey
wrote:
> Quick update for everyone, the initial release blockers on the 2.47.0
> milestone have been resolved and the RC1 commit has been tagged. I'll be
> working on getting RC1 artifacts built now.
>
> On Thu, Apr 1
