You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beam.apache.org by Udi Meiri <eh...@google.com> on 2019/12/19 18:18:01 UTC

re: BEAM-8989 fix for 2.18.0 release

The JIRA issue was assigned to me, but I have no background in the issue.
Who would be the most suitable to take care of fixing, testing (Nemo
quickstart), and cherrypicking?

Re: BEAM-8989 fix for 2.18.0 release

Posted by Udi Meiri <eh...@google.com>.

Thanks. I've reassigned the bug to Reuven and pushed the fix back to 2.19.0

On Thu, Dec 19, 2019 at 11:11 AM Luke Cwik <lc...@google.com> wrote:

> Either Salman Raza who developed the PR or Reuven Lax who reviewed it
> would have the most context. I don't know Salman's contact information
> though.
>
> On Thu, Dec 19, 2019 at 10:18 AM Udi Meiri <eh...@google.com> wrote:
>
>> The JIRA issue was assigned to me, but I have no background in the issue.
>> Who would be the most suitable to take care of fixing, testing (Nemo
>> quickstart), and cherrypicking?
>>
>

Re: BEAM-8989 fix for 2.18.0 release

Posted by Luke Cwik <lc...@google.com>.

Either Salman Raza who developed the PR or Reuven Lax who reviewed it would
have the most context. I don't know Salman's contact information though.

On Thu, Dec 19, 2019 at 10:18 AM Udi Meiri <eh...@google.com> wrote:

> The JIRA issue was assigned to me, but I have no background in the issue.
> Who would be the most suitable to take care of fixing, testing (Nemo
> quickstart), and cherrypicking?
>