You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Yichi Zhang <zy...@google.com> on 2022/05/02 17:45:23 UTC

[Release] 2.39.0 release update

Hi, Beam dev community,

Opening this thread for Beam 2.39.0 release updates. Progress will be
updated here.

Friendly reminder that the 2.39.0 release branch will be cut in 2 days on
05/04/2022. Please mark blocking issues with fix version 2.39.0 if
necessary. Current blocking issues can be seen at link
<https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
.

Thanks,
Yichi

Re: [Release] 2.39.0 release update

Posted by Ahmet Altay <al...@google.com>.
Thank you very much Yichi! Let us know if we can help!

On Fri, May 13, 2022 at 5:36 PM Yichi Zhang <zy...@google.com> wrote:

> Update: all the blocking issues are resolved, building RC1 now.
>
> On Tue, May 10, 2022 at 7:36 PM Ahmet Altay <al...@google.com> wrote:
>
>>
>>
>> On Tue, May 10, 2022 at 8:34 PM Ryan Thompson <ry...@google.com>
>> wrote:
>>
>>> The PR needs to go green, and it needs an lgtm from Valentyn & Ken.
>>> Unless there is some blocker I don't foresee it should be merged EOW.
>>>
>>
>> Thank you. @Kenneth Knowles <kl...@google.com> @Valentyn Tymofieiev
>> <va...@google.com> - would you be able to review this change please?
>>
>>
>>>
>>> On Tue, May 10, 2022 at 9:15 PM Ahmet Altay <al...@google.com> wrote:
>>>
>>>>
>>>>
>>>> On Tue, May 10, 2022 at 5:49 PM Yichi Zhang <zy...@google.com> wrote:
>>>>
>>>>> It now just waiting for https://github.com/apache/beam/pull/17244.
>>>>>
>>>>
>>>> Thank you Yichi!
>>>>
>>>> @Kenneth Knowles <kl...@google.com> @Ryan Thompson
>>>> <ry...@google.com> - I see that you are both active on the PR
>>>> right now, please let us know when would be the earliest to merge this
>>>> change.
>>>>
>>>>
>>>>>
>>>>> On Mon, May 9, 2022 at 6:06 PM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> Thank you Yichi.
>>>>>>
>>>>>> On Mon, May 9, 2022 at 6:38 PM Yichi Zhang <zy...@google.com> wrote:
>>>>>>
>>>>>>> There's two blocking issue/FR:
>>>>>>> https://issues.apache.org/jira/browse/BEAM-14429
>>>>>>>
>>>>>>
>>>>>> Added a few folks to the dev list thread who might help. But if it is
>>>>>> still unblocked, I would suggest not making it a release blocker because it
>>>>>> is already an existing issue.
>>>>>>
>>>>>> /cc @Chamikara Jayalath <ch...@google.com> - this is IO related.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/BEAM-14412
>>>>>>>
>>>>>>
>>>>>> @Kenneth Knowles <kl...@google.com> @Ryan Thompson
>>>>>> <ry...@google.com> - please let us know what your timeline is
>>>>>> for completing the open PR (https://github.com/apache/beam/pull/17244
>>>>>> ).
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I believe there's one outstanding PR under review for BEAM-14412
>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14412>:
>>>>>>> https://github.com/apache/beam/pull/17244.
>>>>>>>
>>>>>>> For https://issues.apache.org/jira/browse/BEAM-14429, it appears to
>>>>>>> be an issue that existed for a long time(exists in previous versions).
>>>>>>> I think it is an issue significant enough to influence the
>>>>>>> correctness of UnboundedSourceUnboundedSourceAsSDFWrapperFn.
>>>>>>> I'm unfamiliar with this piece of code and I'm still trying to
>>>>>>> figure out the right fix. There's another thread I created in the dev
>>>>>>> mailing list regarding the issue.
>>>>>>> I opened https://github.com/apache/beam/pull/17596 as a temp
>>>>>>> improvement but this shouldn't be the right solution.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, May 9, 2022 at 4:56 PM Ahmet Altay <al...@google.com> wrote:
>>>>>>>
>>>>>>>> Yichi, what is the current state of the release? Is it still
>>>>>>>> blocked, do you need help?
>>>>>>>>
>>>>>>>> On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> > The test reveals a correctness bug so I'd prefer to cherry pick
>>>>>>>>> the PR [1] into 2.39.0, if possible.
>>>>>>>>> > [1] https://github.com/apache/beam/pull/17504
>>>>>>>>>
>>>>>>>>> Created cherrypick https://github.com/apache/beam/pull/17561
>>>>>>>>>
>>>>>>>>> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <
>>>>>>>>> jrmccluskey@google.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hey everyone,
>>>>>>>>>>
>>>>>>>>>> I ran into a bug that caused an issue with the new
>>>>>>>>>> self-checkpointing feature in Go this morning. Rather than cherrypick the
>>>>>>>>>> fix for an experimental feature while we're still testing it, I've filed
>>>>>>>>>> BEAM-14424 <https://issues.apache.org/jira/browse/BEAM-14424> and
>>>>>>>>>> put together a PR for the release branch (
>>>>>>>>>> https://github.com/apache/beam/pull/17562)  to revert the
>>>>>>>>>> feature being enabled and called-out in CHANGES.md as being available on an
>>>>>>>>>> experimental basis. While we did call the feature out as experimental, the
>>>>>>>>>> issue prevents self-checkpointing from being used as expected and we should
>>>>>>>>>> avoid having users try it.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Jack McCluskey
>>>>>>>>>>
>>>>>>>>>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> BEAM-14196 is just merged. I changed the priority to P1 (the
>>>>>>>>>>> original JIRA was about adding test, but the fix for FlinkRunner was simple
>>>>>>>>>>> enough, so it was added to the PR). The test reveals a correctness bug so
>>>>>>>>>>> I'd prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>>>>>>>>>
>>>>>>>>>>>  Jan
>>>>>>>>>>>
>>>>>>>>>>> [1] https://github.com/apache/beam/pull/17504
>>>>>>>>>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Update:
>>>>>>>>>>>> - release-2.39.0 branch has been cut.
>>>>>>>>>>>> - 5 remaining blocking issues in link
>>>>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>>>>> .
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2 of these issues are P2s. Are they release blockers?
>>>>>>>>>>>
>>>>>>>>>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>>>>>>>>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Thank you very much Yichi. Please let us know if you need any
>>>>>>>>>>>>> help.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi, Beam dev community,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress
>>>>>>>>>>>>>> will be updated here.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Friendly reminder that the 2.39.0 release branch will be cut
>>>>>>>>>>>>>> in 2 days on 05/04/2022. Please mark blocking issues with fix version
>>>>>>>>>>>>>> 2.39.0 if necessary. Current blocking issues can be seen at
>>>>>>>>>>>>>> link
>>>>>>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>>>>>>> .
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Yichi
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>

Re: [Release] 2.39.0 release update

Posted by Yichi Zhang <zy...@google.com>.
Update: all the blocking issues are resolved, building RC1 now.

On Tue, May 10, 2022 at 7:36 PM Ahmet Altay <al...@google.com> wrote:

>
>
> On Tue, May 10, 2022 at 8:34 PM Ryan Thompson <ry...@google.com>
> wrote:
>
>> The PR needs to go green, and it needs an lgtm from Valentyn & Ken.
>> Unless there is some blocker I don't foresee it should be merged EOW.
>>
>
> Thank you. @Kenneth Knowles <kl...@google.com> @Valentyn Tymofieiev
> <va...@google.com> - would you be able to review this change please?
>
>
>>
>> On Tue, May 10, 2022 at 9:15 PM Ahmet Altay <al...@google.com> wrote:
>>
>>>
>>>
>>> On Tue, May 10, 2022 at 5:49 PM Yichi Zhang <zy...@google.com> wrote:
>>>
>>>> It now just waiting for https://github.com/apache/beam/pull/17244.
>>>>
>>>
>>> Thank you Yichi!
>>>
>>> @Kenneth Knowles <kl...@google.com> @Ryan Thompson
>>> <ry...@google.com> - I see that you are both active on the PR
>>> right now, please let us know when would be the earliest to merge this
>>> change.
>>>
>>>
>>>>
>>>> On Mon, May 9, 2022 at 6:06 PM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Thank you Yichi.
>>>>>
>>>>> On Mon, May 9, 2022 at 6:38 PM Yichi Zhang <zy...@google.com> wrote:
>>>>>
>>>>>> There's two blocking issue/FR:
>>>>>> https://issues.apache.org/jira/browse/BEAM-14429
>>>>>>
>>>>>
>>>>> Added a few folks to the dev list thread who might help. But if it is
>>>>> still unblocked, I would suggest not making it a release blocker because it
>>>>> is already an existing issue.
>>>>>
>>>>> /cc @Chamikara Jayalath <ch...@google.com> - this is IO related.
>>>>>
>>>>>
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/BEAM-14412
>>>>>>
>>>>>
>>>>> @Kenneth Knowles <kl...@google.com> @Ryan Thompson
>>>>> <ry...@google.com> - please let us know what your timeline is
>>>>> for completing the open PR (https://github.com/apache/beam/pull/17244
>>>>> ).
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> I believe there's one outstanding PR under review for BEAM-14412
>>>>>> <https://issues.apache.org/jira/browse/BEAM-14412>:
>>>>>> https://github.com/apache/beam/pull/17244.
>>>>>>
>>>>>> For https://issues.apache.org/jira/browse/BEAM-14429, it appears to
>>>>>> be an issue that existed for a long time(exists in previous versions).
>>>>>> I think it is an issue significant enough to influence the
>>>>>> correctness of UnboundedSourceUnboundedSourceAsSDFWrapperFn.
>>>>>> I'm unfamiliar with this piece of code and I'm still trying to figure
>>>>>> out the right fix. There's another thread I created in the dev mailing list
>>>>>> regarding the issue.
>>>>>> I opened https://github.com/apache/beam/pull/17596 as a temp
>>>>>> improvement but this shouldn't be the right solution.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, May 9, 2022 at 4:56 PM Ahmet Altay <al...@google.com> wrote:
>>>>>>
>>>>>>> Yichi, what is the current state of the release? Is it still
>>>>>>> blocked, do you need help?
>>>>>>>
>>>>>>> On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> > The test reveals a correctness bug so I'd prefer to cherry pick
>>>>>>>> the PR [1] into 2.39.0, if possible.
>>>>>>>> > [1] https://github.com/apache/beam/pull/17504
>>>>>>>>
>>>>>>>> Created cherrypick https://github.com/apache/beam/pull/17561
>>>>>>>>
>>>>>>>> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <
>>>>>>>> jrmccluskey@google.com> wrote:
>>>>>>>>
>>>>>>>>> Hey everyone,
>>>>>>>>>
>>>>>>>>> I ran into a bug that caused an issue with the new
>>>>>>>>> self-checkpointing feature in Go this morning. Rather than cherrypick the
>>>>>>>>> fix for an experimental feature while we're still testing it, I've filed
>>>>>>>>> BEAM-14424 <https://issues.apache.org/jira/browse/BEAM-14424> and
>>>>>>>>> put together a PR for the release branch (
>>>>>>>>> https://github.com/apache/beam/pull/17562)  to revert the feature
>>>>>>>>> being enabled and called-out in CHANGES.md as being available on an
>>>>>>>>> experimental basis. While we did call the feature out as experimental, the
>>>>>>>>> issue prevents self-checkpointing from being used as expected and we should
>>>>>>>>> avoid having users try it.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Jack McCluskey
>>>>>>>>>
>>>>>>>>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> BEAM-14196 is just merged. I changed the priority to P1 (the
>>>>>>>>>> original JIRA was about adding test, but the fix for FlinkRunner was simple
>>>>>>>>>> enough, so it was added to the PR). The test reveals a correctness bug so
>>>>>>>>>> I'd prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>>>>>>>>
>>>>>>>>>>  Jan
>>>>>>>>>>
>>>>>>>>>> [1] https://github.com/apache/beam/pull/17504
>>>>>>>>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Update:
>>>>>>>>>>> - release-2.39.0 branch has been cut.
>>>>>>>>>>> - 5 remaining blocking issues in link
>>>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>>>> .
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2 of these issues are P2s. Are they release blockers?
>>>>>>>>>>
>>>>>>>>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>>>>>>>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thank you very much Yichi. Please let us know if you need any
>>>>>>>>>>>> help.
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi, Beam dev community,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress
>>>>>>>>>>>>> will be updated here.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Friendly reminder that the 2.39.0 release branch will be cut
>>>>>>>>>>>>> in 2 days on 05/04/2022. Please mark blocking issues with fix version
>>>>>>>>>>>>> 2.39.0 if necessary. Current blocking issues can be seen at
>>>>>>>>>>>>> link
>>>>>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>>>>>> .
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Yichi
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>

Re: [Release] 2.39.0 release update

Posted by Ahmet Altay <al...@google.com>.
On Tue, May 10, 2022 at 8:34 PM Ryan Thompson <ry...@google.com>
wrote:

> The PR needs to go green, and it needs an lgtm from Valentyn & Ken.
> Unless there is some blocker I don't foresee it should be merged EOW.
>

Thank you. @Kenneth Knowles <kl...@google.com> @Valentyn Tymofieiev
<va...@google.com> - would you be able to review this change please?


>
> On Tue, May 10, 2022 at 9:15 PM Ahmet Altay <al...@google.com> wrote:
>
>>
>>
>> On Tue, May 10, 2022 at 5:49 PM Yichi Zhang <zy...@google.com> wrote:
>>
>>> It now just waiting for https://github.com/apache/beam/pull/17244.
>>>
>>
>> Thank you Yichi!
>>
>> @Kenneth Knowles <kl...@google.com> @Ryan Thompson
>> <ry...@google.com> - I see that you are both active on the PR
>> right now, please let us know when would be the earliest to merge this
>> change.
>>
>>
>>>
>>> On Mon, May 9, 2022 at 6:06 PM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Thank you Yichi.
>>>>
>>>> On Mon, May 9, 2022 at 6:38 PM Yichi Zhang <zy...@google.com> wrote:
>>>>
>>>>> There's two blocking issue/FR:
>>>>> https://issues.apache.org/jira/browse/BEAM-14429
>>>>>
>>>>
>>>> Added a few folks to the dev list thread who might help. But if it is
>>>> still unblocked, I would suggest not making it a release blocker because it
>>>> is already an existing issue.
>>>>
>>>> /cc @Chamikara Jayalath <ch...@google.com> - this is IO related.
>>>>
>>>>
>>>>>
>>>>> https://issues.apache.org/jira/browse/BEAM-14412
>>>>>
>>>>
>>>> @Kenneth Knowles <kl...@google.com> @Ryan Thompson
>>>> <ry...@google.com> - please let us know what your timeline is
>>>> for completing the open PR (https://github.com/apache/beam/pull/17244).
>>>>
>>>>
>>>>>
>>>>>
>>>>> I believe there's one outstanding PR under review for BEAM-14412
>>>>> <https://issues.apache.org/jira/browse/BEAM-14412>:
>>>>> https://github.com/apache/beam/pull/17244.
>>>>>
>>>>> For https://issues.apache.org/jira/browse/BEAM-14429, it appears to
>>>>> be an issue that existed for a long time(exists in previous versions).
>>>>> I think it is an issue significant enough to influence the correctness
>>>>> of UnboundedSourceUnboundedSourceAsSDFWrapperFn.
>>>>> I'm unfamiliar with this piece of code and I'm still trying to figure
>>>>> out the right fix. There's another thread I created in the dev mailing list
>>>>> regarding the issue.
>>>>> I opened https://github.com/apache/beam/pull/17596 as a temp
>>>>> improvement but this shouldn't be the right solution.
>>>>>
>>>>>
>>>>>
>>>>> On Mon, May 9, 2022 at 4:56 PM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> Yichi, what is the current state of the release? Is it still blocked,
>>>>>> do you need help?
>>>>>>
>>>>>> On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> > The test reveals a correctness bug so I'd prefer to cherry pick
>>>>>>> the PR [1] into 2.39.0, if possible.
>>>>>>> > [1] https://github.com/apache/beam/pull/17504
>>>>>>>
>>>>>>> Created cherrypick https://github.com/apache/beam/pull/17561
>>>>>>>
>>>>>>> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <
>>>>>>> jrmccluskey@google.com> wrote:
>>>>>>>
>>>>>>>> Hey everyone,
>>>>>>>>
>>>>>>>> I ran into a bug that caused an issue with the new
>>>>>>>> self-checkpointing feature in Go this morning. Rather than cherrypick the
>>>>>>>> fix for an experimental feature while we're still testing it, I've filed
>>>>>>>> BEAM-14424 <https://issues.apache.org/jira/browse/BEAM-14424> and
>>>>>>>> put together a PR for the release branch (
>>>>>>>> https://github.com/apache/beam/pull/17562)  to revert the feature
>>>>>>>> being enabled and called-out in CHANGES.md as being available on an
>>>>>>>> experimental basis. While we did call the feature out as experimental, the
>>>>>>>> issue prevents self-checkpointing from being used as expected and we should
>>>>>>>> avoid having users try it.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Jack McCluskey
>>>>>>>>
>>>>>>>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> BEAM-14196 is just merged. I changed the priority to P1 (the
>>>>>>>>> original JIRA was about adding test, but the fix for FlinkRunner was simple
>>>>>>>>> enough, so it was added to the PR). The test reveals a correctness bug so
>>>>>>>>> I'd prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>>>>>>>
>>>>>>>>>  Jan
>>>>>>>>>
>>>>>>>>> [1] https://github.com/apache/beam/pull/17504
>>>>>>>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Update:
>>>>>>>>>> - release-2.39.0 branch has been cut.
>>>>>>>>>> - 5 remaining blocking issues in link
>>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>>> .
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2 of these issues are P2s. Are they release blockers?
>>>>>>>>>
>>>>>>>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>>>>>>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thank you very much Yichi. Please let us know if you need any
>>>>>>>>>>> help.
>>>>>>>>>>>
>>>>>>>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi, Beam dev community,
>>>>>>>>>>>>
>>>>>>>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress
>>>>>>>>>>>> will be updated here.
>>>>>>>>>>>>
>>>>>>>>>>>> Friendly reminder that the 2.39.0 release branch will be cut in
>>>>>>>>>>>> 2 days on 05/04/2022. Please mark blocking issues with fix version 2.39.0
>>>>>>>>>>>> if necessary. Current blocking issues can be seen at link
>>>>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>>>>> .
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Yichi
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>

Re: [Release] 2.39.0 release update

Posted by Ryan Thompson <ry...@google.com>.
The PR needs to go green, and it needs an lgtm from Valentyn & Ken.  Unless
there is some blocker I don't foresee it should be merged EOW.

On Tue, May 10, 2022 at 9:15 PM Ahmet Altay <al...@google.com> wrote:

>
>
> On Tue, May 10, 2022 at 5:49 PM Yichi Zhang <zy...@google.com> wrote:
>
>> It now just waiting for https://github.com/apache/beam/pull/17244.
>>
>
> Thank you Yichi!
>
> @Kenneth Knowles <kl...@google.com> @Ryan Thompson <ry...@google.com> -
> I see that you are both active on the PR right now, please let us know when
> would be the earliest to merge this change.
>
>
>>
>> On Mon, May 9, 2022 at 6:06 PM Ahmet Altay <al...@google.com> wrote:
>>
>>> Thank you Yichi.
>>>
>>> On Mon, May 9, 2022 at 6:38 PM Yichi Zhang <zy...@google.com> wrote:
>>>
>>>> There's two blocking issue/FR:
>>>> https://issues.apache.org/jira/browse/BEAM-14429
>>>>
>>>
>>> Added a few folks to the dev list thread who might help. But if it is
>>> still unblocked, I would suggest not making it a release blocker because it
>>> is already an existing issue.
>>>
>>> /cc @Chamikara Jayalath <ch...@google.com> - this is IO related.
>>>
>>>
>>>>
>>>> https://issues.apache.org/jira/browse/BEAM-14412
>>>>
>>>
>>> @Kenneth Knowles <kl...@google.com> @Ryan Thompson
>>> <ry...@google.com> - please let us know what your timeline is
>>> for completing the open PR (https://github.com/apache/beam/pull/17244).
>>>
>>>
>>>>
>>>>
>>>> I believe there's one outstanding PR under review for BEAM-14412
>>>> <https://issues.apache.org/jira/browse/BEAM-14412>:
>>>> https://github.com/apache/beam/pull/17244.
>>>>
>>>> For https://issues.apache.org/jira/browse/BEAM-14429, it appears to be
>>>> an issue that existed for a long time(exists in previous versions).
>>>> I think it is an issue significant enough to influence the correctness
>>>> of UnboundedSourceUnboundedSourceAsSDFWrapperFn.
>>>> I'm unfamiliar with this piece of code and I'm still trying to figure
>>>> out the right fix. There's another thread I created in the dev mailing list
>>>> regarding the issue.
>>>> I opened https://github.com/apache/beam/pull/17596 as a temp
>>>> improvement but this shouldn't be the right solution.
>>>>
>>>>
>>>>
>>>> On Mon, May 9, 2022 at 4:56 PM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Yichi, what is the current state of the release? Is it still blocked,
>>>>> do you need help?
>>>>>
>>>>> On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com> wrote:
>>>>>
>>>>>> > The test reveals a correctness bug so I'd prefer to cherry pick the
>>>>>> PR [1] into 2.39.0, if possible.
>>>>>> > [1] https://github.com/apache/beam/pull/17504
>>>>>>
>>>>>> Created cherrypick https://github.com/apache/beam/pull/17561
>>>>>>
>>>>>> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <
>>>>>> jrmccluskey@google.com> wrote:
>>>>>>
>>>>>>> Hey everyone,
>>>>>>>
>>>>>>> I ran into a bug that caused an issue with the new
>>>>>>> self-checkpointing feature in Go this morning. Rather than cherrypick the
>>>>>>> fix for an experimental feature while we're still testing it, I've filed
>>>>>>> BEAM-14424 <https://issues.apache.org/jira/browse/BEAM-14424> and
>>>>>>> put together a PR for the release branch (
>>>>>>> https://github.com/apache/beam/pull/17562)  to revert the feature
>>>>>>> being enabled and called-out in CHANGES.md as being available on an
>>>>>>> experimental basis. While we did call the feature out as experimental, the
>>>>>>> issue prevents self-checkpointing from being used as expected and we should
>>>>>>> avoid having users try it.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jack McCluskey
>>>>>>>
>>>>>>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz> wrote:
>>>>>>>
>>>>>>>> BEAM-14196 is just merged. I changed the priority to P1 (the
>>>>>>>> original JIRA was about adding test, but the fix for FlinkRunner was simple
>>>>>>>> enough, so it was added to the PR). The test reveals a correctness bug so
>>>>>>>> I'd prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>>>>>>
>>>>>>>>  Jan
>>>>>>>>
>>>>>>>> [1] https://github.com/apache/beam/pull/17504
>>>>>>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Update:
>>>>>>>>> - release-2.39.0 branch has been cut.
>>>>>>>>> - 5 remaining blocking issues in link
>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>> .
>>>>>>>>>
>>>>>>>>
>>>>>>>> 2 of these issues are P2s. Are they release blockers?
>>>>>>>>
>>>>>>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>>>>>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Thank you very much Yichi. Please let us know if you need any
>>>>>>>>>> help.
>>>>>>>>>>
>>>>>>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi, Beam dev community,
>>>>>>>>>>>
>>>>>>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress
>>>>>>>>>>> will be updated here.
>>>>>>>>>>>
>>>>>>>>>>> Friendly reminder that the 2.39.0 release branch will be cut in
>>>>>>>>>>> 2 days on 05/04/2022. Please mark blocking issues with fix version 2.39.0
>>>>>>>>>>> if necessary. Current blocking issues can be seen at link
>>>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>>>> .
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Yichi
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>

Re: [Release] 2.39.0 release update

Posted by Ahmet Altay <al...@google.com>.
On Tue, May 10, 2022 at 5:49 PM Yichi Zhang <zy...@google.com> wrote:

> It now just waiting for https://github.com/apache/beam/pull/17244.
>

Thank you Yichi!

@Kenneth Knowles <kl...@google.com> @Ryan Thompson <ry...@google.com> -
I see that you are both active on the PR right now, please let us know when
would be the earliest to merge this change.


>
> On Mon, May 9, 2022 at 6:06 PM Ahmet Altay <al...@google.com> wrote:
>
>> Thank you Yichi.
>>
>> On Mon, May 9, 2022 at 6:38 PM Yichi Zhang <zy...@google.com> wrote:
>>
>>> There's two blocking issue/FR:
>>> https://issues.apache.org/jira/browse/BEAM-14429
>>>
>>
>> Added a few folks to the dev list thread who might help. But if it is
>> still unblocked, I would suggest not making it a release blocker because it
>> is already an existing issue.
>>
>> /cc @Chamikara Jayalath <ch...@google.com> - this is IO related.
>>
>>
>>>
>>> https://issues.apache.org/jira/browse/BEAM-14412
>>>
>>
>> @Kenneth Knowles <kl...@google.com> @Ryan Thompson
>> <ry...@google.com> - please let us know what your timeline is for
>> completing the open PR (https://github.com/apache/beam/pull/17244).
>>
>>
>>>
>>>
>>> I believe there's one outstanding PR under review for BEAM-14412
>>> <https://issues.apache.org/jira/browse/BEAM-14412>:
>>> https://github.com/apache/beam/pull/17244.
>>>
>>> For https://issues.apache.org/jira/browse/BEAM-14429, it appears to be
>>> an issue that existed for a long time(exists in previous versions).
>>> I think it is an issue significant enough to influence the correctness
>>> of UnboundedSourceUnboundedSourceAsSDFWrapperFn.
>>> I'm unfamiliar with this piece of code and I'm still trying to figure
>>> out the right fix. There's another thread I created in the dev mailing list
>>> regarding the issue.
>>> I opened https://github.com/apache/beam/pull/17596 as a temp
>>> improvement but this shouldn't be the right solution.
>>>
>>>
>>>
>>> On Mon, May 9, 2022 at 4:56 PM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Yichi, what is the current state of the release? Is it still blocked,
>>>> do you need help?
>>>>
>>>> On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com> wrote:
>>>>
>>>>> > The test reveals a correctness bug so I'd prefer to cherry pick the
>>>>> PR [1] into 2.39.0, if possible.
>>>>> > [1] https://github.com/apache/beam/pull/17504
>>>>>
>>>>> Created cherrypick https://github.com/apache/beam/pull/17561
>>>>>
>>>>> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <jr...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Hey everyone,
>>>>>>
>>>>>> I ran into a bug that caused an issue with the new self-checkpointing
>>>>>> feature in Go this morning. Rather than cherrypick the fix for an
>>>>>> experimental feature while we're still testing it, I've filed
>>>>>> BEAM-14424 <https://issues.apache.org/jira/browse/BEAM-14424> and
>>>>>> put together a PR for the release branch (
>>>>>> https://github.com/apache/beam/pull/17562)  to revert the feature
>>>>>> being enabled and called-out in CHANGES.md as being available on an
>>>>>> experimental basis. While we did call the feature out as experimental, the
>>>>>> issue prevents self-checkpointing from being used as expected and we should
>>>>>> avoid having users try it.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jack McCluskey
>>>>>>
>>>>>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz> wrote:
>>>>>>
>>>>>>> BEAM-14196 is just merged. I changed the priority to P1 (the
>>>>>>> original JIRA was about adding test, but the fix for FlinkRunner was simple
>>>>>>> enough, so it was added to the PR). The test reveals a correctness bug so
>>>>>>> I'd prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>>>>>
>>>>>>>  Jan
>>>>>>>
>>>>>>> [1] https://github.com/apache/beam/pull/17504
>>>>>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Update:
>>>>>>>> - release-2.39.0 branch has been cut.
>>>>>>>> - 5 remaining blocking issues in link
>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>> .
>>>>>>>>
>>>>>>>
>>>>>>> 2 of these issues are P2s. Are they release blockers?
>>>>>>>
>>>>>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>>>>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thank you very much Yichi. Please let us know if you need any help.
>>>>>>>>>
>>>>>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi, Beam dev community,
>>>>>>>>>>
>>>>>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress
>>>>>>>>>> will be updated here.
>>>>>>>>>>
>>>>>>>>>> Friendly reminder that the 2.39.0 release branch will be cut in 2
>>>>>>>>>> days on 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>>>>>>>>>> necessary. Current blocking issues can be seen at link
>>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>>> .
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Yichi
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>

Re: [Release] 2.39.0 release update

Posted by Yichi Zhang <zy...@google.com>.
It now just waiting for https://github.com/apache/beam/pull/17244.

On Mon, May 9, 2022 at 6:06 PM Ahmet Altay <al...@google.com> wrote:

> Thank you Yichi.
>
> On Mon, May 9, 2022 at 6:38 PM Yichi Zhang <zy...@google.com> wrote:
>
>> There's two blocking issue/FR:
>> https://issues.apache.org/jira/browse/BEAM-14429
>>
>
> Added a few folks to the dev list thread who might help. But if it is
> still unblocked, I would suggest not making it a release blocker because it
> is already an existing issue.
>
> /cc @Chamikara Jayalath <ch...@google.com> - this is IO related.
>
>
>>
>> https://issues.apache.org/jira/browse/BEAM-14412
>>
>
> @Kenneth Knowles <kl...@google.com> @Ryan Thompson <ry...@google.com> -
> please let us know what your timeline is for completing the open PR (
> https://github.com/apache/beam/pull/17244).
>
>
>>
>>
>> I believe there's one outstanding PR under review for BEAM-14412
>> <https://issues.apache.org/jira/browse/BEAM-14412>:
>> https://github.com/apache/beam/pull/17244.
>>
>> For https://issues.apache.org/jira/browse/BEAM-14429, it appears to be
>> an issue that existed for a long time(exists in previous versions).
>> I think it is an issue significant enough to influence the correctness of
>> UnboundedSourceUnboundedSourceAsSDFWrapperFn.
>> I'm unfamiliar with this piece of code and I'm still trying to figure out
>> the right fix. There's another thread I created in the dev mailing list
>> regarding the issue.
>> I opened https://github.com/apache/beam/pull/17596 as a temp improvement
>> but this shouldn't be the right solution.
>>
>>
>>
>> On Mon, May 9, 2022 at 4:56 PM Ahmet Altay <al...@google.com> wrote:
>>
>>> Yichi, what is the current state of the release? Is it still blocked, do
>>> you need help?
>>>
>>> On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com> wrote:
>>>
>>>> > The test reveals a correctness bug so I'd prefer to cherry pick the
>>>> PR [1] into 2.39.0, if possible.
>>>> > [1] https://github.com/apache/beam/pull/17504
>>>>
>>>> Created cherrypick https://github.com/apache/beam/pull/17561
>>>>
>>>> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <jr...@google.com>
>>>> wrote:
>>>>
>>>>> Hey everyone,
>>>>>
>>>>> I ran into a bug that caused an issue with the new self-checkpointing
>>>>> feature in Go this morning. Rather than cherrypick the fix for an
>>>>> experimental feature while we're still testing it, I've filed
>>>>> BEAM-14424 <https://issues.apache.org/jira/browse/BEAM-14424> and put
>>>>> together a PR for the release branch (
>>>>> https://github.com/apache/beam/pull/17562)  to revert the feature
>>>>> being enabled and called-out in CHANGES.md as being available on an
>>>>> experimental basis. While we did call the feature out as experimental, the
>>>>> issue prevents self-checkpointing from being used as expected and we should
>>>>> avoid having users try it.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jack McCluskey
>>>>>
>>>>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz> wrote:
>>>>>
>>>>>> BEAM-14196 is just merged. I changed the priority to P1 (the original
>>>>>> JIRA was about adding test, but the fix for FlinkRunner was simple enough,
>>>>>> so it was added to the PR). The test reveals a correctness bug so I'd
>>>>>> prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>>>>
>>>>>>  Jan
>>>>>>
>>>>>> [1] https://github.com/apache/beam/pull/17504
>>>>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com> wrote:
>>>>>>
>>>>>>> Update:
>>>>>>> - release-2.39.0 branch has been cut.
>>>>>>> - 5 remaining blocking issues in link
>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>> .
>>>>>>>
>>>>>>
>>>>>> 2 of these issues are P2s. Are they release blockers?
>>>>>>
>>>>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>>>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:
>>>>>>>
>>>>>>>> Thank you very much Yichi. Please let us know if you need any help.
>>>>>>>>
>>>>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi, Beam dev community,
>>>>>>>>>
>>>>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress will
>>>>>>>>> be updated here.
>>>>>>>>>
>>>>>>>>> Friendly reminder that the 2.39.0 release branch will be cut in 2
>>>>>>>>> days on 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>>>>>>>>> necessary. Current blocking issues can be seen at link
>>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>>> .
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Yichi
>>>>>>>>>
>>>>>>>>>
>>>>>>>>

Re: [Release] 2.39.0 release update

Posted by Ahmet Altay <al...@google.com>.
Thank you Yichi.

On Mon, May 9, 2022 at 6:38 PM Yichi Zhang <zy...@google.com> wrote:

> There's two blocking issue/FR:
> https://issues.apache.org/jira/browse/BEAM-14429
>

Added a few folks to the dev list thread who might help. But if it is still
unblocked, I would suggest not making it a release blocker because it is
already an existing issue.

/cc @Chamikara Jayalath <ch...@google.com> - this is IO related.


>
> https://issues.apache.org/jira/browse/BEAM-14412
>

@Kenneth Knowles <kl...@google.com> @Ryan Thompson <ry...@google.com> -
please let us know what your timeline is for completing the open PR (
https://github.com/apache/beam/pull/17244).


>
>
> I believe there's one outstanding PR under review for BEAM-14412
> <https://issues.apache.org/jira/browse/BEAM-14412>:
> https://github.com/apache/beam/pull/17244.
>
> For https://issues.apache.org/jira/browse/BEAM-14429, it appears to be an
> issue that existed for a long time(exists in previous versions).
> I think it is an issue significant enough to influence the correctness of
> UnboundedSourceUnboundedSourceAsSDFWrapperFn.
> I'm unfamiliar with this piece of code and I'm still trying to figure out
> the right fix. There's another thread I created in the dev mailing list
> regarding the issue.
> I opened https://github.com/apache/beam/pull/17596 as a temp improvement
> but this shouldn't be the right solution.
>
>
>
> On Mon, May 9, 2022 at 4:56 PM Ahmet Altay <al...@google.com> wrote:
>
>> Yichi, what is the current state of the release? Is it still blocked, do
>> you need help?
>>
>> On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com> wrote:
>>
>>> > The test reveals a correctness bug so I'd prefer to cherry pick the PR
>>> [1] into 2.39.0, if possible.
>>> > [1] https://github.com/apache/beam/pull/17504
>>>
>>> Created cherrypick https://github.com/apache/beam/pull/17561
>>>
>>> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <jr...@google.com>
>>> wrote:
>>>
>>>> Hey everyone,
>>>>
>>>> I ran into a bug that caused an issue with the new self-checkpointing
>>>> feature in Go this morning. Rather than cherrypick the fix for an
>>>> experimental feature while we're still testing it, I've filed
>>>> BEAM-14424 <https://issues.apache.org/jira/browse/BEAM-14424> and put
>>>> together a PR for the release branch (
>>>> https://github.com/apache/beam/pull/17562)  to revert the feature
>>>> being enabled and called-out in CHANGES.md as being available on an
>>>> experimental basis. While we did call the feature out as experimental, the
>>>> issue prevents self-checkpointing from being used as expected and we should
>>>> avoid having users try it.
>>>>
>>>> Thanks,
>>>>
>>>> Jack McCluskey
>>>>
>>>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz> wrote:
>>>>
>>>>> BEAM-14196 is just merged. I changed the priority to P1 (the original
>>>>> JIRA was about adding test, but the fix for FlinkRunner was simple enough,
>>>>> so it was added to the PR). The test reveals a correctness bug so I'd
>>>>> prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>>>
>>>>>  Jan
>>>>>
>>>>> [1] https://github.com/apache/beam/pull/17504
>>>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com> wrote:
>>>>>
>>>>>> Update:
>>>>>> - release-2.39.0 branch has been cut.
>>>>>> - 5 remaining blocking issues in link
>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>> .
>>>>>>
>>>>>
>>>>> 2 of these issues are P2s. Are they release blockers?
>>>>>
>>>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>>>
>>>>>
>>>>>>
>>>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:
>>>>>>
>>>>>>> Thank you very much Yichi. Please let us know if you need any help.
>>>>>>>
>>>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi, Beam dev community,
>>>>>>>>
>>>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress will
>>>>>>>> be updated here.
>>>>>>>>
>>>>>>>> Friendly reminder that the 2.39.0 release branch will be cut in 2
>>>>>>>> days on 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>>>>>>>> necessary. Current blocking issues can be seen at link
>>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>>> .
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Yichi
>>>>>>>>
>>>>>>>>
>>>>>>>

Re: [Release] 2.39.0 release update

Posted by Yichi Zhang <zy...@google.com>.
There's two blocking issue/FR:
https://issues.apache.org/jira/browse/BEAM-14429
https://issues.apache.org/jira/browse/BEAM-14412

I believe there's one outstanding PR under review for BEAM-14412
<https://issues.apache.org/jira/browse/BEAM-14412>:
https://github.com/apache/beam/pull/17244.

For https://issues.apache.org/jira/browse/BEAM-14429, it appears to be an
issue that existed for a long time(exists in previous versions).
I think it is an issue significant enough to influence the correctness of
UnboundedSourceUnboundedSourceAsSDFWrapperFn.
I'm unfamiliar with this piece of code and I'm still trying to figure out
the right fix. There's another thread I created in the dev mailing list
regarding the issue.
I opened https://github.com/apache/beam/pull/17596 as a temp improvement
but this shouldn't be the right solution.



On Mon, May 9, 2022 at 4:56 PM Ahmet Altay <al...@google.com> wrote:

> Yichi, what is the current state of the release? Is it still blocked, do
> you need help?
>
> On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com> wrote:
>
>> > The test reveals a correctness bug so I'd prefer to cherry pick the PR
>> [1] into 2.39.0, if possible.
>> > [1] https://github.com/apache/beam/pull/17504
>>
>> Created cherrypick https://github.com/apache/beam/pull/17561
>>
>> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <jr...@google.com>
>> wrote:
>>
>>> Hey everyone,
>>>
>>> I ran into a bug that caused an issue with the new self-checkpointing
>>> feature in Go this morning. Rather than cherrypick the fix for an
>>> experimental feature while we're still testing it, I've filed BEAM-14424
>>> <https://issues.apache.org/jira/browse/BEAM-14424> and put together a
>>> PR for the release branch (https://github.com/apache/beam/pull/17562)
>>> to revert the feature being enabled and called-out in CHANGES.md as being
>>> available on an experimental basis. While we did call the feature out as
>>> experimental, the issue prevents self-checkpointing from being used as
>>> expected and we should avoid having users try it.
>>>
>>> Thanks,
>>>
>>> Jack McCluskey
>>>
>>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz> wrote:
>>>
>>>> BEAM-14196 is just merged. I changed the priority to P1 (the original
>>>> JIRA was about adding test, but the fix for FlinkRunner was simple enough,
>>>> so it was added to the PR). The test reveals a correctness bug so I'd
>>>> prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>>
>>>>  Jan
>>>>
>>>> [1] https://github.com/apache/beam/pull/17504
>>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>>
>>>>
>>>>
>>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com> wrote:
>>>>
>>>>> Update:
>>>>> - release-2.39.0 branch has been cut.
>>>>> - 5 remaining blocking issues in link
>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>> .
>>>>>
>>>>
>>>> 2 of these issues are P2s. Are they release blockers?
>>>>
>>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>>
>>>>
>>>>>
>>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> Thank you very much Yichi. Please let us know if you need any help.
>>>>>>
>>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi, Beam dev community,
>>>>>>>
>>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress will
>>>>>>> be updated here.
>>>>>>>
>>>>>>> Friendly reminder that the 2.39.0 release branch will be cut in 2
>>>>>>> days on 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>>>>>>> necessary. Current blocking issues can be seen at link
>>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>>> .
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Yichi
>>>>>>>
>>>>>>>
>>>>>>

Re: [Release] 2.39.0 release update

Posted by Ahmet Altay <al...@google.com>.
Yichi, what is the current state of the release? Is it still blocked, do
you need help?

On Thu, May 5, 2022 at 12:16 PM Yichi Zhang <zy...@google.com> wrote:

> > The test reveals a correctness bug so I'd prefer to cherry pick the PR
> [1] into 2.39.0, if possible.
> > [1] https://github.com/apache/beam/pull/17504
>
> Created cherrypick https://github.com/apache/beam/pull/17561
>
> On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <jr...@google.com>
> wrote:
>
>> Hey everyone,
>>
>> I ran into a bug that caused an issue with the new self-checkpointing
>> feature in Go this morning. Rather than cherrypick the fix for an
>> experimental feature while we're still testing it, I've filed BEAM-14424
>> <https://issues.apache.org/jira/browse/BEAM-14424> and put together a PR
>> for the release branch (https://github.com/apache/beam/pull/17562)  to
>> revert the feature being enabled and called-out in CHANGES.md as being
>> available on an experimental basis. While we did call the feature out as
>> experimental, the issue prevents self-checkpointing from being used as
>> expected and we should avoid having users try it.
>>
>> Thanks,
>>
>> Jack McCluskey
>>
>> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz> wrote:
>>
>>> BEAM-14196 is just merged. I changed the priority to P1 (the original
>>> JIRA was about adding test, but the fix for FlinkRunner was simple enough,
>>> so it was added to the PR). The test reveals a correctness bug so I'd
>>> prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>>
>>>  Jan
>>>
>>> [1] https://github.com/apache/beam/pull/17504
>>> On 5/5/22 02:54, Ahmet Altay wrote:
>>>
>>>
>>>
>>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com> wrote:
>>>
>>>> Update:
>>>> - release-2.39.0 branch has been cut.
>>>> - 5 remaining blocking issues in link
>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>> .
>>>>
>>>
>>> 2 of these issues are P2s. Are they release blockers?
>>>
>>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>>
>>>
>>>>
>>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Thank you very much Yichi. Please let us know if you need any help.
>>>>>
>>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com> wrote:
>>>>>
>>>>>> Hi, Beam dev community,
>>>>>>
>>>>>> Opening this thread for Beam 2.39.0 release updates. Progress will be
>>>>>> updated here.
>>>>>>
>>>>>> Friendly reminder that the 2.39.0 release branch will be cut in 2
>>>>>> days on 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>>>>>> necessary. Current blocking issues can be seen at link
>>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>>> .
>>>>>>
>>>>>> Thanks,
>>>>>> Yichi
>>>>>>
>>>>>>
>>>>>

Re: [Release] 2.39.0 release update

Posted by Yichi Zhang <zy...@google.com>.
> The test reveals a correctness bug so I'd prefer to cherry pick the PR
[1] into 2.39.0, if possible.
> [1] https://github.com/apache/beam/pull/17504

Created cherrypick https://github.com/apache/beam/pull/17561

On Thu, May 5, 2022 at 11:11 AM Jack McCluskey <jr...@google.com>
wrote:

> Hey everyone,
>
> I ran into a bug that caused an issue with the new self-checkpointing
> feature in Go this morning. Rather than cherrypick the fix for an
> experimental feature while we're still testing it, I've filed BEAM-14424
> <https://issues.apache.org/jira/browse/BEAM-14424> and put together a PR
> for the release branch (https://github.com/apache/beam/pull/17562)  to
> revert the feature being enabled and called-out in CHANGES.md as being
> available on an experimental basis. While we did call the feature out as
> experimental, the issue prevents self-checkpointing from being used as
> expected and we should avoid having users try it.
>
> Thanks,
>
> Jack McCluskey
>
> On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz> wrote:
>
>> BEAM-14196 is just merged. I changed the priority to P1 (the original
>> JIRA was about adding test, but the fix for FlinkRunner was simple enough,
>> so it was added to the PR). The test reveals a correctness bug so I'd
>> prefer to cherry pick the PR [1] into 2.39.0, if possible.
>>
>>  Jan
>>
>> [1] https://github.com/apache/beam/pull/17504
>> On 5/5/22 02:54, Ahmet Altay wrote:
>>
>>
>>
>> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com> wrote:
>>
>>> Update:
>>> - release-2.39.0 branch has been cut.
>>> - 5 remaining blocking issues in link
>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>> .
>>>
>>
>> 2 of these issues are P2s. Are they release blockers?
>>
>> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
>> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>>
>>
>>>
>>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Thank you very much Yichi. Please let us know if you need any help.
>>>>
>>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com> wrote:
>>>>
>>>>> Hi, Beam dev community,
>>>>>
>>>>> Opening this thread for Beam 2.39.0 release updates. Progress will be
>>>>> updated here.
>>>>>
>>>>> Friendly reminder that the 2.39.0 release branch will be cut in 2 days
>>>>> on 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>>>>> necessary. Current blocking issues can be seen at link
>>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>>> .
>>>>>
>>>>> Thanks,
>>>>> Yichi
>>>>>
>>>>>
>>>>

Re: [Release] 2.39.0 release update

Posted by Jack McCluskey <jr...@google.com>.
Hey everyone,

I ran into a bug that caused an issue with the new self-checkpointing
feature in Go this morning. Rather than cherrypick the fix for an
experimental feature while we're still testing it, I've filed BEAM-14424
<https://issues.apache.org/jira/browse/BEAM-14424> and put together a PR
for the release branch (https://github.com/apache/beam/pull/17562)  to
revert the feature being enabled and called-out in CHANGES.md as being
available on an experimental basis. While we did call the feature out as
experimental, the issue prevents self-checkpointing from being used as
expected and we should avoid having users try it.

Thanks,

Jack McCluskey

On Thu, May 5, 2022 at 4:09 AM Jan Lukavský <je...@seznam.cz> wrote:

> BEAM-14196 is just merged. I changed the priority to P1 (the original JIRA
> was about adding test, but the fix for FlinkRunner was simple enough, so it
> was added to the PR). The test reveals a correctness bug so I'd prefer to
> cherry pick the PR [1] into 2.39.0, if possible.
>
>  Jan
>
> [1] https://github.com/apache/beam/pull/17504
> On 5/5/22 02:54, Ahmet Altay wrote:
>
>
>
> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com> wrote:
>
>> Update:
>> - release-2.39.0 branch has been cut.
>> - 5 remaining blocking issues in link
>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>> .
>>
>
> 2 of these issues are P2s. Are they release blockers?
>
> BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
> BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>
>
>
>>
>> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:
>>
>>> Thank you very much Yichi. Please let us know if you need any help.
>>>
>>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com> wrote:
>>>
>>>> Hi, Beam dev community,
>>>>
>>>> Opening this thread for Beam 2.39.0 release updates. Progress will be
>>>> updated here.
>>>>
>>>> Friendly reminder that the 2.39.0 release branch will be cut in 2 days
>>>> on 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>>>> necessary. Current blocking issues can be seen at link
>>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>>> .
>>>>
>>>> Thanks,
>>>> Yichi
>>>>
>>>>
>>>

Re: [Release] 2.39.0 release update

Posted by Jan Lukavský <je...@seznam.cz>.
BEAM-14196 is just merged. I changed the priority to P1 (the original 
JIRA was about adding test, but the fix for FlinkRunner was simple 
enough, so it was added to the PR). The test reveals a correctness bug 
so I'd prefer to cherry pick the PR [1] into 2.39.0, if possible.

  Jan

[1] https://github.com/apache/beam/pull/17504

On 5/5/22 02:54, Ahmet Altay wrote:
>
>
> On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com> wrote:
>
>     Update:
>     - release-2.39.0 branch has been cut.
>     - 5 remaining blocking issues in link
>     <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>.
>
>
> 2 of these issues are P2s. Are they release blockers?
>
> BEAM-14416 - assigned to @Yichi Zhang <ma...@google.com>
> BEAM-14196 - assigned to @Jan Lukavský <ma...@seznam.cz>
>
>
>     On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:
>
>         Thank you very much Yichi. Please let us know if you need any
>         help.
>
>         On Mon, May 2, 2022 at 11:45 AM Yichi Zhang
>         <zy...@google.com> wrote:
>
>             Hi, Beam dev community,
>
>             Opening this thread for Beam 2.39.0 release updates.
>             Progress will be updated here.
>
>             Friendly reminder that the 2.39.0 release branch will be
>             cut in 2 days on 05/04/2022. Please mark blocking issues
>             with fix version 2.39.0 if necessary. Current blocking
>             issues can be seen at link
>             <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>.
>
>             Thanks,
>             Yichi
>

Re: [Release] 2.39.0 release update

Posted by Ahmet Altay <al...@google.com>.
On Wed, May 4, 2022 at 6:04 PM Yichi Zhang <zy...@google.com> wrote:

> Update:
> - release-2.39.0 branch has been cut.
> - 5 remaining blocking issues in link
> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
> .
>

2 of these issues are P2s. Are they release blockers?

BEAM-14416 - assigned to @Yichi Zhang <zy...@google.com>
BEAM-14196 - assigned to @Jan Lukavský <je...@seznam.cz>


>
> On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:
>
>> Thank you very much Yichi. Please let us know if you need any help.
>>
>> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com> wrote:
>>
>>> Hi, Beam dev community,
>>>
>>> Opening this thread for Beam 2.39.0 release updates. Progress will be
>>> updated here.
>>>
>>> Friendly reminder that the 2.39.0 release branch will be cut in 2 days
>>> on 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>>> necessary. Current blocking issues can be seen at link
>>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>>> .
>>>
>>> Thanks,
>>> Yichi
>>>
>>>
>>

Re: [Release] 2.39.0 release update

Posted by Yichi Zhang <zy...@google.com>.
Update:
- release-2.39.0 branch has been cut.
- 5 remaining blocking issues in link
<https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
.

On Wed, May 4, 2022 at 9:41 AM Ahmet Altay <al...@google.com> wrote:

> Thank you very much Yichi. Please let us know if you need any help.
>
> On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com> wrote:
>
>> Hi, Beam dev community,
>>
>> Opening this thread for Beam 2.39.0 release updates. Progress will be
>> updated here.
>>
>> Friendly reminder that the 2.39.0 release branch will be cut in 2 days on
>> 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
>> necessary. Current blocking issues can be seen at link
>> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
>> .
>>
>> Thanks,
>> Yichi
>>
>>
>

Re: [Release] 2.39.0 release update

Posted by Ahmet Altay <al...@google.com>.
Thank you very much Yichi. Please let us know if you need any help.

On Mon, May 2, 2022 at 11:45 AM Yichi Zhang <zy...@google.com> wrote:

> Hi, Beam dev community,
>
> Opening this thread for Beam 2.39.0 release updates. Progress will be
> updated here.
>
> Friendly reminder that the 2.39.0 release branch will be cut in 2 days on
> 05/04/2022. Please mark blocking issues with fix version 2.39.0 if
> necessary. Current blocking issues can be seen at link
> <https://issues.apache.org/jira/browse/BEAM-14146?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.39.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC>
> .
>
> Thanks,
> Yichi
>
>