You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Brian Hulette <bh...@google.com> on 2022/02/10 01:53:22 UTC
Re: [PROPOSAL] Preparing for 2.37.0 Release
The 2.37.0 release branch has been cut [1]!
There are a few open release blockers [2] - I'll be working with the owners
to get them resolved over the next few days. It would be a great help if
everyone could review that list and close any issues that have been
resolved, or bump the fix version for anything that doesn't meet the
criteria at [3].
Also, if you have any significant changes to announce, please send me a PR
which adds them to CHANGES.md [4].
Thanks,
Brian
[1] https://github.com/apache/beam/tree/release-2.37.0
[2]
https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
[3] https://beam.apache.org/contribute/release-blocking/
[4] https://github.com/apache/beam/blob/master/CHANGES.md
On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org> wrote:
> +1 and don't hesitate to ask for help
>
> Kenn
>
> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com> wrote:
>
>> +1 and thank you Brian!
>>
>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>> according to
>>> the release calendar [1].
>>>
>>> I would like to volunteer myself to do this release. My plan is to cut
>>> the branch on that date, and cherrypick release-blocking fixes afterwards
>>> if any.
>>>
>>> Please help the release go smoothly by:
>>> - Making sure that any unresolved release blocking JIRA issues for
>>> 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>> possible.
>>> - Reviewing the current release blockers [2] and remove the "Fix
>>> Version/s" if they don't meet the criteria at [3].
>>>
>>> Let me know if you have any comments/objections/questions.
>>>
>>> Thanks,
>>> Brian
>>>
>>> [1]
>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>> [2]
>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>
>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Brian Hulette <bh...@google.com>.
Upon closer inspection this is
https://issues.apache.org/jira/browse/BEAM-13921
On Wed, Feb 16, 2022 at 8:54 AM Brian Hulette <bh...@google.com> wrote:
> All the fixes for the release blockers I referenced yesterday have been
> merged, but I found a new hard failure in
> validatesCrossLanguageRunnerGoUsingJava in the XVR Spark (2 and 3) suites
> [1]. It looks like the tasks were failing at HEAD when I cut the branch
> [2].
>
> The issue was resolved shortly after the cut [3] - but it's not clear to
> me which commit fixed it. If anyone has any insight here it would be
> greatly appreciated. I've been unable to run this suite locally to identify
> the fix commit, so in the absence of other information I'll just look for
> the fix by opening cherrypicks and testing them.
>
> [1] https://issues.apache.org/jira/browse/BEAM-13958
> [2] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1277/
> [3] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1279/
>
> On Tue, Feb 15, 2022 at 11:26 AM Ahmet Altay <al...@google.com> wrote:
>
>> Thank you Brian!
>>
>> On Tue, Feb 15, 2022 at 11:24 AM Brian Hulette <bh...@google.com>
>> wrote:
>>
>>> [1] is accurate right now. There are three open release blockers, but
>>> all have fixes in the process of merging to master and/or release-2.37.0.
>>> Thanks everyone for your quick responses!
>>>
>>> I should be able to get these merged and finish validating the branch
>>> today and move on to making an RC, assuming ci-beam cooperates [2] and
>>> nothing else comes up.
>>>
>>> [1]
>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>> [2] https://issues.apache.org/jira/browse/INFRA-22878
>>>
>>> On Tue, Feb 15, 2022 at 11:03 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Brian, what are the remaining blockers on the release? Are you blocked?
>>>>
>>>> On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com>
>>>> wrote:
>>>>
>>>>> PVR Spark 2 Streaming should not be a release blocker, since this test
>>>>> suite was never consistently green to begin with.
>>>>>
>>>>>
>>>>> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com>
>>>>> wrote:
>>>>>
>>>>>> I ran some PostCommits and VR suites on the release branch today [1]
>>>>>> and found that several are failing. Some are just related to missing
>>>>>> Dataflow containers, but many are real failures.
>>>>>>
>>>>>> I'm going through these failures and making sure we have release
>>>>>> blocking jiras [2] filed for them. I'll try to ping relevant people on the
>>>>>> jiras themselves, but I may raise some issues here if it's not making
>>>>>> progress or I'm not sure who owns it.
>>>>>>
>>>>>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little
>>>>>> unclear on. Can someone help out with these tests? Or maybe should we
>>>>>> consider just skipping them for 2.37.0?
>>>>>>
>>>>>> [1] https://github.com/apache/beam/pull/16849
>>>>>> [2]
>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>> 0
>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>>>>>
>>>>>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> The 2.37.0 release branch has been cut [1]!
>>>>>>>
>>>>>>> There are a few open release blockers [2] - I'll be working with the
>>>>>>> owners to get them resolved over the next few days. It would be a great
>>>>>>> help if everyone could review that list and close any issues that have been
>>>>>>> resolved, or bump the fix version for anything that doesn't meet the
>>>>>>> criteria at [3].
>>>>>>>
>>>>>>> Also, if you have any significant changes to announce, please send
>>>>>>> me a PR which adds them to CHANGES.md [4].
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Brian
>>>>>>>
>>>>>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>>>>>> [2]
>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>>> 0
>>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>>>>>
>>>>>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 and don't hesitate to ask for help
>>>>>>>>
>>>>>>>> Kenn
>>>>>>>>
>>>>>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 and thank you Brian!
>>>>>>>>>
>>>>>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>>>>>>>>> according to
>>>>>>>>>> the release calendar [1].
>>>>>>>>>>
>>>>>>>>>> I would like to volunteer myself to do this release. My plan is
>>>>>>>>>> to cut the branch on that date, and cherrypick release-blocking fixes
>>>>>>>>>> afterwards if any.
>>>>>>>>>>
>>>>>>>>>> Please help the release go smoothly by:
>>>>>>>>>> - Making sure that any unresolved release blocking JIRA issues
>>>>>>>>>> for 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>>>>>> possible.
>>>>>>>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>>>>>>>> Version/s" if they don't meet the criteria at [3].
>>>>>>>>>>
>>>>>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Brian
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>> [2]
>>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>>>
>>>>>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Brian Hulette <bh...@google.com>.
Oops, sorry for the double message. It turns out INFRA-22894 was resolved
while I wrote that, so I should have an RC out soon.
On Thu, Feb 17, 2022 at 9:19 AM Brian Hulette <bh...@google.com> wrote:
> No open release blockers! However I'm blocked building RC1 until INFRA
> adds a repo for the python 3.9 SDK container [1]. Everything else is ready
> - in theory we could start validating everything but Python 3.9 until that
> happens. Is that something we should consider?
>
> [1] https://issues.apache.org/jira/browse/INFRA-22894
>
> On Wed, Feb 16, 2022 at 6:43 PM Ahmet Altay <al...@google.com> wrote:
>
>> Thank you Brian, and thank you Rebo!
>>
>> I saw that the fix for the last issue was also cherry picked to the
>> release branch. Are there any other blockers left?
>>
>> On Wed, Feb 16, 2022 at 9:28 AM Robert Burke <ro...@frantil.com> wrote:
>>
>>> It should be PR 16815 which disables the test. It seems though the
>>> debezium transform from java is doing something that Spark doesn't know how
>>> to handle.
>>>
>>> On Wed, Feb 16, 2022, 8:55 AM Brian Hulette <bh...@google.com> wrote:
>>>
>>>> All the fixes for the release blockers I referenced yesterday have been
>>>> merged, but I found a new hard failure in
>>>> validatesCrossLanguageRunnerGoUsingJava in the XVR Spark (2 and 3) suites
>>>> [1]. It looks like the tasks were failing at HEAD when I cut the branch
>>>> [2].
>>>>
>>>> The issue was resolved shortly after the cut [3] - but it's not clear
>>>> to me which commit fixed it. If anyone has any insight here it would be
>>>> greatly appreciated. I've been unable to run this suite locally to identify
>>>> the fix commit, so in the absence of other information I'll just look for
>>>> the fix by opening cherrypicks and testing them.
>>>>
>>>> [1] https://issues.apache.org/jira/browse/BEAM-13958
>>>> [2] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1277/
>>>> [3] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1279/
>>>>
>>>> On Tue, Feb 15, 2022 at 11:26 AM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Thank you Brian!
>>>>>
>>>>> On Tue, Feb 15, 2022 at 11:24 AM Brian Hulette <bh...@google.com>
>>>>> wrote:
>>>>>
>>>>>> [1] is accurate right now. There are three open release blockers, but
>>>>>> all have fixes in the process of merging to master and/or release-2.37.0.
>>>>>> Thanks everyone for your quick responses!
>>>>>>
>>>>>> I should be able to get these merged and finish validating the branch
>>>>>> today and move on to making an RC, assuming ci-beam cooperates [2] and
>>>>>> nothing else comes up.
>>>>>>
>>>>>> [1]
>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>> [2] https://issues.apache.org/jira/browse/INFRA-22878
>>>>>>
>>>>>> On Tue, Feb 15, 2022 at 11:03 AM Ahmet Altay <al...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Brian, what are the remaining blockers on the release? Are you
>>>>>>> blocked?
>>>>>>>
>>>>>>> On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> PVR Spark 2 Streaming should not be a release blocker, since this
>>>>>>>> test suite was never consistently green to begin with.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I ran some PostCommits and VR suites on the release branch today
>>>>>>>>> [1] and found that several are failing. Some are just related to missing
>>>>>>>>> Dataflow containers, but many are real failures.
>>>>>>>>>
>>>>>>>>> I'm going through these failures and making sure we have release
>>>>>>>>> blocking jiras [2] filed for them. I'll try to ping relevant people on the
>>>>>>>>> jiras themselves, but I may raise some issues here if it's not making
>>>>>>>>> progress or I'm not sure who owns it.
>>>>>>>>>
>>>>>>>>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little
>>>>>>>>> unclear on. Can someone help out with these tests? Or maybe should we
>>>>>>>>> consider just skipping them for 2.37.0?
>>>>>>>>>
>>>>>>>>> [1] https://github.com/apache/beam/pull/16849
>>>>>>>>> [2]
>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>>>>> 0
>>>>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>>>>>>>>
>>>>>>>>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> The 2.37.0 release branch has been cut [1]!
>>>>>>>>>>
>>>>>>>>>> There are a few open release blockers [2] - I'll be working with
>>>>>>>>>> the owners to get them resolved over the next few days. It would be a great
>>>>>>>>>> help if everyone could review that list and close any issues that have been
>>>>>>>>>> resolved, or bump the fix version for anything that doesn't meet the
>>>>>>>>>> criteria at [3].
>>>>>>>>>>
>>>>>>>>>> Also, if you have any significant changes to announce, please
>>>>>>>>>> send me a PR which adds them to CHANGES.md [4].
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Brian
>>>>>>>>>>
>>>>>>>>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>>>>>>>>> [2]
>>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>>>>>> 0
>>>>>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>>>>>>>>
>>>>>>>>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1 and don't hesitate to ask for help
>>>>>>>>>>>
>>>>>>>>>>> Kenn
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1 and thank you Brian!
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <
>>>>>>>>>>>> bhulette@google.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>
>>>>>>>>>>>>> The next (2.37.0) release branch cut is scheduled for 9
>>>>>>>>>>>>> February, according to
>>>>>>>>>>>>> the release calendar [1].
>>>>>>>>>>>>>
>>>>>>>>>>>>> I would like to volunteer myself to do this release. My plan
>>>>>>>>>>>>> is to cut the branch on that date, and cherrypick release-blocking fixes
>>>>>>>>>>>>> afterwards if any.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please help the release go smoothly by:
>>>>>>>>>>>>> - Making sure that any unresolved release blocking JIRA issues
>>>>>>>>>>>>> for 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>>>>>>>>> possible.
>>>>>>>>>>>>> - Reviewing the current release blockers [2] and remove the
>>>>>>>>>>>>> "Fix Version/s" if they don't meet the criteria at [3].
>>>>>>>>>>>>>
>>>>>>>>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Brian
>>>>>>>>>>>>>
>>>>>>>>>>>>> [1]
>>>>>>>>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>>> [2]
>>>>>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>>>>>>
>>>>>>>>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Brian Hulette <bh...@google.com>.
No open release blockers! However I'm blocked building RC1 until INFRA adds
a repo for the python 3.9 SDK container [1]. Everything else is ready - in
theory we could start validating everything but Python 3.9 until that
happens. Is that something we should consider?
[1] https://issues.apache.org/jira/browse/INFRA-22894
On Wed, Feb 16, 2022 at 6:43 PM Ahmet Altay <al...@google.com> wrote:
> Thank you Brian, and thank you Rebo!
>
> I saw that the fix for the last issue was also cherry picked to the
> release branch. Are there any other blockers left?
>
> On Wed, Feb 16, 2022 at 9:28 AM Robert Burke <ro...@frantil.com> wrote:
>
>> It should be PR 16815 which disables the test. It seems though the
>> debezium transform from java is doing something that Spark doesn't know how
>> to handle.
>>
>> On Wed, Feb 16, 2022, 8:55 AM Brian Hulette <bh...@google.com> wrote:
>>
>>> All the fixes for the release blockers I referenced yesterday have been
>>> merged, but I found a new hard failure in
>>> validatesCrossLanguageRunnerGoUsingJava in the XVR Spark (2 and 3) suites
>>> [1]. It looks like the tasks were failing at HEAD when I cut the branch
>>> [2].
>>>
>>> The issue was resolved shortly after the cut [3] - but it's not clear to
>>> me which commit fixed it. If anyone has any insight here it would be
>>> greatly appreciated. I've been unable to run this suite locally to identify
>>> the fix commit, so in the absence of other information I'll just look for
>>> the fix by opening cherrypicks and testing them.
>>>
>>> [1] https://issues.apache.org/jira/browse/BEAM-13958
>>> [2] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1277/
>>> [3] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1279/
>>>
>>> On Tue, Feb 15, 2022 at 11:26 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Thank you Brian!
>>>>
>>>> On Tue, Feb 15, 2022 at 11:24 AM Brian Hulette <bh...@google.com>
>>>> wrote:
>>>>
>>>>> [1] is accurate right now. There are three open release blockers, but
>>>>> all have fixes in the process of merging to master and/or release-2.37.0.
>>>>> Thanks everyone for your quick responses!
>>>>>
>>>>> I should be able to get these merged and finish validating the branch
>>>>> today and move on to making an RC, assuming ci-beam cooperates [2] and
>>>>> nothing else comes up.
>>>>>
>>>>> [1]
>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>> [2] https://issues.apache.org/jira/browse/INFRA-22878
>>>>>
>>>>> On Tue, Feb 15, 2022 at 11:03 AM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> Brian, what are the remaining blockers on the release? Are you
>>>>>> blocked?
>>>>>>
>>>>>> On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> PVR Spark 2 Streaming should not be a release blocker, since this
>>>>>>> test suite was never consistently green to begin with.
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I ran some PostCommits and VR suites on the release branch today
>>>>>>>> [1] and found that several are failing. Some are just related to missing
>>>>>>>> Dataflow containers, but many are real failures.
>>>>>>>>
>>>>>>>> I'm going through these failures and making sure we have release
>>>>>>>> blocking jiras [2] filed for them. I'll try to ping relevant people on the
>>>>>>>> jiras themselves, but I may raise some issues here if it's not making
>>>>>>>> progress or I'm not sure who owns it.
>>>>>>>>
>>>>>>>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little
>>>>>>>> unclear on. Can someone help out with these tests? Or maybe should we
>>>>>>>> consider just skipping them for 2.37.0?
>>>>>>>>
>>>>>>>> [1] https://github.com/apache/beam/pull/16849
>>>>>>>> [2]
>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>>>> 0
>>>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>>>>>>>
>>>>>>>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> The 2.37.0 release branch has been cut [1]!
>>>>>>>>>
>>>>>>>>> There are a few open release blockers [2] - I'll be working with
>>>>>>>>> the owners to get them resolved over the next few days. It would be a great
>>>>>>>>> help if everyone could review that list and close any issues that have been
>>>>>>>>> resolved, or bump the fix version for anything that doesn't meet the
>>>>>>>>> criteria at [3].
>>>>>>>>>
>>>>>>>>> Also, if you have any significant changes to announce, please send
>>>>>>>>> me a PR which adds them to CHANGES.md [4].
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Brian
>>>>>>>>>
>>>>>>>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>>>>>>>> [2]
>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>>>>> 0
>>>>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>>>>>>>
>>>>>>>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 and don't hesitate to ask for help
>>>>>>>>>>
>>>>>>>>>> Kenn
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1 and thank you Brian!
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <
>>>>>>>>>>> bhulette@google.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>
>>>>>>>>>>>> The next (2.37.0) release branch cut is scheduled for 9
>>>>>>>>>>>> February, according to
>>>>>>>>>>>> the release calendar [1].
>>>>>>>>>>>>
>>>>>>>>>>>> I would like to volunteer myself to do this release. My plan is
>>>>>>>>>>>> to cut the branch on that date, and cherrypick release-blocking fixes
>>>>>>>>>>>> afterwards if any.
>>>>>>>>>>>>
>>>>>>>>>>>> Please help the release go smoothly by:
>>>>>>>>>>>> - Making sure that any unresolved release blocking JIRA issues
>>>>>>>>>>>> for 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>>>>>>>> possible.
>>>>>>>>>>>> - Reviewing the current release blockers [2] and remove the
>>>>>>>>>>>> "Fix Version/s" if they don't meet the criteria at [3].
>>>>>>>>>>>>
>>>>>>>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Brian
>>>>>>>>>>>>
>>>>>>>>>>>> [1]
>>>>>>>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>> [2]
>>>>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>>>>>
>>>>>>>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Ahmet Altay <al...@google.com>.
Thank you Brian, and thank you Rebo!
I saw that the fix for the last issue was also cherry picked to the
release branch. Are there any other blockers left?
On Wed, Feb 16, 2022 at 9:28 AM Robert Burke <ro...@frantil.com> wrote:
> It should be PR 16815 which disables the test. It seems though the
> debezium transform from java is doing something that Spark doesn't know how
> to handle.
>
> On Wed, Feb 16, 2022, 8:55 AM Brian Hulette <bh...@google.com> wrote:
>
>> All the fixes for the release blockers I referenced yesterday have been
>> merged, but I found a new hard failure in
>> validatesCrossLanguageRunnerGoUsingJava in the XVR Spark (2 and 3) suites
>> [1]. It looks like the tasks were failing at HEAD when I cut the branch
>> [2].
>>
>> The issue was resolved shortly after the cut [3] - but it's not clear to
>> me which commit fixed it. If anyone has any insight here it would be
>> greatly appreciated. I've been unable to run this suite locally to identify
>> the fix commit, so in the absence of other information I'll just look for
>> the fix by opening cherrypicks and testing them.
>>
>> [1] https://issues.apache.org/jira/browse/BEAM-13958
>> [2] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1277/
>> [3] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1279/
>>
>> On Tue, Feb 15, 2022 at 11:26 AM Ahmet Altay <al...@google.com> wrote:
>>
>>> Thank you Brian!
>>>
>>> On Tue, Feb 15, 2022 at 11:24 AM Brian Hulette <bh...@google.com>
>>> wrote:
>>>
>>>> [1] is accurate right now. There are three open release blockers, but
>>>> all have fixes in the process of merging to master and/or release-2.37.0.
>>>> Thanks everyone for your quick responses!
>>>>
>>>> I should be able to get these merged and finish validating the branch
>>>> today and move on to making an RC, assuming ci-beam cooperates [2] and
>>>> nothing else comes up.
>>>>
>>>> [1]
>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>> [2] https://issues.apache.org/jira/browse/INFRA-22878
>>>>
>>>> On Tue, Feb 15, 2022 at 11:03 AM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Brian, what are the remaining blockers on the release? Are you blocked?
>>>>>
>>>>> On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com>
>>>>> wrote:
>>>>>
>>>>>> PVR Spark 2 Streaming should not be a release blocker, since this
>>>>>> test suite was never consistently green to begin with.
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I ran some PostCommits and VR suites on the release branch today [1]
>>>>>>> and found that several are failing. Some are just related to missing
>>>>>>> Dataflow containers, but many are real failures.
>>>>>>>
>>>>>>> I'm going through these failures and making sure we have release
>>>>>>> blocking jiras [2] filed for them. I'll try to ping relevant people on the
>>>>>>> jiras themselves, but I may raise some issues here if it's not making
>>>>>>> progress or I'm not sure who owns it.
>>>>>>>
>>>>>>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little
>>>>>>> unclear on. Can someone help out with these tests? Or maybe should we
>>>>>>> consider just skipping them for 2.37.0?
>>>>>>>
>>>>>>> [1] https://github.com/apache/beam/pull/16849
>>>>>>> [2]
>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>>> 0
>>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>>>>>>
>>>>>>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> The 2.37.0 release branch has been cut [1]!
>>>>>>>>
>>>>>>>> There are a few open release blockers [2] - I'll be working with
>>>>>>>> the owners to get them resolved over the next few days. It would be a great
>>>>>>>> help if everyone could review that list and close any issues that have been
>>>>>>>> resolved, or bump the fix version for anything that doesn't meet the
>>>>>>>> criteria at [3].
>>>>>>>>
>>>>>>>> Also, if you have any significant changes to announce, please send
>>>>>>>> me a PR which adds them to CHANGES.md [4].
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Brian
>>>>>>>>
>>>>>>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>>>>>>> [2]
>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>>>> 0
>>>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>>>>>>
>>>>>>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 and don't hesitate to ask for help
>>>>>>>>>
>>>>>>>>> Kenn
>>>>>>>>>
>>>>>>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 and thank you Brian!
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <
>>>>>>>>>> bhulette@google.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all,
>>>>>>>>>>>
>>>>>>>>>>> The next (2.37.0) release branch cut is scheduled for 9
>>>>>>>>>>> February, according to
>>>>>>>>>>> the release calendar [1].
>>>>>>>>>>>
>>>>>>>>>>> I would like to volunteer myself to do this release. My plan is
>>>>>>>>>>> to cut the branch on that date, and cherrypick release-blocking fixes
>>>>>>>>>>> afterwards if any.
>>>>>>>>>>>
>>>>>>>>>>> Please help the release go smoothly by:
>>>>>>>>>>> - Making sure that any unresolved release blocking JIRA issues
>>>>>>>>>>> for 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>>>>>>> possible.
>>>>>>>>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>>>>>>>>> Version/s" if they don't meet the criteria at [3].
>>>>>>>>>>>
>>>>>>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Brian
>>>>>>>>>>>
>>>>>>>>>>> [1]
>>>>>>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>> [2]
>>>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>>>>
>>>>>>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Robert Burke <ro...@frantil.com>.
It should be PR 16815 which disables the test. It seems though the debezium
transform from java is doing something that Spark doesn't know how to
handle.
On Wed, Feb 16, 2022, 8:55 AM Brian Hulette <bh...@google.com> wrote:
> All the fixes for the release blockers I referenced yesterday have been
> merged, but I found a new hard failure in
> validatesCrossLanguageRunnerGoUsingJava in the XVR Spark (2 and 3) suites
> [1]. It looks like the tasks were failing at HEAD when I cut the branch
> [2].
>
> The issue was resolved shortly after the cut [3] - but it's not clear to
> me which commit fixed it. If anyone has any insight here it would be
> greatly appreciated. I've been unable to run this suite locally to identify
> the fix commit, so in the absence of other information I'll just look for
> the fix by opening cherrypicks and testing them.
>
> [1] https://issues.apache.org/jira/browse/BEAM-13958
> [2] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1277/
> [3] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1279/
>
> On Tue, Feb 15, 2022 at 11:26 AM Ahmet Altay <al...@google.com> wrote:
>
>> Thank you Brian!
>>
>> On Tue, Feb 15, 2022 at 11:24 AM Brian Hulette <bh...@google.com>
>> wrote:
>>
>>> [1] is accurate right now. There are three open release blockers, but
>>> all have fixes in the process of merging to master and/or release-2.37.0.
>>> Thanks everyone for your quick responses!
>>>
>>> I should be able to get these merged and finish validating the branch
>>> today and move on to making an RC, assuming ci-beam cooperates [2] and
>>> nothing else comes up.
>>>
>>> [1]
>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>> [2] https://issues.apache.org/jira/browse/INFRA-22878
>>>
>>> On Tue, Feb 15, 2022 at 11:03 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Brian, what are the remaining blockers on the release? Are you blocked?
>>>>
>>>> On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com>
>>>> wrote:
>>>>
>>>>> PVR Spark 2 Streaming should not be a release blocker, since this test
>>>>> suite was never consistently green to begin with.
>>>>>
>>>>>
>>>>> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com>
>>>>> wrote:
>>>>>
>>>>>> I ran some PostCommits and VR suites on the release branch today [1]
>>>>>> and found that several are failing. Some are just related to missing
>>>>>> Dataflow containers, but many are real failures.
>>>>>>
>>>>>> I'm going through these failures and making sure we have release
>>>>>> blocking jiras [2] filed for them. I'll try to ping relevant people on the
>>>>>> jiras themselves, but I may raise some issues here if it's not making
>>>>>> progress or I'm not sure who owns it.
>>>>>>
>>>>>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little
>>>>>> unclear on. Can someone help out with these tests? Or maybe should we
>>>>>> consider just skipping them for 2.37.0?
>>>>>>
>>>>>> [1] https://github.com/apache/beam/pull/16849
>>>>>> [2]
>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>> 0
>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>>>>>
>>>>>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> The 2.37.0 release branch has been cut [1]!
>>>>>>>
>>>>>>> There are a few open release blockers [2] - I'll be working with the
>>>>>>> owners to get them resolved over the next few days. It would be a great
>>>>>>> help if everyone could review that list and close any issues that have been
>>>>>>> resolved, or bump the fix version for anything that doesn't meet the
>>>>>>> criteria at [3].
>>>>>>>
>>>>>>> Also, if you have any significant changes to announce, please send
>>>>>>> me a PR which adds them to CHANGES.md [4].
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Brian
>>>>>>>
>>>>>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>>>>>> [2]
>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>>> 0
>>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>>>>>
>>>>>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 and don't hesitate to ask for help
>>>>>>>>
>>>>>>>> Kenn
>>>>>>>>
>>>>>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 and thank you Brian!
>>>>>>>>>
>>>>>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>>>>>>>>> according to
>>>>>>>>>> the release calendar [1].
>>>>>>>>>>
>>>>>>>>>> I would like to volunteer myself to do this release. My plan is
>>>>>>>>>> to cut the branch on that date, and cherrypick release-blocking fixes
>>>>>>>>>> afterwards if any.
>>>>>>>>>>
>>>>>>>>>> Please help the release go smoothly by:
>>>>>>>>>> - Making sure that any unresolved release blocking JIRA issues
>>>>>>>>>> for 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>>>>>> possible.
>>>>>>>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>>>>>>>> Version/s" if they don't meet the criteria at [3].
>>>>>>>>>>
>>>>>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Brian
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>> [2]
>>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>>>
>>>>>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Brian Hulette <bh...@google.com>.
All the fixes for the release blockers I referenced yesterday have been
merged, but I found a new hard failure in
validatesCrossLanguageRunnerGoUsingJava in the XVR Spark (2 and 3) suites
[1]. It looks like the tasks were failing at HEAD when I cut the branch
[2].
The issue was resolved shortly after the cut [3] - but it's not clear to me
which commit fixed it. If anyone has any insight here it would be greatly
appreciated. I've been unable to run this suite locally to identify the fix
commit, so in the absence of other information I'll just look for the fix
by opening cherrypicks and testing them.
[1] https://issues.apache.org/jira/browse/BEAM-13958
[2] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1277/
[3] https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1279/
On Tue, Feb 15, 2022 at 11:26 AM Ahmet Altay <al...@google.com> wrote:
> Thank you Brian!
>
> On Tue, Feb 15, 2022 at 11:24 AM Brian Hulette <bh...@google.com>
> wrote:
>
>> [1] is accurate right now. There are three open release blockers, but all
>> have fixes in the process of merging to master and/or release-2.37.0.
>> Thanks everyone for your quick responses!
>>
>> I should be able to get these merged and finish validating the branch
>> today and move on to making an RC, assuming ci-beam cooperates [2] and
>> nothing else comes up.
>>
>> [1]
>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>> [2] https://issues.apache.org/jira/browse/INFRA-22878
>>
>> On Tue, Feb 15, 2022 at 11:03 AM Ahmet Altay <al...@google.com> wrote:
>>
>>> Brian, what are the remaining blockers on the release? Are you blocked?
>>>
>>> On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com>
>>> wrote:
>>>
>>>> PVR Spark 2 Streaming should not be a release blocker, since this test
>>>> suite was never consistently green to begin with.
>>>>
>>>>
>>>> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com>
>>>> wrote:
>>>>
>>>>> I ran some PostCommits and VR suites on the release branch today [1]
>>>>> and found that several are failing. Some are just related to missing
>>>>> Dataflow containers, but many are real failures.
>>>>>
>>>>> I'm going through these failures and making sure we have release
>>>>> blocking jiras [2] filed for them. I'll try to ping relevant people on the
>>>>> jiras themselves, but I may raise some issues here if it's not making
>>>>> progress or I'm not sure who owns it.
>>>>>
>>>>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little
>>>>> unclear on. Can someone help out with these tests? Or maybe should we
>>>>> consider just skipping them for 2.37.0?
>>>>>
>>>>> [1] https://github.com/apache/beam/pull/16849
>>>>> [2]
>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>> 0
>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>>>>
>>>>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com>
>>>>> wrote:
>>>>>
>>>>>> The 2.37.0 release branch has been cut [1]!
>>>>>>
>>>>>> There are a few open release blockers [2] - I'll be working with the
>>>>>> owners to get them resolved over the next few days. It would be a great
>>>>>> help if everyone could review that list and close any issues that have been
>>>>>> resolved, or bump the fix version for anything that doesn't meet the
>>>>>> criteria at [3].
>>>>>>
>>>>>> Also, if you have any significant changes to announce, please send me
>>>>>> a PR which adds them to CHANGES.md [4].
>>>>>>
>>>>>> Thanks,
>>>>>> Brian
>>>>>>
>>>>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>>>>> [2]
>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>>> 0
>>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>>>>
>>>>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> +1 and don't hesitate to ask for help
>>>>>>>
>>>>>>> Kenn
>>>>>>>
>>>>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 and thank you Brian!
>>>>>>>>
>>>>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>>>>>>>> according to
>>>>>>>>> the release calendar [1].
>>>>>>>>>
>>>>>>>>> I would like to volunteer myself to do this release. My plan is to
>>>>>>>>> cut the branch on that date, and cherrypick release-blocking fixes
>>>>>>>>> afterwards if any.
>>>>>>>>>
>>>>>>>>> Please help the release go smoothly by:
>>>>>>>>> - Making sure that any unresolved release blocking JIRA issues for
>>>>>>>>> 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>>>>> possible.
>>>>>>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>>>>>>> Version/s" if they don't meet the criteria at [3].
>>>>>>>>>
>>>>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Brian
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>> [2]
>>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>>
>>>>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Ahmet Altay <al...@google.com>.
Thank you Brian!
On Tue, Feb 15, 2022 at 11:24 AM Brian Hulette <bh...@google.com> wrote:
> [1] is accurate right now. There are three open release blockers, but all
> have fixes in the process of merging to master and/or release-2.37.0.
> Thanks everyone for your quick responses!
>
> I should be able to get these merged and finish validating the branch
> today and move on to making an RC, assuming ci-beam cooperates [2] and
> nothing else comes up.
>
> [1]
> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
> [2] https://issues.apache.org/jira/browse/INFRA-22878
>
> On Tue, Feb 15, 2022 at 11:03 AM Ahmet Altay <al...@google.com> wrote:
>
>> Brian, what are the remaining blockers on the release? Are you blocked?
>>
>> On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com> wrote:
>>
>>> PVR Spark 2 Streaming should not be a release blocker, since this test
>>> suite was never consistently green to begin with.
>>>
>>>
>>> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com>
>>> wrote:
>>>
>>>> I ran some PostCommits and VR suites on the release branch today [1]
>>>> and found that several are failing. Some are just related to missing
>>>> Dataflow containers, but many are real failures.
>>>>
>>>> I'm going through these failures and making sure we have release
>>>> blocking jiras [2] filed for them. I'll try to ping relevant people on the
>>>> jiras themselves, but I may raise some issues here if it's not making
>>>> progress or I'm not sure who owns it.
>>>>
>>>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little unclear
>>>> on. Can someone help out with these tests? Or maybe should we consider just
>>>> skipping them for 2.37.0?
>>>>
>>>> [1] https://github.com/apache/beam/pull/16849
>>>> [2]
>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>> 0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>>>
>>>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com>
>>>> wrote:
>>>>
>>>>> The 2.37.0 release branch has been cut [1]!
>>>>>
>>>>> There are a few open release blockers [2] - I'll be working with the
>>>>> owners to get them resolved over the next few days. It would be a great
>>>>> help if everyone could review that list and close any issues that have been
>>>>> resolved, or bump the fix version for anything that doesn't meet the
>>>>> criteria at [3].
>>>>>
>>>>> Also, if you have any significant changes to announce, please send me
>>>>> a PR which adds them to CHANGES.md [4].
>>>>>
>>>>> Thanks,
>>>>> Brian
>>>>>
>>>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>>>> [2]
>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>>> 0
>>>>> %20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>>>
>>>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> +1 and don't hesitate to ask for help
>>>>>>
>>>>>> Kenn
>>>>>>
>>>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com> wrote:
>>>>>>
>>>>>>> +1 and thank you Brian!
>>>>>>>
>>>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>>>>>>> according to
>>>>>>>> the release calendar [1].
>>>>>>>>
>>>>>>>> I would like to volunteer myself to do this release. My plan is to
>>>>>>>> cut the branch on that date, and cherrypick release-blocking fixes
>>>>>>>> afterwards if any.
>>>>>>>>
>>>>>>>> Please help the release go smoothly by:
>>>>>>>> - Making sure that any unresolved release blocking JIRA issues for
>>>>>>>> 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>>>> possible.
>>>>>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>>>>>> Version/s" if they don't meet the criteria at [3].
>>>>>>>>
>>>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Brian
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>> [2]
>>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>>
>>>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Brian Hulette <bh...@google.com>.
[1] is accurate right now. There are three open release blockers, but all
have fixes in the process of merging to master and/or release-2.37.0.
Thanks everyone for your quick responses!
I should be able to get these merged and finish validating the branch today
and move on to making an RC, assuming ci-beam cooperates [2] and nothing
else comes up.
[1]
https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
[2] https://issues.apache.org/jira/browse/INFRA-22878
On Tue, Feb 15, 2022 at 11:03 AM Ahmet Altay <al...@google.com> wrote:
> Brian, what are the remaining blockers on the release? Are you blocked?
>
> On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com> wrote:
>
>> PVR Spark 2 Streaming should not be a release blocker, since this test
>> suite was never consistently green to begin with.
>>
>>
>> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com>
>> wrote:
>>
>>> I ran some PostCommits and VR suites on the release branch today [1] and
>>> found that several are failing. Some are just related to missing Dataflow
>>> containers, but many are real failures.
>>>
>>> I'm going through these failures and making sure we have release
>>> blocking jiras [2] filed for them. I'll try to ping relevant people on the
>>> jiras themselves, but I may raise some issues here if it's not making
>>> progress or I'm not sure who owns it.
>>>
>>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little unclear
>>> on. Can someone help out with these tests? Or maybe should we consider just
>>> skipping them for 2.37.0?
>>>
>>> [1] https://github.com/apache/beam/pull/16849
>>> [2]
>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>> 0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>>
>>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com>
>>> wrote:
>>>
>>>> The 2.37.0 release branch has been cut [1]!
>>>>
>>>> There are a few open release blockers [2] - I'll be working with the
>>>> owners to get them resolved over the next few days. It would be a great
>>>> help if everyone could review that list and close any issues that have been
>>>> resolved, or bump the fix version for anything that doesn't meet the
>>>> criteria at [3].
>>>>
>>>> Also, if you have any significant changes to announce, please send me a
>>>> PR which adds them to CHANGES.md [4].
>>>>
>>>> Thanks,
>>>> Brian
>>>>
>>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>>> [2]
>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>>> 0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>>
>>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org>
>>>> wrote:
>>>>
>>>>> +1 and don't hesitate to ask for help
>>>>>
>>>>> Kenn
>>>>>
>>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> +1 and thank you Brian!
>>>>>>
>>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>>>>>> according to
>>>>>>> the release calendar [1].
>>>>>>>
>>>>>>> I would like to volunteer myself to do this release. My plan is to
>>>>>>> cut the branch on that date, and cherrypick release-blocking fixes
>>>>>>> afterwards if any.
>>>>>>>
>>>>>>> Please help the release go smoothly by:
>>>>>>> - Making sure that any unresolved release blocking JIRA issues for
>>>>>>> 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>>> possible.
>>>>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>>>>> Version/s" if they don't meet the criteria at [3].
>>>>>>>
>>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Brian
>>>>>>>
>>>>>>> [1]
>>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>> [2]
>>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>>
>>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Ahmet Altay <al...@google.com>.
Brian, what are the remaining blockers on the release? Are you blocked?
On Tue, Feb 15, 2022 at 10:27 AM Kyle Weaver <kc...@google.com> wrote:
> PVR Spark 2 Streaming should not be a release blocker, since this test
> suite was never consistently green to begin with.
>
>
> On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com> wrote:
>
>> I ran some PostCommits and VR suites on the release branch today [1] and
>> found that several are failing. Some are just related to missing Dataflow
>> containers, but many are real failures.
>>
>> I'm going through these failures and making sure we have release blocking
>> jiras [2] filed for them. I'll try to ping relevant people on the jiras
>> themselves, but I may raise some issues here if it's not making progress or
>> I'm not sure who owns it.
>>
>> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little unclear
>> on. Can someone help out with these tests? Or maybe should we consider just
>> skipping them for 2.37.0?
>>
>> [1] https://github.com/apache/beam/pull/16849
>> [2]
>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>> 0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>> [3] https://issues.apache.org/jira/browse/BEAM-13950
>>
>> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com> wrote:
>>
>>> The 2.37.0 release branch has been cut [1]!
>>>
>>> There are a few open release blockers [2] - I'll be working with the
>>> owners to get them resolved over the next few days. It would be a great
>>> help if everyone could review that list and close any issues that have been
>>> resolved, or bump the fix version for anything that doesn't meet the
>>> criteria at [3].
>>>
>>> Also, if you have any significant changes to announce, please send me a
>>> PR which adds them to CHANGES.md [4].
>>>
>>> Thanks,
>>> Brian
>>>
>>> [1] https://github.com/apache/beam/tree/release-2.37.0
>>> [2]
>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>>> 0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>> [3] https://beam.apache.org/contribute/release-blocking/
>>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>>
>>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org> wrote:
>>>
>>>> +1 and don't hesitate to ask for help
>>>>
>>>> Kenn
>>>>
>>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> +1 and thank you Brian!
>>>>>
>>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>>>>> according to
>>>>>> the release calendar [1].
>>>>>>
>>>>>> I would like to volunteer myself to do this release. My plan is to
>>>>>> cut the branch on that date, and cherrypick release-blocking fixes
>>>>>> afterwards if any.
>>>>>>
>>>>>> Please help the release go smoothly by:
>>>>>> - Making sure that any unresolved release blocking JIRA issues for
>>>>>> 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>>> possible.
>>>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>>>> Version/s" if they don't meet the criteria at [3].
>>>>>>
>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>
>>>>>> Thanks,
>>>>>> Brian
>>>>>>
>>>>>> [1]
>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>> [2]
>>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>
>>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Kyle Weaver <kc...@google.com>.
PVR Spark 2 Streaming should not be a release blocker, since this test
suite was never consistently green to begin with.
On Mon, Feb 14, 2022 at 5:38 PM Brian Hulette <bh...@google.com> wrote:
> I ran some PostCommits and VR suites on the release branch today [1] and
> found that several are failing. Some are just related to missing Dataflow
> containers, but many are real failures.
>
> I'm going through these failures and making sure we have release blocking
> jiras [2] filed for them. I'll try to ping relevant people on the jiras
> themselves, but I may raise some issues here if it's not making progress or
> I'm not sure who owns it.
>
> BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little unclear
> on. Can someone help out with these tests? Or maybe should we consider just
> skipping them for 2.37.0?
>
> [1] https://github.com/apache/beam/pull/16849
> [2]
> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
> 0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
> [3] https://issues.apache.org/jira/browse/BEAM-13950
>
> On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com> wrote:
>
>> The 2.37.0 release branch has been cut [1]!
>>
>> There are a few open release blockers [2] - I'll be working with the
>> owners to get them resolved over the next few days. It would be a great
>> help if everyone could review that list and close any issues that have been
>> resolved, or bump the fix version for anything that doesn't meet the
>> criteria at [3].
>>
>> Also, if you have any significant changes to announce, please send me a
>> PR which adds them to CHANGES.md [4].
>>
>> Thanks,
>> Brian
>>
>> [1] https://github.com/apache/beam/tree/release-2.37.0
>> [2]
>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
>> 0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>> [3] https://beam.apache.org/contribute/release-blocking/
>> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>>
>> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org> wrote:
>>
>>> +1 and don't hesitate to ask for help
>>>
>>> Kenn
>>>
>>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> +1 and thank you Brian!
>>>>
>>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>>>> according to
>>>>> the release calendar [1].
>>>>>
>>>>> I would like to volunteer myself to do this release. My plan is to cut
>>>>> the branch on that date, and cherrypick release-blocking fixes afterwards
>>>>> if any.
>>>>>
>>>>> Please help the release go smoothly by:
>>>>> - Making sure that any unresolved release blocking JIRA issues for
>>>>> 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>>> possible.
>>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>>> Version/s" if they don't meet the criteria at [3].
>>>>>
>>>>> Let me know if you have any comments/objections/questions.
>>>>>
>>>>> Thanks,
>>>>> Brian
>>>>>
>>>>> [1]
>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>> [2]
>>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>
>>>>
Re: [PROPOSAL] Preparing for 2.37.0 Release
Posted by Brian Hulette <bh...@google.com>.
I ran some PostCommits and VR suites on the release branch today [1] and
found that several are failing. Some are just related to missing Dataflow
containers, but many are real failures.
I'm going through these failures and making sure we have release blocking
jiras [2] filed for them. I'll try to ping relevant people on the jiras
themselves, but I may raise some issues here if it's not making progress or
I'm not sure who owns it.
BEAM-13950 (PVR Spark 2 Streaming) [3] is one that I'm a little unclear on.
Can someone help out with these tests? Or maybe should we consider just
skipping them for 2.37.0?
[1] https://github.com/apache/beam/pull/16849
[2]
https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
[3] https://issues.apache.org/jira/browse/BEAM-13950
On Wed, Feb 9, 2022 at 5:53 PM Brian Hulette <bh...@google.com> wrote:
> The 2.37.0 release branch has been cut [1]!
>
> There are a few open release blockers [2] - I'll be working with the
> owners to get them resolved over the next few days. It would be a great
> help if everyone could review that list and close any issues that have been
> resolved, or bump the fix version for anything that doesn't meet the
> criteria at [3].
>
> Also, if you have any significant changes to announce, please send me a PR
> which adds them to CHANGES.md [4].
>
> Thanks,
> Brian
>
> [1] https://github.com/apache/beam/tree/release-2.37.0
> [2]
> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.
> 0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
> [3] https://beam.apache.org/contribute/release-blocking/
> [4] https://github.com/apache/beam/blob/master/CHANGES.md
>
> On Mon, Jan 31, 2022 at 6:01 AM Kenneth Knowles <ke...@apache.org> wrote:
>
>> +1 and don't hesitate to ask for help
>>
>> Kenn
>>
>> On Fri, Jan 28, 2022 at 3:41 PM Ahmet Altay <al...@google.com> wrote:
>>
>>> +1 and thank you Brian!
>>>
>>> On Fri, Jan 28, 2022 at 2:47 PM Brian Hulette <bh...@google.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> The next (2.37.0) release branch cut is scheduled for 9 February,
>>>> according to
>>>> the release calendar [1].
>>>>
>>>> I would like to volunteer myself to do this release. My plan is to cut
>>>> the branch on that date, and cherrypick release-blocking fixes afterwards
>>>> if any.
>>>>
>>>> Please help the release go smoothly by:
>>>> - Making sure that any unresolved release blocking JIRA issues for
>>>> 2.37.0 should have their "Fix Version/s" marked as "2.37.0" as soon as
>>>> possible.
>>>> - Reviewing the current release blockers [2] and remove the "Fix
>>>> Version/s" if they don't meet the criteria at [3].
>>>>
>>>> Let me know if you have any comments/objections/questions.
>>>>
>>>> Thanks,
>>>> Brian
>>>>
>>>> [1]
>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>> [2]
>>>> https://issues.apache.org/jira/issues/?filter=-1&jql=project%3DBEAM%20and%20fixVersion%3D2.37.0%20%20AND%20statusCategory%20!%3D%20Done%20order%20by%20updated%20DESC
>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>
>>>