youngoli commented on PR #625:
URL: https://github.com/apache/beam-site/pull/625#issuecomment-1097458268
R: @TheNeuralBit
As per the release instructions, won't be merging this until the release is
actually finalized, but I'm just adding you as a reviewer in advance.
--
This is an
Thanks for doing so much work verifying this and analyzing it! It really
seems like we did all this for mockito, so it has very little risk of
impacting users. And you've verified it is working with mockito now. So I
think I'm in favor of unvendoring. This will make it much easier to get
bugfixes,
This is your daily summary of Beam's current P1 issues, not including flaky
tests
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake).
See
This is your daily summary of Beam's current flaky tests
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake)
These are P1 issues because they have a major negative impact on the community
and make it hard to
+1 to cherry-pick. It will make the release broken for enough users that we
shouldn't produce a release without the fix.
Kenn
On Sat, Apr 9, 2022 at 4:05 PM Ahmet Altay wrote:
> +1 to cherry picking https://github.com/apache/beam/pull/17329 to the
> release branch.
>
> For completeness,
