You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Ankur Goenka <go...@google.com> on 2021/07/07 16:20:15 UTC
[PROPOSAL] Preparing for Beam 2.32.0 release
Hi All,
Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
released by Aug 18th according to the release calendar [1].
If there are no objections then I would like to nominate myself to do this
release.
Sorry for the shorter notice as I was OOO for an extended period of time.
Please review your bug list and mark the blockers as blocker for the
release and move non blockers to the next release by July 14th.
Please let me know if you have any questions.
Thanks,
Ankur
[1]
https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
I agree with Ahmet that these PRs do not meet cherry pick criteria.
I am pretty much done with RC1 creation. We can discuss more if we go for
RC2.
Thanks,
Ankur
On Thu, Aug 19, 2021 at 7:56 PM Luke Cwik <lc...@google.com> wrote:
> Also the next release starts next week on Wednesday.
>
> On Thu, Aug 19, 2021 at 5:44 PM Ahmet Altay <al...@google.com> wrote:
>
>> I am not the release manager, but I do not think these PRs meet the
>> cherry pick criteria [1].
>>
>> https://github.com/apache/beam/pull/15237 -> is a P2 issue and not a new
>> regression, it exists since 2.30.0.
>> https://github.com/apache/beam/pull/15352 -> test code change
>> https://issues.apache.org/jira/browse/BEAM-12628 -> is a P2 issue and
>> not a new regression, it exists in 2.30.0.
>>
>> Building an RC takes a considerable amount of time and we are close to
>> RC1. I would suggest not including them in RC1, and if there will be an RC2
>> Ankur could make a cherry pick decision at that time,
>>
>> Ahmet
>>
>> [1] https://beam.apache.org/contribute/release-guide/#review-cherry-picks
>>
>> On Thu, Aug 19, 2021 at 5:41 PM Kirill Panarin <ki...@gmail.com>
>> wrote:
>>
>>> +1 to include the fix for
>>> https://issues.apache.org/jira/browse/BEAM-12628! 🙏
>>>
>>> Thanks,
>>> Kirill
>>>
>>> On Thu, Aug 19, 2021 at 8:29 PM Claire McGinty <
>>> claire.d.mcginty@gmail.com> wrote:
>>>
>>>> Hi! To add on, would you also consider including the cherry-picked
>>>> commit from
>>>> https://issues.apache.org/jira/browse/BEAM-12628 since it does include
>>>> a bug fix?
>>>>
>>>> -Claire
>>>>
>>>> On Thu, Aug 19, 2021 at 8:26 PM Sayat Satybaldiyev <
>>>> sayat.satybaldiyev@getcruise.com> wrote:
>>>>
>>>>> Hello Ankur,
>>>>>
>>>>> I am wondering would you consider having commits from this PRs in the
>>>>> release if I make cherry-picks commits to resolve the issue with BQ write
>>>>> connector?
>>>>>
>>>>> https://github.com/apache/beam/pull/15237
>>>>> https://github.com/apache/beam/pull/15352
>>>>>
>>>>> On Mon, Aug 16, 2021 at 9:59 AM Ankur Goenka <go...@google.com>
>>>>> wrote:
>>>>>
>>>>>> The issue regarding Dataflow Validation is resolved. Will do the
>>>>>> validation and post RC1 for voting once the validation is done.
>>>>>>
>>>>>> On Tue, Aug 10, 2021 at 9:22 PM Ankur Goenka <go...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> For the release branch release-2.32.0
>>>>>>> <https://github.com/apache/beam/tree/release-2.32.0> is the right
>>>>>>> one. I think 2.32 was created by mistake somewhere along the way.
>>>>>>>
>>>>>>> The 2 blocking issues 123723 and 12676 seems to have the same
>>>>>>> testing project issue tracked in the b/195313999
>>>>>>> <https://buganizer.corp.google.com/195313999> I am not waiting on
>>>>>>> the fix for this issue as this is only a test configuration issue.
>>>>>>>
>>>>>>> I am in the process of promoting RC1 for validation which should be
>>>>>>> out in another hour.
>>>>>>>
>>>>>>> PR https://github.com/apache/beam/pull/15237 doesn't fix a
>>>>>>> regression so it's not a blocker. I will pick it up if we endup creating a
>>>>>>> new RC.
>>>>>>>
>>>>>>> On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <lc...@google.com> wrote:
>>>>>>>
>>>>>>>> Buquian doesn't seem to have a JIRA account to reassign it
>>>>>>>> appropriately. Buquian can you create one and provide your JIRA user name?
>>>>>>>>
>>>>>>>> Slava you are a contributor in JIRA so I believe you should be able
>>>>>>>> to reassign the issue. Were you logged into JIRA?
>>>>>>>>
>>>>>>>> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>>>> is assigned to me by mistake. I dont have permissions to change the issue
>>>>>>>>> though. Buquian has a solution for that issue.
>>>>>>>>>
>>>>>>>>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> The remaining open issues are all related to the test failures in
>>>>>>>>>> the apache-beam-testing project due to b/195313999
>>>>>>>>>> <https://buganizer.corp.google.com/195313999>. This is also
>>>>>>>>>> impacting out precommits for open PRs making it difficult for the Apache
>>>>>>>>>> Beam community to get a green signal before merging code so code is being
>>>>>>>>>> merged with assumptions that the failure is due to the streaming issue.
>>>>>>>>>>
>>>>>>>>>> Ahmet, I added you to the thread that has more details as well in
>>>>>>>>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>>>>>>>>>
>>>>>>>>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <
>>>>>>>>>> pabloem@google.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I'd like to request that we also include a cherry-pick for
>>>>>>>>>>> https://github.com/apache/beam/pull/15237
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>>>>>>>>>
>>>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same
>>>>>>>>>>>> as https://issues.apache.org/jira/browse/BEAM-12699 and is due
>>>>>>>>>>>> to a key negotiation error between the worker and streaming engine failing
>>>>>>>>>>>> so no work is done causing the job to fail.
>>>>>>>>>>>>
>>>>>>>>>>>> Kiley has a comment that it seems as though this is a known
>>>>>>>>>>>> issue.
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Ankur, how is the release coming along?
>>>>>>>>>>>>>
>>>>>>>>>>>>> I noticed there are 2 open blockers:
>>>>>>>>>>>>> - One assigned to @Slava Chernyak <ch...@google.com> -
>>>>>>>>>>>>> Could you check with Slava, he may not be aware that this is a release
>>>>>>>>>>>>> blocker. (https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>>>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>>>>>>>>>> Cwik <lc...@google.com> ?) (
>>>>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ahmet
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>>>>>>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I noticed that we seems to have two branches for this release:
>>>>>>>>>>>>>> "release-2.32" (
>>>>>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32) and
>>>>>>>>>>>>>> "release-2.32.0” (
>>>>>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Is it intended or not? Would it better to keep only one to
>>>>>>>>>>>>>> avoid a confusion?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> —
>>>>>>>>>>>>>> Alexey
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> If there are no objections then I would like to nominate
>>>>>>>>>>>>>> myself to do this release.
>>>>>>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended
>>>>>>>>>>>>>> period of time.
>>>>>>>>>>>>>> Please review your bug list and mark the blockers as blocker
>>>>>>>>>>>>>> for the release and move non blockers to the next release by July 14th.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Ankur
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [1]
>>>>>>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks,
>>>>>>>>> - Slava Chernyak
>>>>>>>>>
>>>>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Sayat Satybaldyev
>>>>>
>>>>> Cruise
>>>>>
>>>>>
>>>>> *Confidentiality Note:* We care about protecting our proprietary
>>>>> information, confidential material, and trade secrets. This message
>>>>> may contain some or all of those things. Cruise will suffer material harm
>>>>> if anyone other than the intended recipient disseminates or takes any
>>>>> action based on this message. If you have received this message (including
>>>>> any attachments) in error, please delete it immediately and notify the
>>>>> sender promptly.
>>>>
>>>>
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Luke Cwik <lc...@google.com>.
Also the next release starts next week on Wednesday.
On Thu, Aug 19, 2021 at 5:44 PM Ahmet Altay <al...@google.com> wrote:
> I am not the release manager, but I do not think these PRs meet the cherry
> pick criteria [1].
>
> https://github.com/apache/beam/pull/15237 -> is a P2 issue and not a new
> regression, it exists since 2.30.0.
> https://github.com/apache/beam/pull/15352 -> test code change
> https://issues.apache.org/jira/browse/BEAM-12628 -> is a P2 issue and
> not a new regression, it exists in 2.30.0.
>
> Building an RC takes a considerable amount of time and we are close to
> RC1. I would suggest not including them in RC1, and if there will be an RC2
> Ankur could make a cherry pick decision at that time,
>
> Ahmet
>
> [1] https://beam.apache.org/contribute/release-guide/#review-cherry-picks
>
> On Thu, Aug 19, 2021 at 5:41 PM Kirill Panarin <ki...@gmail.com>
> wrote:
>
>> +1 to include the fix for
>> https://issues.apache.org/jira/browse/BEAM-12628! 🙏
>>
>> Thanks,
>> Kirill
>>
>> On Thu, Aug 19, 2021 at 8:29 PM Claire McGinty <
>> claire.d.mcginty@gmail.com> wrote:
>>
>>> Hi! To add on, would you also consider including the cherry-picked
>>> commit from
>>> https://issues.apache.org/jira/browse/BEAM-12628 since it does include
>>> a bug fix?
>>>
>>> -Claire
>>>
>>> On Thu, Aug 19, 2021 at 8:26 PM Sayat Satybaldiyev <
>>> sayat.satybaldiyev@getcruise.com> wrote:
>>>
>>>> Hello Ankur,
>>>>
>>>> I am wondering would you consider having commits from this PRs in the
>>>> release if I make cherry-picks commits to resolve the issue with BQ write
>>>> connector?
>>>>
>>>> https://github.com/apache/beam/pull/15237
>>>> https://github.com/apache/beam/pull/15352
>>>>
>>>> On Mon, Aug 16, 2021 at 9:59 AM Ankur Goenka <go...@google.com> wrote:
>>>>
>>>>> The issue regarding Dataflow Validation is resolved. Will do the
>>>>> validation and post RC1 for voting once the validation is done.
>>>>>
>>>>> On Tue, Aug 10, 2021 at 9:22 PM Ankur Goenka <go...@google.com>
>>>>> wrote:
>>>>>
>>>>>> For the release branch release-2.32.0
>>>>>> <https://github.com/apache/beam/tree/release-2.32.0> is the right
>>>>>> one. I think 2.32 was created by mistake somewhere along the way.
>>>>>>
>>>>>> The 2 blocking issues 123723 and 12676 seems to have the same testing
>>>>>> project issue tracked in the b/195313999
>>>>>> <https://buganizer.corp.google.com/195313999> I am not waiting on
>>>>>> the fix for this issue as this is only a test configuration issue.
>>>>>>
>>>>>> I am in the process of promoting RC1 for validation which should be
>>>>>> out in another hour.
>>>>>>
>>>>>> PR https://github.com/apache/beam/pull/15237 doesn't fix a
>>>>>> regression so it's not a blocker. I will pick it up if we endup creating a
>>>>>> new RC.
>>>>>>
>>>>>> On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <lc...@google.com> wrote:
>>>>>>
>>>>>>> Buquian doesn't seem to have a JIRA account to reassign it
>>>>>>> appropriately. Buquian can you create one and provide your JIRA user name?
>>>>>>>
>>>>>>> Slava you are a contributor in JIRA so I believe you should be able
>>>>>>> to reassign the issue. Were you logged into JIRA?
>>>>>>>
>>>>>>> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>>> is assigned to me by mistake. I dont have permissions to change the issue
>>>>>>>> though. Buquian has a solution for that issue.
>>>>>>>>
>>>>>>>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
>>>>>>>>
>>>>>>>>> The remaining open issues are all related to the test failures in
>>>>>>>>> the apache-beam-testing project due to b/195313999
>>>>>>>>> <https://buganizer.corp.google.com/195313999>. This is also
>>>>>>>>> impacting out precommits for open PRs making it difficult for the Apache
>>>>>>>>> Beam community to get a green signal before merging code so code is being
>>>>>>>>> merged with assumptions that the failure is due to the streaming issue.
>>>>>>>>>
>>>>>>>>> Ahmet, I added you to the thread that has more details as well in
>>>>>>>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>>>>>>>>
>>>>>>>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I'd like to request that we also include a cherry-pick for
>>>>>>>>>> https://github.com/apache/beam/pull/15237
>>>>>>>>>>
>>>>>>>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>>>>>>>>
>>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to
>>>>>>>>>>> a key negotiation error between the worker and streaming engine failing so
>>>>>>>>>>> no work is done causing the job to fail.
>>>>>>>>>>>
>>>>>>>>>>> Kiley has a comment that it seems as though this is a known
>>>>>>>>>>> issue.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Ankur, how is the release coming along?
>>>>>>>>>>>>
>>>>>>>>>>>> I noticed there are 2 open blockers:
>>>>>>>>>>>> - One assigned to @Slava Chernyak <ch...@google.com> -
>>>>>>>>>>>> Could you check with Slava, he may not be aware that this is a release
>>>>>>>>>>>> blocker. (https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>>>>>>>>> Cwik <lc...@google.com> ?) (
>>>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>>>>>>>>
>>>>>>>>>>>> Ahmet
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>>>>>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I noticed that we seems to have two branches for this release:
>>>>>>>>>>>>> "release-2.32" (
>>>>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32) and
>>>>>>>>>>>>> "release-2.32.0” (
>>>>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Is it intended or not? Would it better to keep only one to
>>>>>>>>>>>>> avoid a confusion?
>>>>>>>>>>>>>
>>>>>>>>>>>>> —
>>>>>>>>>>>>> Alexey
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>>>>>
>>>>>>>>>>>>> If there are no objections then I would like to nominate
>>>>>>>>>>>>> myself to do this release.
>>>>>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended
>>>>>>>>>>>>> period of time.
>>>>>>>>>>>>> Please review your bug list and mark the blockers as blocker
>>>>>>>>>>>>> for the release and move non blockers to the next release by July 14th.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Ankur
>>>>>>>>>>>>>
>>>>>>>>>>>>> [1]
>>>>>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks,
>>>>>>>> - Slava Chernyak
>>>>>>>>
>>>>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Sayat Satybaldyev
>>>>
>>>> Cruise
>>>>
>>>>
>>>> *Confidentiality Note:* We care about protecting our proprietary
>>>> information, confidential material, and trade secrets. This message
>>>> may contain some or all of those things. Cruise will suffer material harm
>>>> if anyone other than the intended recipient disseminates or takes any
>>>> action based on this message. If you have received this message (including
>>>> any attachments) in error, please delete it immediately and notify the
>>>> sender promptly.
>>>
>>>
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ahmet Altay <al...@google.com>.
I am not the release manager, but I do not think these PRs meet the cherry
pick criteria [1].
https://github.com/apache/beam/pull/15237 -> is a P2 issue and not a new
regression, it exists since 2.30.0.
https://github.com/apache/beam/pull/15352 -> test code change
https://issues.apache.org/jira/browse/BEAM-12628 -> is a P2 issue and not
a new regression, it exists in 2.30.0.
Building an RC takes a considerable amount of time and we are close to RC1.
I would suggest not including them in RC1, and if there will be an RC2
Ankur could make a cherry pick decision at that time,
Ahmet
[1] https://beam.apache.org/contribute/release-guide/#review-cherry-picks
On Thu, Aug 19, 2021 at 5:41 PM Kirill Panarin <ki...@gmail.com>
wrote:
> +1 to include the fix for https://issues.apache.org/jira/browse/BEAM-12628
> ! 🙏
>
> Thanks,
> Kirill
>
> On Thu, Aug 19, 2021 at 8:29 PM Claire McGinty <cl...@gmail.com>
> wrote:
>
>> Hi! To add on, would you also consider including the cherry-picked commit
>> from
>> https://issues.apache.org/jira/browse/BEAM-12628 since it does include a
>> bug fix?
>>
>> -Claire
>>
>> On Thu, Aug 19, 2021 at 8:26 PM Sayat Satybaldiyev <
>> sayat.satybaldiyev@getcruise.com> wrote:
>>
>>> Hello Ankur,
>>>
>>> I am wondering would you consider having commits from this PRs in the
>>> release if I make cherry-picks commits to resolve the issue with BQ write
>>> connector?
>>>
>>> https://github.com/apache/beam/pull/15237
>>> https://github.com/apache/beam/pull/15352
>>>
>>> On Mon, Aug 16, 2021 at 9:59 AM Ankur Goenka <go...@google.com> wrote:
>>>
>>>> The issue regarding Dataflow Validation is resolved. Will do the
>>>> validation and post RC1 for voting once the validation is done.
>>>>
>>>> On Tue, Aug 10, 2021 at 9:22 PM Ankur Goenka <go...@google.com> wrote:
>>>>
>>>>> For the release branch release-2.32.0
>>>>> <https://github.com/apache/beam/tree/release-2.32.0> is the right
>>>>> one. I think 2.32 was created by mistake somewhere along the way.
>>>>>
>>>>> The 2 blocking issues 123723 and 12676 seems to have the same testing
>>>>> project issue tracked in the b/195313999
>>>>> <https://buganizer.corp.google.com/195313999> I am not waiting on the
>>>>> fix for this issue as this is only a test configuration issue.
>>>>>
>>>>> I am in the process of promoting RC1 for validation which should be
>>>>> out in another hour.
>>>>>
>>>>> PR https://github.com/apache/beam/pull/15237 doesn't fix a regression
>>>>> so it's not a blocker. I will pick it up if we endup creating a new RC.
>>>>>
>>>>> On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <lc...@google.com> wrote:
>>>>>
>>>>>> Buquian doesn't seem to have a JIRA account to reassign it
>>>>>> appropriately. Buquian can you create one and provide your JIRA user name?
>>>>>>
>>>>>> Slava you are a contributor in JIRA so I believe you should be able
>>>>>> to reassign the issue. Were you logged into JIRA?
>>>>>>
>>>>>> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is
>>>>>>> assigned to me by mistake. I dont have permissions to change the issue
>>>>>>> though. Buquian has a solution for that issue.
>>>>>>>
>>>>>>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
>>>>>>>
>>>>>>>> The remaining open issues are all related to the test failures in
>>>>>>>> the apache-beam-testing project due to b/195313999
>>>>>>>> <https://buganizer.corp.google.com/195313999>. This is also
>>>>>>>> impacting out precommits for open PRs making it difficult for the Apache
>>>>>>>> Beam community to get a green signal before merging code so code is being
>>>>>>>> merged with assumptions that the failure is due to the streaming issue.
>>>>>>>>
>>>>>>>> Ahmet, I added you to the thread that has more details as well in
>>>>>>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>>>>>>>
>>>>>>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I'd like to request that we also include a cherry-pick for
>>>>>>>>> https://github.com/apache/beam/pull/15237
>>>>>>>>>
>>>>>>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>>>>>>>
>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a
>>>>>>>>>> key negotiation error between the worker and streaming engine failing so no
>>>>>>>>>> work is done causing the job to fail.
>>>>>>>>>>
>>>>>>>>>> Kiley has a comment that it seems as though this is a known issue.
>>>>>>>>>>
>>>>>>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Ankur, how is the release coming along?
>>>>>>>>>>>
>>>>>>>>>>> I noticed there are 2 open blockers:
>>>>>>>>>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could
>>>>>>>>>>> you check with Slava, he may not be aware that this is a release blocker. (
>>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>>>>>>>> Cwik <lc...@google.com> ?) (
>>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>>>>>>>
>>>>>>>>>>> Ahmet
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>>>>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I noticed that we seems to have two branches for this release:
>>>>>>>>>>>> "release-2.32" (
>>>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32) and
>>>>>>>>>>>> "release-2.32.0” (
>>>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>>>>>>>
>>>>>>>>>>>> Is it intended or not? Would it better to keep only one to
>>>>>>>>>>>> avoid a confusion?
>>>>>>>>>>>>
>>>>>>>>>>>> —
>>>>>>>>>>>> Alexey
>>>>>>>>>>>>
>>>>>>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>
>>>>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>>>>
>>>>>>>>>>>> If there are no objections then I would like to nominate myself
>>>>>>>>>>>> to do this release.
>>>>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended
>>>>>>>>>>>> period of time.
>>>>>>>>>>>> Please review your bug list and mark the blockers as blocker
>>>>>>>>>>>> for the release and move non blockers to the next release by July 14th.
>>>>>>>>>>>>
>>>>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Ankur
>>>>>>>>>>>>
>>>>>>>>>>>> [1]
>>>>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks,
>>>>>>> - Slava Chernyak
>>>>>>>
>>>>>>
>>>
>>> --
>>>
>>>
>>> Sayat Satybaldyev
>>>
>>> Cruise
>>>
>>>
>>> *Confidentiality Note:* We care about protecting our proprietary
>>> information, confidential material, and trade secrets. This message may
>>> contain some or all of those things. Cruise will suffer material harm if
>>> anyone other than the intended recipient disseminates or takes any action
>>> based on this message. If you have received this message (including any
>>> attachments) in error, please delete it immediately and notify the sender
>>> promptly.
>>
>>
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Kirill Panarin <ki...@gmail.com>.
+1 to include the fix for https://issues.apache.org/jira/browse/BEAM-12628
! 🙏
Thanks,
Kirill
On Thu, Aug 19, 2021 at 8:29 PM Claire McGinty <cl...@gmail.com>
wrote:
> Hi! To add on, would you also consider including the cherry-picked commit
> from
> https://issues.apache.org/jira/browse/BEAM-12628 since it does include a
> bug fix?
>
> -Claire
>
> On Thu, Aug 19, 2021 at 8:26 PM Sayat Satybaldiyev <
> sayat.satybaldiyev@getcruise.com> wrote:
>
>> Hello Ankur,
>>
>> I am wondering would you consider having commits from this PRs in the
>> release if I make cherry-picks commits to resolve the issue with BQ write
>> connector?
>>
>> https://github.com/apache/beam/pull/15237
>> https://github.com/apache/beam/pull/15352
>>
>> On Mon, Aug 16, 2021 at 9:59 AM Ankur Goenka <go...@google.com> wrote:
>>
>>> The issue regarding Dataflow Validation is resolved. Will do the
>>> validation and post RC1 for voting once the validation is done.
>>>
>>> On Tue, Aug 10, 2021 at 9:22 PM Ankur Goenka <go...@google.com> wrote:
>>>
>>>> For the release branch release-2.32.0
>>>> <https://github.com/apache/beam/tree/release-2.32.0> is the right one.
>>>> I think 2.32 was created by mistake somewhere along the way.
>>>>
>>>> The 2 blocking issues 123723 and 12676 seems to have the same testing
>>>> project issue tracked in the b/195313999
>>>> <https://buganizer.corp.google.com/195313999> I am not waiting on the
>>>> fix for this issue as this is only a test configuration issue.
>>>>
>>>> I am in the process of promoting RC1 for validation which should be out
>>>> in another hour.
>>>>
>>>> PR https://github.com/apache/beam/pull/15237 doesn't fix a regression
>>>> so it's not a blocker. I will pick it up if we endup creating a new RC.
>>>>
>>>> On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <lc...@google.com> wrote:
>>>>
>>>>> Buquian doesn't seem to have a JIRA account to reassign it
>>>>> appropriately. Buquian can you create one and provide your JIRA user name?
>>>>>
>>>>> Slava you are a contributor in JIRA so I believe you should be able to
>>>>> reassign the issue. Were you logged into JIRA?
>>>>>
>>>>> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com>
>>>>> wrote:
>>>>>
>>>>>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is
>>>>>> assigned to me by mistake. I dont have permissions to change the issue
>>>>>> though. Buquian has a solution for that issue.
>>>>>>
>>>>>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
>>>>>>
>>>>>>> The remaining open issues are all related to the test failures in
>>>>>>> the apache-beam-testing project due to b/195313999
>>>>>>> <https://buganizer.corp.google.com/195313999>. This is also
>>>>>>> impacting out precommits for open PRs making it difficult for the Apache
>>>>>>> Beam community to get a green signal before merging code so code is being
>>>>>>> merged with assumptions that the failure is due to the streaming issue.
>>>>>>>
>>>>>>> Ahmet, I added you to the thread that has more details as well in
>>>>>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>>>>>>
>>>>>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I'd like to request that we also include a cherry-pick for
>>>>>>>> https://github.com/apache/beam/pull/15237
>>>>>>>>
>>>>>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>>>>>>
>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a
>>>>>>>>> key negotiation error between the worker and streaming engine failing so no
>>>>>>>>> work is done causing the job to fail.
>>>>>>>>>
>>>>>>>>> Kiley has a comment that it seems as though this is a known issue.
>>>>>>>>>
>>>>>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Ankur, how is the release coming along?
>>>>>>>>>>
>>>>>>>>>> I noticed there are 2 open blockers:
>>>>>>>>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could
>>>>>>>>>> you check with Slava, he may not be aware that this is a release blocker. (
>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>>>>>>> Cwik <lc...@google.com> ?) (
>>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>>>>>>
>>>>>>>>>> Ahmet
>>>>>>>>>>
>>>>>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>>>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I noticed that we seems to have two branches for this release:
>>>>>>>>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32)
>>>>>>>>>>> and "release-2.32.0” (
>>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>>>>>>
>>>>>>>>>>> Is it intended or not? Would it better to keep only one to avoid
>>>>>>>>>>> a confusion?
>>>>>>>>>>>
>>>>>>>>>>> —
>>>>>>>>>>> Alexey
>>>>>>>>>>>
>>>>>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi All,
>>>>>>>>>>>
>>>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>>>
>>>>>>>>>>> If there are no objections then I would like to nominate myself
>>>>>>>>>>> to do this release.
>>>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period
>>>>>>>>>>> of time.
>>>>>>>>>>> Please review your bug list and mark the blockers as blocker for
>>>>>>>>>>> the release and move non blockers to the next release by July 14th.
>>>>>>>>>>>
>>>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Ankur
>>>>>>>>>>>
>>>>>>>>>>> [1]
>>>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks,
>>>>>> - Slava Chernyak
>>>>>>
>>>>>
>>
>> --
>>
>>
>> Sayat Satybaldyev
>>
>> Cruise
>>
>>
>> *Confidentiality Note:* We care about protecting our proprietary
>> information, confidential material, and trade secrets. This message may
>> contain some or all of those things. Cruise will suffer material harm if
>> anyone other than the intended recipient disseminates or takes any action
>> based on this message. If you have received this message (including any
>> attachments) in error, please delete it immediately and notify the sender
>> promptly.
>
>
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Claire McGinty <cl...@gmail.com>.
Hi! To add on, would you also consider including the cherry-picked commit
from
https://issues.apache.org/jira/browse/BEAM-12628 since it does include a
bug fix?
-Claire
On Thu, Aug 19, 2021 at 8:26 PM Sayat Satybaldiyev <
sayat.satybaldiyev@getcruise.com> wrote:
> Hello Ankur,
>
> I am wondering would you consider having commits from this PRs in the
> release if I make cherry-picks commits to resolve the issue with BQ write
> connector?
>
> https://github.com/apache/beam/pull/15237
> https://github.com/apache/beam/pull/15352
>
> On Mon, Aug 16, 2021 at 9:59 AM Ankur Goenka <go...@google.com> wrote:
>
>> The issue regarding Dataflow Validation is resolved. Will do the
>> validation and post RC1 for voting once the validation is done.
>>
>> On Tue, Aug 10, 2021 at 9:22 PM Ankur Goenka <go...@google.com> wrote:
>>
>>> For the release branch release-2.32.0
>>> <https://github.com/apache/beam/tree/release-2.32.0> is the right one.
>>> I think 2.32 was created by mistake somewhere along the way.
>>>
>>> The 2 blocking issues 123723 and 12676 seems to have the same testing
>>> project issue tracked in the b/195313999
>>> <https://buganizer.corp.google.com/195313999> I am not waiting on the
>>> fix for this issue as this is only a test configuration issue.
>>>
>>> I am in the process of promoting RC1 for validation which should be out
>>> in another hour.
>>>
>>> PR https://github.com/apache/beam/pull/15237 doesn't fix a regression
>>> so it's not a blocker. I will pick it up if we endup creating a new RC.
>>>
>>> On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <lc...@google.com> wrote:
>>>
>>>> Buquian doesn't seem to have a JIRA account to reassign it
>>>> appropriately. Buquian can you create one and provide your JIRA user name?
>>>>
>>>> Slava you are a contributor in JIRA so I believe you should be able to
>>>> reassign the issue. Were you logged into JIRA?
>>>>
>>>> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com>
>>>> wrote:
>>>>
>>>>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is
>>>>> assigned to me by mistake. I dont have permissions to change the issue
>>>>> though. Buquian has a solution for that issue.
>>>>>
>>>>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
>>>>>
>>>>>> The remaining open issues are all related to the test failures in the
>>>>>> apache-beam-testing project due to b/195313999
>>>>>> <https://buganizer.corp.google.com/195313999>. This is also
>>>>>> impacting out precommits for open PRs making it difficult for the Apache
>>>>>> Beam community to get a green signal before merging code so code is being
>>>>>> merged with assumptions that the failure is due to the streaming issue.
>>>>>>
>>>>>> Ahmet, I added you to the thread that has more details as well in
>>>>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>>>>>
>>>>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I'd like to request that we also include a cherry-pick for
>>>>>>> https://github.com/apache/beam/pull/15237
>>>>>>>
>>>>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com> wrote:
>>>>>>>
>>>>>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a
>>>>>>>> key negotiation error between the worker and streaming engine failing so no
>>>>>>>> work is done causing the job to fail.
>>>>>>>>
>>>>>>>> Kiley has a comment that it seems as though this is a known issue.
>>>>>>>>
>>>>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Ankur, how is the release coming along?
>>>>>>>>>
>>>>>>>>> I noticed there are 2 open blockers:
>>>>>>>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could
>>>>>>>>> you check with Slava, he may not be aware that this is a release blocker. (
>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>>>>>> Cwik <lc...@google.com> ?) (
>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>>>>>
>>>>>>>>> Ahmet
>>>>>>>>>
>>>>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> I noticed that we seems to have two branches for this release:
>>>>>>>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32)
>>>>>>>>>> and "release-2.32.0” (
>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>>>>>
>>>>>>>>>> Is it intended or not? Would it better to keep only one to avoid
>>>>>>>>>> a confusion?
>>>>>>>>>>
>>>>>>>>>> —
>>>>>>>>>> Alexey
>>>>>>>>>>
>>>>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi All,
>>>>>>>>>>
>>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>>
>>>>>>>>>> If there are no objections then I would like to nominate myself
>>>>>>>>>> to do this release.
>>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period
>>>>>>>>>> of time.
>>>>>>>>>> Please review your bug list and mark the blockers as blocker for
>>>>>>>>>> the release and move non blockers to the next release by July 14th.
>>>>>>>>>>
>>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Ankur
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>> --
>>>>> Thanks,
>>>>> - Slava Chernyak
>>>>>
>>>>
>
> --
>
>
> Sayat Satybaldyev
>
> Cruise
>
>
> *Confidentiality Note:* We care about protecting our proprietary
> information, confidential material, and trade secrets. This message may
> contain some or all of those things. Cruise will suffer material harm if
> anyone other than the intended recipient disseminates or takes any action
> based on this message. If you have received this message (including any
> attachments) in error, please delete it immediately and notify the sender
> promptly.
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Sayat Satybaldiyev <sa...@getcruise.com>.
Hello Ankur,
I am wondering would you consider having commits from this PRs in the
release if I make cherry-picks commits to resolve the issue with BQ write
connector?
https://github.com/apache/beam/pull/15237
https://github.com/apache/beam/pull/15352
On Mon, Aug 16, 2021 at 9:59 AM Ankur Goenka <go...@google.com> wrote:
> The issue regarding Dataflow Validation is resolved. Will do the
> validation and post RC1 for voting once the validation is done.
>
> On Tue, Aug 10, 2021 at 9:22 PM Ankur Goenka <go...@google.com> wrote:
>
>> For the release branch release-2.32.0
>> <https://github.com/apache/beam/tree/release-2.32.0> is the right one. I
>> think 2.32 was created by mistake somewhere along the way.
>>
>> The 2 blocking issues 123723 and 12676 seems to have the same testing
>> project issue tracked in the b/195313999
>> <https://buganizer.corp.google.com/195313999> I am not waiting on the
>> fix for this issue as this is only a test configuration issue.
>>
>> I am in the process of promoting RC1 for validation which should be out
>> in another hour.
>>
>> PR https://github.com/apache/beam/pull/15237 doesn't fix a regression so
>> it's not a blocker. I will pick it up if we endup creating a new RC.
>>
>> On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <lc...@google.com> wrote:
>>
>>> Buquian doesn't seem to have a JIRA account to reassign it
>>> appropriately. Buquian can you create one and provide your JIRA user name?
>>>
>>> Slava you are a contributor in JIRA so I believe you should be able to
>>> reassign the issue. Were you logged into JIRA?
>>>
>>> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com>
>>> wrote:
>>>
>>>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is
>>>> assigned to me by mistake. I dont have permissions to change the issue
>>>> though. Buquian has a solution for that issue.
>>>>
>>>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
>>>>
>>>>> The remaining open issues are all related to the test failures in the
>>>>> apache-beam-testing project due to b/195313999
>>>>> <https://buganizer.corp.google.com/195313999>. This is also impacting
>>>>> out precommits for open PRs making it difficult for the Apache Beam
>>>>> community to get a green signal before merging code so code is being merged
>>>>> with assumptions that the failure is due to the streaming issue.
>>>>>
>>>>> Ahmet, I added you to the thread that has more details as well in
>>>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>>>>
>>>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com>
>>>>> wrote:
>>>>>
>>>>>> I'd like to request that we also include a cherry-pick for
>>>>>> https://github.com/apache/beam/pull/15237
>>>>>>
>>>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com> wrote:
>>>>>>
>>>>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>>>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a
>>>>>>> key negotiation error between the worker and streaming engine failing so no
>>>>>>> work is done causing the job to fail.
>>>>>>>
>>>>>>> Kiley has a comment that it seems as though this is a known issue.
>>>>>>>
>>>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Ankur, how is the release coming along?
>>>>>>>>
>>>>>>>> I noticed there are 2 open blockers:
>>>>>>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could
>>>>>>>> you check with Slava, he may not be aware that this is a release blocker. (
>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>>>>> Cwik <lc...@google.com> ?) (
>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>>>>
>>>>>>>> Ahmet
>>>>>>>>
>>>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> I noticed that we seems to have two branches for this release:
>>>>>>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32)
>>>>>>>>> and "release-2.32.0” (
>>>>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>>>>
>>>>>>>>> Is it intended or not? Would it better to keep only one to avoid a
>>>>>>>>> confusion?
>>>>>>>>>
>>>>>>>>> —
>>>>>>>>> Alexey
>>>>>>>>>
>>>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>
>>>>>>>>> If there are no objections then I would like to nominate myself to
>>>>>>>>> do this release.
>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period
>>>>>>>>> of time.
>>>>>>>>> Please review your bug list and mark the blockers as blocker for
>>>>>>>>> the release and move non blockers to the next release by July 14th.
>>>>>>>>>
>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Ankur
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>> --
>>>> Thanks,
>>>> - Slava Chernyak
>>>>
>>>
--
Sayat Satybaldyev
Cruise
--
*Confidentiality Note:* We care about protecting our proprietary
information, confidential material, and trade secrets. This message may
contain some or all of those things. Cruise will suffer material harm if
anyone other than the intended recipient disseminates or takes any action
based on this message. If you have received this message (including any
attachments) in error, please delete it immediately and notify the sender
promptly.
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
The issue regarding Dataflow Validation is resolved. Will do the validation
and post RC1 for voting once the validation is done.
On Tue, Aug 10, 2021 at 9:22 PM Ankur Goenka <go...@google.com> wrote:
> For the release branch release-2.32.0
> <https://github.com/apache/beam/tree/release-2.32.0> is the right one. I
> think 2.32 was created by mistake somewhere along the way.
>
> The 2 blocking issues 123723 and 12676 seems to have the same testing
> project issue tracked in the b/195313999
> <https://buganizer.corp.google.com/195313999> I am not waiting on the fix
> for this issue as this is only a test configuration issue.
>
> I am in the process of promoting RC1 for validation which should be out in
> another hour.
>
> PR https://github.com/apache/beam/pull/15237 doesn't fix a regression so
> it's not a blocker. I will pick it up if we endup creating a new RC.
>
> On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <lc...@google.com> wrote:
>
>> Buquian doesn't seem to have a JIRA account to reassign it appropriately.
>> Buquian can you create one and provide your JIRA user name?
>>
>> Slava you are a contributor in JIRA so I believe you should be able to
>> reassign the issue. Were you logged into JIRA?
>>
>> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com>
>> wrote:
>>
>>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is
>>> assigned to me by mistake. I dont have permissions to change the issue
>>> though. Buquian has a solution for that issue.
>>>
>>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
>>>
>>>> The remaining open issues are all related to the test failures in the
>>>> apache-beam-testing project due to b/195313999
>>>> <https://buganizer.corp.google.com/195313999>. This is also impacting
>>>> out precommits for open PRs making it difficult for the Apache Beam
>>>> community to get a green signal before merging code so code is being merged
>>>> with assumptions that the failure is due to the streaming issue.
>>>>
>>>> Ahmet, I added you to the thread that has more details as well in
>>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>>>
>>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com>
>>>> wrote:
>>>>
>>>>> I'd like to request that we also include a cherry-pick for
>>>>> https://github.com/apache/beam/pull/15237
>>>>>
>>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com> wrote:
>>>>>
>>>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a key
>>>>>> negotiation error between the worker and streaming engine failing so no
>>>>>> work is done causing the job to fail.
>>>>>>
>>>>>> Kiley has a comment that it seems as though this is a known issue.
>>>>>>
>>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Ankur, how is the release coming along?
>>>>>>>
>>>>>>> I noticed there are 2 open blockers:
>>>>>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could you
>>>>>>> check with Slava, he may not be aware that this is a release blocker. (
>>>>>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>>>> Cwik <lc...@google.com> ?) (
>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>>>
>>>>>>> Ahmet
>>>>>>>
>>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>>>
>>>>>>>> I noticed that we seems to have two branches for this release:
>>>>>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32)
>>>>>>>> and "release-2.32.0” (
>>>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>>>
>>>>>>>> Is it intended or not? Would it better to keep only one to avoid a
>>>>>>>> confusion?
>>>>>>>>
>>>>>>>> —
>>>>>>>> Alexey
>>>>>>>>
>>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday)
>>>>>>>> and released by Aug 18th according to the release calendar [1].
>>>>>>>>
>>>>>>>> If there are no objections then I would like to nominate myself to
>>>>>>>> do this release.
>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>>>>>> time.
>>>>>>>> Please review your bug list and mark the blockers as blocker for
>>>>>>>> the release and move non blockers to the next release by July 14th.
>>>>>>>>
>>>>>>>> Please let me know if you have any questions.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Ankur
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>
>>> --
>>> Thanks,
>>> - Slava Chernyak
>>>
>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
For the release branch release-2.32.0
<https://github.com/apache/beam/tree/release-2.32.0> is the right one. I
think 2.32 was created by mistake somewhere along the way.
The 2 blocking issues 123723 and 12676 seems to have the same testing
project issue tracked in the b/195313999
<https://buganizer.corp.google.com/195313999> I am not waiting on the fix
for this issue as this is only a test configuration issue.
I am in the process of promoting RC1 for validation which should be out in
another hour.
PR https://github.com/apache/beam/pull/15237 doesn't fix a regression so
it's not a blocker. I will pick it up if we endup creating a new RC.
On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <lc...@google.com> wrote:
> Buquian doesn't seem to have a JIRA account to reassign it appropriately.
> Buquian can you create one and provide your JIRA user name?
>
> Slava you are a contributor in JIRA so I believe you should be able to
> reassign the issue. Were you logged into JIRA?
>
> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com>
> wrote:
>
>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is
>> assigned to me by mistake. I dont have permissions to change the issue
>> though. Buquian has a solution for that issue.
>>
>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
>>
>>> The remaining open issues are all related to the test failures in the
>>> apache-beam-testing project due to b/195313999
>>> <https://buganizer.corp.google.com/195313999>. This is also impacting
>>> out precommits for open PRs making it difficult for the Apache Beam
>>> community to get a green signal before merging code so code is being merged
>>> with assumptions that the failure is due to the streaming issue.
>>>
>>> Ahmet, I added you to the thread that has more details as well in
>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>>
>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com>
>>> wrote:
>>>
>>>> I'd like to request that we also include a cherry-pick for
>>>> https://github.com/apache/beam/pull/15237
>>>>
>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com> wrote:
>>>>
>>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>>
>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a key
>>>>> negotiation error between the worker and streaming engine failing so no
>>>>> work is done causing the job to fail.
>>>>>
>>>>> Kiley has a comment that it seems as though this is a known issue.
>>>>>
>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> Ankur, how is the release coming along?
>>>>>>
>>>>>> I noticed there are 2 open blockers:
>>>>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could you
>>>>>> check with Slava, he may not be aware that this is a release blocker. (
>>>>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>>> Cwik <lc...@google.com> ?) (
>>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>>
>>>>>> Ahmet
>>>>>>
>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>>
>>>>>>> I noticed that we seems to have two branches for this release:
>>>>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32)
>>>>>>> and "release-2.32.0” (
>>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>>
>>>>>>> Is it intended or not? Would it better to keep only one to avoid a
>>>>>>> confusion?
>>>>>>>
>>>>>>> —
>>>>>>> Alexey
>>>>>>>
>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday)
>>>>>>> and released by Aug 18th according to the release calendar [1].
>>>>>>>
>>>>>>> If there are no objections then I would like to nominate myself to
>>>>>>> do this release.
>>>>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>>>>> time.
>>>>>>> Please review your bug list and mark the blockers as blocker for the
>>>>>>> release and move non blockers to the next release by July 14th.
>>>>>>>
>>>>>>> Please let me know if you have any questions.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ankur
>>>>>>>
>>>>>>> [1]
>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>
>>>>>>>
>>>>>>>
>>
>> --
>> Thanks,
>> - Slava Chernyak
>>
>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Luke Cwik <lc...@google.com>.
Buquian doesn't seem to have a JIRA account to reassign it appropriately.
Buquian can you create one and provide your JIRA user name?
Slava you are a contributor in JIRA so I believe you should be able to
reassign the issue. Were you logged into JIRA?
On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <ch...@google.com> wrote:
> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is
> assigned to me by mistake. I dont have permissions to change the issue
> though. Buquian has a solution for that issue.
>
> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
>
>> The remaining open issues are all related to the test failures in the
>> apache-beam-testing project due to b/195313999
>> <https://buganizer.corp.google.com/195313999>. This is also impacting
>> out precommits for open PRs making it difficult for the Apache Beam
>> community to get a green signal before merging code so code is being merged
>> with assumptions that the failure is due to the streaming issue.
>>
>> Ahmet, I added you to the thread that has more details as well in
>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>>
>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com>
>> wrote:
>>
>>> I'd like to request that we also include a cherry-pick for
>>> https://github.com/apache/beam/pull/15237
>>>
>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com> wrote:
>>>
>>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>>
>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a key
>>>> negotiation error between the worker and streaming engine failing so no
>>>> work is done causing the job to fail.
>>>>
>>>> Kiley has a comment that it seems as though this is a known issue.
>>>>
>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Ankur, how is the release coming along?
>>>>>
>>>>> I noticed there are 2 open blockers:
>>>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could you
>>>>> check with Slava, he may not be aware that this is a release blocker. (
>>>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz
>>>>> Cwik <lc...@google.com> ?) (
>>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>>
>>>>> Ahmet
>>>>>
>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>>> aromanenko.dev@gmail.com> wrote:
>>>>>
>>>>>> I noticed that we seems to have two branches for this release:
>>>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32)
>>>>>> and "release-2.32.0” (
>>>>>> https://github.com/apache/beam/tree/release-2.32.0)
>>>>>>
>>>>>> Is it intended or not? Would it better to keep only one to avoid a
>>>>>> confusion?
>>>>>>
>>>>>> —
>>>>>> Alexey
>>>>>>
>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday)
>>>>>> and released by Aug 18th according to the release calendar [1].
>>>>>>
>>>>>> If there are no objections then I would like to nominate myself to do
>>>>>> this release.
>>>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>>>> time.
>>>>>> Please review your bug list and mark the blockers as blocker for the
>>>>>> release and move non blockers to the next release by July 14th.
>>>>>>
>>>>>> Please let me know if you have any questions.
>>>>>>
>>>>>> Thanks,
>>>>>> Ankur
>>>>>>
>>>>>> [1]
>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>
>>>>>>
>>>>>>
>
> --
> Thanks,
> - Slava Chernyak
>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Slava Chernyak <ch...@google.com>.
FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is
assigned to me by mistake. I dont have permissions to change the issue
though. Buquian has a solution for that issue.
On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <lc...@google.com> wrote:
> The remaining open issues are all related to the test failures in the
> apache-beam-testing project due to b/195313999
> <https://buganizer.corp.google.com/195313999>. This is also impacting out
> precommits for open PRs making it difficult for the Apache Beam community
> to get a green signal before merging code so code is being merged with
> assumptions that the failure is due to the streaming issue.
>
> Ahmet, I added you to the thread that has more details as well in
> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
>
> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com> wrote:
>
>> I'd like to request that we also include a cherry-pick for
>> https://github.com/apache/beam/pull/15237
>>
>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com> wrote:
>>
>>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>>
>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a key
>>> negotiation error between the worker and streaming engine failing so no
>>> work is done causing the job to fail.
>>>
>>> Kiley has a comment that it seems as though this is a known issue.
>>>
>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Ankur, how is the release coming along?
>>>>
>>>> I noticed there are 2 open blockers:
>>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could you
>>>> check with Slava, he may not be aware that this is a release blocker. (
>>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>>> - One unassigned. Could you find someone who could help? ( @Lukasz Cwik
>>>> <lc...@google.com> ?) (
>>>> https://issues.apache.org/jira/browse/BEAM-12723)
>>>>
>>>> Ahmet
>>>>
>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>>> aromanenko.dev@gmail.com> wrote:
>>>>
>>>>> I noticed that we seems to have two branches for this release:
>>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32) and
>>>>> "release-2.32.0” (https://github.com/apache/beam/tree/release-2.32.0)
>>>>>
>>>>> Is it intended or not? Would it better to keep only one to avoid a
>>>>> confusion?
>>>>>
>>>>> —
>>>>> Alexey
>>>>>
>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>>>
>>>>> Hi All,
>>>>>
>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday)
>>>>> and released by Aug 18th according to the release calendar [1].
>>>>>
>>>>> If there are no objections then I would like to nominate myself to do
>>>>> this release.
>>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>>> time.
>>>>> Please review your bug list and mark the blockers as blocker for the
>>>>> release and move non blockers to the next release by July 14th.
>>>>>
>>>>> Please let me know if you have any questions.
>>>>>
>>>>> Thanks,
>>>>> Ankur
>>>>>
>>>>> [1]
>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>
>>>>>
>>>>>
--
Thanks,
- Slava Chernyak
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Luke Cwik <lc...@google.com>.
The remaining open issues are all related to the test failures in the
apache-beam-testing project due to b/195313999. This is also impacting out
precommits for open PRs making it difficult for the Apache Beam community
to get a green signal before merging code so code is being merged with
assumptions that the failure is due to the streaming issue.
Ahmet, I added you to the thread that has more details as well in
https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc
On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <pa...@google.com> wrote:
> I'd like to request that we also include a cherry-pick for
> https://github.com/apache/beam/pull/15237
>
> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com> wrote:
>
>> +Kiley Sok <ki...@google.com> as previous plat-mon.
>>
>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a key
>> negotiation error between the worker and streaming engine failing so no
>> work is done causing the job to fail.
>>
>> Kiley has a comment that it seems as though this is a known issue.
>>
>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com> wrote:
>>
>>> Ankur, how is the release coming along?
>>>
>>> I noticed there are 2 open blockers:
>>> - One assigned to @Slava Chernyak <ch...@google.com> - Could you
>>> check with Slava, he may not be aware that this is a release blocker. (
>>> https://issues.apache.org/jira/browse/BEAM-12676)
>>> - One unassigned. Could you find someone who could help? ( @Lukasz Cwik
>>> <lc...@google.com> ?) (https://issues.apache.org/jira/browse/BEAM-12723
>>> )
>>>
>>> Ahmet
>>>
>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <
>>> aromanenko.dev@gmail.com> wrote:
>>>
>>>> I noticed that we seems to have two branches for this release:
>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32) and
>>>> "release-2.32.0” (https://github.com/apache/beam/tree/release-2.32.0)
>>>>
>>>> Is it intended or not? Would it better to keep only one to avoid a
>>>> confusion?
>>>>
>>>> —
>>>> Alexey
>>>>
>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>>
>>>> Hi All,
>>>>
>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
>>>> released by Aug 18th according to the release calendar [1].
>>>>
>>>> If there are no objections then I would like to nominate myself to do
>>>> this release.
>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>> time.
>>>> Please review your bug list and mark the blockers as blocker for the
>>>> release and move non blockers to the next release by July 14th.
>>>>
>>>> Please let me know if you have any questions.
>>>>
>>>> Thanks,
>>>> Ankur
>>>>
>>>> [1]
>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>
>>>>
>>>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Pablo Estrada <pa...@google.com>.
I'd like to request that we also include a cherry-pick for
https://github.com/apache/beam/pull/15237
On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <lc...@google.com> wrote:
> +Kiley Sok <ki...@google.com> as previous plat-mon.
>
> https://issues.apache.org/jira/browse/BEAM-12723 is the same as
> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a key
> negotiation error between the worker and streaming engine failing so no
> work is done causing the job to fail.
>
> Kiley has a comment that it seems as though this is a known issue.
>
> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com> wrote:
>
>> Ankur, how is the release coming along?
>>
>> I noticed there are 2 open blockers:
>> - One assigned to @Slava Chernyak <ch...@google.com> - Could you
>> check with Slava, he may not be aware that this is a release blocker. (
>> https://issues.apache.org/jira/browse/BEAM-12676)
>> - One unassigned. Could you find someone who could help? ( @Lukasz Cwik
>> <lc...@google.com> ?) (https://issues.apache.org/jira/browse/BEAM-12723)
>>
>> Ahmet
>>
>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <ar...@gmail.com>
>> wrote:
>>
>>> I noticed that we seems to have two branches for this release:
>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32) and
>>> "release-2.32.0” (https://github.com/apache/beam/tree/release-2.32.0)
>>>
>>> Is it intended or not? Would it better to keep only one to avoid a
>>> confusion?
>>>
>>> —
>>> Alexey
>>>
>>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>>
>>> Hi All,
>>>
>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
>>> released by Aug 18th according to the release calendar [1].
>>>
>>> If there are no objections then I would like to nominate myself to do
>>> this release.
>>> Sorry for the shorter notice as I was OOO for an extended period of time.
>>> Please review your bug list and mark the blockers as blocker for the
>>> release and move non blockers to the next release by July 14th.
>>>
>>> Please let me know if you have any questions.
>>>
>>> Thanks,
>>> Ankur
>>>
>>> [1]
>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>
>>>
>>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Luke Cwik <lc...@google.com>.
+Kiley Sok <ki...@google.com> as previous plat-mon.
https://issues.apache.org/jira/browse/BEAM-12723 is the same as
https://issues.apache.org/jira/browse/BEAM-12699 and is due to a key
negotiation error between the worker and streaming engine failing so no
work is done causing the job to fail.
Kiley has a comment that it seems as though this is a known issue.
On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <al...@google.com> wrote:
> Ankur, how is the release coming along?
>
> I noticed there are 2 open blockers:
> - One assigned to @Slava Chernyak <ch...@google.com> - Could you check
> with Slava, he may not be aware that this is a release blocker. (
> https://issues.apache.org/jira/browse/BEAM-12676)
> - One unassigned. Could you find someone who could help? ( @Lukasz Cwik
> <lc...@google.com> ?) (https://issues.apache.org/jira/browse/BEAM-12723)
>
> Ahmet
>
> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <ar...@gmail.com>
> wrote:
>
>> I noticed that we seems to have two branches for this release:
>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32) and
>> "release-2.32.0” (https://github.com/apache/beam/tree/release-2.32.0)
>>
>> Is it intended or not? Would it better to keep only one to avoid a
>> confusion?
>>
>> —
>> Alexey
>>
>> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>>
>> Hi All,
>>
>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
>> released by Aug 18th according to the release calendar [1].
>>
>> If there are no objections then I would like to nominate myself to do
>> this release.
>> Sorry for the shorter notice as I was OOO for an extended period of time.
>> Please review your bug list and mark the blockers as blocker for the
>> release and move non blockers to the next release by July 14th.
>>
>> Please let me know if you have any questions.
>>
>> Thanks,
>> Ankur
>>
>> [1]
>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>
>>
>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ahmet Altay <al...@google.com>.
Ankur, how is the release coming along?
I noticed there are 2 open blockers:
- One assigned to @Slava Chernyak <ch...@google.com> - Could you check
with Slava, he may not be aware that this is a release blocker. (
https://issues.apache.org/jira/browse/BEAM-12676)
- One unassigned. Could you find someone who could help? ( @Lukasz Cwik
<lc...@google.com> ?) (https://issues.apache.org/jira/browse/BEAM-12723)
Ahmet
On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko <ar...@gmail.com>
wrote:
> I noticed that we seems to have two branches for this release:
> "release-2.32" (https://github.com/apache/beam/tree/release-2.32) and
> "release-2.32.0” (https://github.com/apache/beam/tree/release-2.32.0)
>
> Is it intended or not? Would it better to keep only one to avoid a
> confusion?
>
> —
> Alexey
>
> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>
> Hi All,
>
> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
> released by Aug 18th according to the release calendar [1].
>
> If there are no objections then I would like to nominate myself to do this
> release.
> Sorry for the shorter notice as I was OOO for an extended period of time.
> Please review your bug list and mark the blockers as blocker for the
> release and move non blockers to the next release by July 14th.
>
> Please let me know if you have any questions.
>
> Thanks,
> Ankur
>
> [1]
> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>
>
>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Alexey Romanenko <ar...@gmail.com>.
I noticed that we seems to have two branches for this release:
"release-2.32" (https://github.com/apache/beam/tree/release-2.32) and "release-2.32.0” (https://github.com/apache/beam/tree/release-2.32.0)
Is it intended or not? Would it better to keep only one to avoid a confusion?
—
Alexey
> On 7 Jul 2021, at 18:20, Ankur Goenka <go...@google.com> wrote:
>
> Hi All,
>
> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and released by Aug 18th according to the release calendar [1].
>
> If there are no objections then I would like to nominate myself to do this release.
> Sorry for the shorter notice as I was OOO for an extended period of time.
> Please review your bug list and mark the blockers as blocker for the release and move non blockers to the next release by July 14th.
>
> Please let me know if you have any questions.
>
> Thanks,
> Ankur
>
> [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles <https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles>
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
Update:
We currently have 4 issue and 3 of which are blocking
https://issues.apache.org/jira/browse/BEAM-12726?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Triage%20Needed%22)%20AND%20priority%20in%20(P0%2C%20P1)%20AND%20fixVersion%20%3D%202.32.0
On Mon, Aug 2, 2021 at 5:24 PM Ankur Goenka <go...@google.com> wrote:
> Thanks for the pointer. I think it will not be a blocker for 2.32 as it
> was already broken in 2.30
> However, if we have a fix which we can apply before the CR and validation
> then I can cherry pick it.
>
> On Mon, Aug 2, 2021 at 5:22 PM Sayat Satybaldiyev <
> sayat.satybaldiyev@getcruise.com> wrote:
>
>> Could I also mention that there's a bug in write to bigquery component?
>> https://github.com/apache/beam/pull/15237 This blocked us to upgrade to
>> 2.30 version.
>>
>> On Mon, Aug 2, 2021 at 4:00 PM Ankur Goenka <go...@google.com> wrote:
>>
>>> Hi,
>>>
>>> We still have 4 open bugs listed here
>>> <https://issues.apache.org/jira/browse/BEAM-12678?jql=project%20%3D%20BEAM%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.32.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC>
>>> .
>>> I should be able to publish an RC once these are resolved.
>>>
>>> Thanks,
>>> Ankur
>>>
>>> On Mon, Aug 2, 2021 at 3:41 PM Pablo Estrada <pa...@google.com> wrote:
>>>
>>>> +Ankur Goenka <go...@google.com> - any updates on the release?
>>>> Thanks!
>>>>
>>>> On Fri, Jul 23, 2021 at 11:08 AM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> How is the release going on? Are there any blockers left on the
>>>>> burndown list?
>>>>>
>>>>> On Wed, Jul 14, 2021 at 11:53 AM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 14, 2021 at 11:28 AM Ankur Goenka <go...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Please create 2.33.0 Release tag so that we can move the open bugs
>>>>>>> to the next release.
>>>>>>>
>>>>>>
>>>>>> Done.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> On Wed, Jul 14, 2021 at 9:48 AM Kenneth Knowles <ke...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Here's the burndown list, for easy reference:
>>>>>>>> https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>>>>>>>>
>>>>>>>> Kenn
>>>>>>>>
>>>>>>>> On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> Just a friendly reminder that 2.32 will be cut on Wednesday.
>>>>>>>>> Please move non blockers to the next release.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Ankur
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Sounds good and thank you, Ankur!
>>>>>>>>>>
>>>>>>>>>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi All,
>>>>>>>>>>>
>>>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>>>
>>>>>>>>>>> If there are no objections then I would like to nominate myself
>>>>>>>>>>> to do this release.
>>>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period
>>>>>>>>>>> of time.
>>>>>>>>>>> Please review your bug list and mark the blockers as blocker for
>>>>>>>>>>> the release and move non blockers to the next release by July 14th.
>>>>>>>>>>>
>>>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Ankur
>>>>>>>>>>>
>>>>>>>>>>> [1]
>>>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>>>
>>>>>>>>>>
>>
>> --
>>
>>
>> Sayat Satybald
>>
>> Senior Software Engineer
>>
>> Cruise
>>
>>
>> *Confidentiality Note:* We care about protecting our proprietary
>> information, confidential material, and trade secrets. This message may
>> contain some or all of those things. Cruise will suffer material harm if
>> anyone other than the intended recipient disseminates or takes any action
>> based on this message. If you have received this message (including any
>> attachments) in error, please delete it immediately and notify the sender
>> promptly.
>
>
Re: [EXT] Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
Hi Sayat,
Please create a cherrypick PR and if the tests pass then I can merge it.
Thanks,
Ankur
On Tue, Aug 3, 2021 at 10:38 AM Sayat Satybaldiyev <
sayat.satybaldiyev@getcruise.com> wrote:
> Hello Ankur,
>
> Thank you to @Pablo Estrada <pa...@google.com>. He has reviewed and
> approved PR. I've validated the fix on our pipelines. The PR fixes the
> issue with running on a larger scale. I would highly appreciate if it would
> be possible to include the commit into the 2.32 version.
>
>
>
>
> *Confidentiality Note:* We care about protecting our proprietary
> information, confidential material, and trade secrets. This message may
> contain some or all of those things. Cruise will suffer material harm if
> anyone other than the intended recipient disseminates or takes any action
> based on this message. If you have received this message (including any
> attachments) in error, please delete it immediately and notify the sender
> promptly.
Re: [EXT] Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Sayat Satybaldiyev <sa...@getcruise.com>.
Hello Ankur,
Thank you to @Pablo Estrada <pa...@google.com>. He has reviewed and
approved PR. I've validated the fix on our pipelines. The PR fixes the
issue with running on a larger scale. I would highly appreciate if it would
be possible to include the commit into the 2.32 version.
--
*Confidentiality Note:* We care about protecting our proprietary
information, confidential material, and trade secrets. This message may
contain some or all of those things. Cruise will suffer material harm if
anyone other than the intended recipient disseminates or takes any action
based on this message. If you have received this message (including any
attachments) in error, please delete it immediately and notify the sender
promptly.
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
Thanks for the pointer. I think it will not be a blocker for 2.32 as it was
already broken in 2.30
However, if we have a fix which we can apply before the CR and validation
then I can cherry pick it.
On Mon, Aug 2, 2021 at 5:22 PM Sayat Satybaldiyev <
sayat.satybaldiyev@getcruise.com> wrote:
> Could I also mention that there's a bug in write to bigquery component?
> https://github.com/apache/beam/pull/15237 This blocked us to upgrade to
> 2.30 version.
>
> On Mon, Aug 2, 2021 at 4:00 PM Ankur Goenka <go...@google.com> wrote:
>
>> Hi,
>>
>> We still have 4 open bugs listed here
>> <https://issues.apache.org/jira/browse/BEAM-12678?jql=project%20%3D%20BEAM%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.32.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC>
>> .
>> I should be able to publish an RC once these are resolved.
>>
>> Thanks,
>> Ankur
>>
>> On Mon, Aug 2, 2021 at 3:41 PM Pablo Estrada <pa...@google.com> wrote:
>>
>>> +Ankur Goenka <go...@google.com> - any updates on the release?
>>> Thanks!
>>>
>>> On Fri, Jul 23, 2021 at 11:08 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> How is the release going on? Are there any blockers left on the
>>>> burndown list?
>>>>
>>>> On Wed, Jul 14, 2021 at 11:53 AM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Jul 14, 2021 at 11:28 AM Ankur Goenka <go...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Please create 2.33.0 Release tag so that we can move the open bugs to
>>>>>> the next release.
>>>>>>
>>>>>
>>>>> Done.
>>>>>
>>>>>
>>>>>>
>>>>>> On Wed, Jul 14, 2021 at 9:48 AM Kenneth Knowles <ke...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Here's the burndown list, for easy reference:
>>>>>>> https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>>>>>>>
>>>>>>> Kenn
>>>>>>>
>>>>>>> On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> Just a friendly reminder that 2.32 will be cut on Wednesday. Please
>>>>>>>> move non blockers to the next release.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Ankur
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Sounds good and thank you, Ankur!
>>>>>>>>>
>>>>>>>>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi All,
>>>>>>>>>>
>>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>>
>>>>>>>>>> If there are no objections then I would like to nominate myself
>>>>>>>>>> to do this release.
>>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period
>>>>>>>>>> of time.
>>>>>>>>>> Please review your bug list and mark the blockers as blocker for
>>>>>>>>>> the release and move non blockers to the next release by July 14th.
>>>>>>>>>>
>>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Ankur
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>>
>>>>>>>>>
>
> --
>
>
> Sayat Satybald
>
> Senior Software Engineer
>
> Cruise
>
>
> *Confidentiality Note:* We care about protecting our proprietary
> information, confidential material, and trade secrets. This message may
> contain some or all of those things. Cruise will suffer material harm if
> anyone other than the intended recipient disseminates or takes any action
> based on this message. If you have received this message (including any
> attachments) in error, please delete it immediately and notify the sender
> promptly.
Re: [EXT] Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Sayat Satybaldiyev <sa...@getcruise.com>.
Could I also mention that there's a bug in write to bigquery component?
https://github.com/apache/beam/pull/15237 This blocked us to upgrade to
2.30 version.
On Mon, Aug 2, 2021 at 4:00 PM Ankur Goenka <go...@google.com> wrote:
> Hi,
>
> We still have 4 open bugs listed here
> <https://issues.apache.org/jira/browse/BEAM-12678?jql=project%20%3D%20BEAM%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.32.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC>
> .
> I should be able to publish an RC once these are resolved.
>
> Thanks,
> Ankur
>
> On Mon, Aug 2, 2021 at 3:41 PM Pablo Estrada <pa...@google.com> wrote:
>
>> +Ankur Goenka <go...@google.com> - any updates on the release?
>> Thanks!
>>
>> On Fri, Jul 23, 2021 at 11:08 AM Ahmet Altay <al...@google.com> wrote:
>>
>>> How is the release going on? Are there any blockers left on the burndown
>>> list?
>>>
>>> On Wed, Jul 14, 2021 at 11:53 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Jul 14, 2021 at 11:28 AM Ankur Goenka <go...@google.com>
>>>> wrote:
>>>>
>>>>> Please create 2.33.0 Release tag so that we can move the open bugs to
>>>>> the next release.
>>>>>
>>>>
>>>> Done.
>>>>
>>>>
>>>>>
>>>>> On Wed, Jul 14, 2021 at 9:48 AM Kenneth Knowles <ke...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Here's the burndown list, for easy reference:
>>>>>> https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>>>>>>
>>>>>> Kenn
>>>>>>
>>>>>> On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Just a friendly reminder that 2.32 will be cut on Wednesday. Please
>>>>>>> move non blockers to the next release.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ankur
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Sounds good and thank you, Ankur!
>>>>>>>>
>>>>>>>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th
>>>>>>>>> (Wednesday) and released by Aug 18th according to the release calendar [1].
>>>>>>>>>
>>>>>>>>> If there are no objections then I would like to nominate myself to
>>>>>>>>> do this release.
>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period
>>>>>>>>> of time.
>>>>>>>>> Please review your bug list and mark the blockers as blocker for
>>>>>>>>> the release and move non blockers to the next release by July 14th.
>>>>>>>>>
>>>>>>>>> Please let me know if you have any questions.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Ankur
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>
>>>>>>>>
--
Sayat Satybald
Senior Software Engineer
Cruise
--
*Confidentiality Note:* We care about protecting our proprietary
information, confidential material, and trade secrets. This message may
contain some or all of those things. Cruise will suffer material harm if
anyone other than the intended recipient disseminates or takes any action
based on this message. If you have received this message (including any
attachments) in error, please delete it immediately and notify the sender
promptly.
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
Hi,
We still have 4 open bugs listed here
<https://issues.apache.org/jira/browse/BEAM-12678?jql=project%20%3D%20BEAM%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.32.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC>
.
I should be able to publish an RC once these are resolved.
Thanks,
Ankur
On Mon, Aug 2, 2021 at 3:41 PM Pablo Estrada <pa...@google.com> wrote:
> +Ankur Goenka <go...@google.com> - any updates on the release?
> Thanks!
>
> On Fri, Jul 23, 2021 at 11:08 AM Ahmet Altay <al...@google.com> wrote:
>
>> How is the release going on? Are there any blockers left on the burndown
>> list?
>>
>> On Wed, Jul 14, 2021 at 11:53 AM Ahmet Altay <al...@google.com> wrote:
>>
>>>
>>>
>>> On Wed, Jul 14, 2021 at 11:28 AM Ankur Goenka <go...@google.com> wrote:
>>>
>>>> Please create 2.33.0 Release tag so that we can move the open bugs to
>>>> the next release.
>>>>
>>>
>>> Done.
>>>
>>>
>>>>
>>>> On Wed, Jul 14, 2021 at 9:48 AM Kenneth Knowles <ke...@apache.org>
>>>> wrote:
>>>>
>>>>> Here's the burndown list, for easy reference:
>>>>> https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>>>>>
>>>>> Kenn
>>>>>
>>>>> On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Just a friendly reminder that 2.32 will be cut on Wednesday. Please
>>>>>> move non blockers to the next release.
>>>>>>
>>>>>> Thanks,
>>>>>> Ankur
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com> wrote:
>>>>>>
>>>>>>> Sounds good and thank you, Ankur!
>>>>>>>
>>>>>>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday)
>>>>>>>> and released by Aug 18th according to the release calendar [1].
>>>>>>>>
>>>>>>>> If there are no objections then I would like to nominate myself to
>>>>>>>> do this release.
>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>>>>>> time.
>>>>>>>> Please review your bug list and mark the blockers as blocker for
>>>>>>>> the release and move non blockers to the next release by July 14th.
>>>>>>>>
>>>>>>>> Please let me know if you have any questions.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Ankur
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>
>>>>>>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Pablo Estrada <pa...@google.com>.
+Ankur Goenka <go...@google.com> - any updates on the release?
Thanks!
On Fri, Jul 23, 2021 at 11:08 AM Ahmet Altay <al...@google.com> wrote:
> How is the release going on? Are there any blockers left on the burndown
> list?
>
> On Wed, Jul 14, 2021 at 11:53 AM Ahmet Altay <al...@google.com> wrote:
>
>>
>>
>> On Wed, Jul 14, 2021 at 11:28 AM Ankur Goenka <go...@google.com> wrote:
>>
>>> Please create 2.33.0 Release tag so that we can move the open bugs to
>>> the next release.
>>>
>>
>> Done.
>>
>>
>>>
>>> On Wed, Jul 14, 2021 at 9:48 AM Kenneth Knowles <ke...@apache.org> wrote:
>>>
>>>> Here's the burndown list, for easy reference:
>>>> https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>>>>
>>>> Kenn
>>>>
>>>> On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com>
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Just a friendly reminder that 2.32 will be cut on Wednesday. Please
>>>>> move non blockers to the next release.
>>>>>
>>>>> Thanks,
>>>>> Ankur
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> Sounds good and thank you, Ankur!
>>>>>>
>>>>>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday)
>>>>>>> and released by Aug 18th according to the release calendar [1].
>>>>>>>
>>>>>>> If there are no objections then I would like to nominate myself to
>>>>>>> do this release.
>>>>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>>>>> time.
>>>>>>> Please review your bug list and mark the blockers as blocker for the
>>>>>>> release and move non blockers to the next release by July 14th.
>>>>>>>
>>>>>>> Please let me know if you have any questions.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ankur
>>>>>>>
>>>>>>> [1]
>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>
>>>>>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ahmet Altay <al...@google.com>.
How is the release going on? Are there any blockers left on the burndown
list?
On Wed, Jul 14, 2021 at 11:53 AM Ahmet Altay <al...@google.com> wrote:
>
>
> On Wed, Jul 14, 2021 at 11:28 AM Ankur Goenka <go...@google.com> wrote:
>
>> Please create 2.33.0 Release tag so that we can move the open bugs to the
>> next release.
>>
>
> Done.
>
>
>>
>> On Wed, Jul 14, 2021 at 9:48 AM Kenneth Knowles <ke...@apache.org> wrote:
>>
>>> Here's the burndown list, for easy reference:
>>> https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>>>
>>> Kenn
>>>
>>> On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Just a friendly reminder that 2.32 will be cut on Wednesday. Please
>>>> move non blockers to the next release.
>>>>
>>>> Thanks,
>>>> Ankur
>>>>
>>>>
>>>>
>>>> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Sounds good and thank you, Ankur!
>>>>>
>>>>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday)
>>>>>> and released by Aug 18th according to the release calendar [1].
>>>>>>
>>>>>> If there are no objections then I would like to nominate myself to do
>>>>>> this release.
>>>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>>>> time.
>>>>>> Please review your bug list and mark the blockers as blocker for the
>>>>>> release and move non blockers to the next release by July 14th.
>>>>>>
>>>>>> Please let me know if you have any questions.
>>>>>>
>>>>>> Thanks,
>>>>>> Ankur
>>>>>>
>>>>>> [1]
>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>
>>>>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ahmet Altay <al...@google.com>.
On Wed, Jul 14, 2021 at 11:28 AM Ankur Goenka <go...@google.com> wrote:
> Please create 2.33.0 Release tag so that we can move the open bugs to the
> next release.
>
Done.
>
> On Wed, Jul 14, 2021 at 9:48 AM Kenneth Knowles <ke...@apache.org> wrote:
>
>> Here's the burndown list, for easy reference:
>> https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>>
>> Kenn
>>
>> On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com> wrote:
>>
>>> Hi All,
>>>
>>> Just a friendly reminder that 2.32 will be cut on Wednesday. Please move
>>> non blockers to the next release.
>>>
>>> Thanks,
>>> Ankur
>>>
>>>
>>>
>>> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Sounds good and thank you, Ankur!
>>>>
>>>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday)
>>>>> and released by Aug 18th according to the release calendar [1].
>>>>>
>>>>> If there are no objections then I would like to nominate myself to do
>>>>> this release.
>>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>>> time.
>>>>> Please review your bug list and mark the blockers as blocker for the
>>>>> release and move non blockers to the next release by July 14th.
>>>>>
>>>>> Please let me know if you have any questions.
>>>>>
>>>>> Thanks,
>>>>> Ankur
>>>>>
>>>>> [1]
>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>
>>>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
Please create 2.33.0 Release tag so that we can move the open bugs to the
next release.
On Wed, Jul 14, 2021 at 9:48 AM Kenneth Knowles <ke...@apache.org> wrote:
> Here's the burndown list, for easy reference:
> https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>
> Kenn
>
> On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com> wrote:
>
>> Hi All,
>>
>> Just a friendly reminder that 2.32 will be cut on Wednesday. Please move
>> non blockers to the next release.
>>
>> Thanks,
>> Ankur
>>
>>
>>
>> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com> wrote:
>>
>>> Sounds good and thank you, Ankur!
>>>
>>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
>>>> released by Aug 18th according to the release calendar [1].
>>>>
>>>> If there are no objections then I would like to nominate myself to do
>>>> this release.
>>>> Sorry for the shorter notice as I was OOO for an extended period of
>>>> time.
>>>> Please review your bug list and mark the blockers as blocker for the
>>>> release and move non blockers to the next release by July 14th.
>>>>
>>>> Please let me know if you have any questions.
>>>>
>>>> Thanks,
>>>> Ankur
>>>>
>>>> [1]
>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>>
>>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Kenneth Knowles <ke...@apache.org>.
Here's the burndown list, for easy reference:
https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349992%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
Kenn
On Mon, Jul 12, 2021 at 11:30 PM Ankur Goenka <go...@google.com> wrote:
> Hi All,
>
> Just a friendly reminder that 2.32 will be cut on Wednesday. Please move
> non blockers to the next release.
>
> Thanks,
> Ankur
>
>
>
> On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com> wrote:
>
>> Sounds good and thank you, Ankur!
>>
>> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com> wrote:
>>
>>> Hi All,
>>>
>>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
>>> released by Aug 18th according to the release calendar [1].
>>>
>>> If there are no objections then I would like to nominate myself to do
>>> this release.
>>> Sorry for the shorter notice as I was OOO for an extended period of time.
>>> Please review your bug list and mark the blockers as blocker for the
>>> release and move non blockers to the next release by July 14th.
>>>
>>> Please let me know if you have any questions.
>>>
>>> Thanks,
>>> Ankur
>>>
>>> [1]
>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>>
>>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ankur Goenka <go...@google.com>.
Hi All,
Just a friendly reminder that 2.32 will be cut on Wednesday. Please move
non blockers to the next release.
Thanks,
Ankur
On Wed, Jul 7, 2021 at 11:16 AM Ahmet Altay <al...@google.com> wrote:
> Sounds good and thank you, Ankur!
>
> On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com> wrote:
>
>> Hi All,
>>
>> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
>> released by Aug 18th according to the release calendar [1].
>>
>> If there are no objections then I would like to nominate myself to do
>> this release.
>> Sorry for the shorter notice as I was OOO for an extended period of time.
>> Please review your bug list and mark the blockers as blocker for the
>> release and move non blockers to the next release by July 14th.
>>
>> Please let me know if you have any questions.
>>
>> Thanks,
>> Ankur
>>
>> [1]
>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>>
>
Re: [PROPOSAL] Preparing for Beam 2.32.0 release
Posted by Ahmet Altay <al...@google.com>.
Sounds good and thank you, Ankur!
On Wed, Jul 7, 2021 at 9:21 AM Ankur Goenka <go...@google.com> wrote:
> Hi All,
>
> Beam 2.32.0 release is scheduled to be cut on July 14th (Wednesday) and
> released by Aug 18th according to the release calendar [1].
>
> If there are no objections then I would like to nominate myself to do this
> release.
> Sorry for the shorter notice as I was OOO for an extended period of time.
> Please review your bug list and mark the blockers as blocker for the
> release and move non blockers to the next release by July 14th.
>
> Please let me know if you have any questions.
>
> Thanks,
> Ankur
>
> [1]
> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouanigd0@group.calendar.google.com&ctz=America/Los_Angeles
>