Yeah, this seems like a critical fix. Please send a cherry-pick. Also
please make sure that this did not break any post-commits after being
merged.

Thanks,
Cham

On Thu, Feb 11, 2021 at 9:40 AM Nir Gazit <nir....@gmail.com> wrote:

> Hey,
> I hope it's not too late but is it possible to Cherry-pick this PR as well:
> https://github.com/apache/beam/pull/13723
>
> It fixes a critical bug <https://issues.apache.org/jira/browse/BEAM-11790>
> that currently prevents the use of S3IO (and probably other IOs) on the
> Python SDK.
>
> Thanks
> Nir
>
> On Wed, Feb 10, 2021 at 1:37 AM Chamikara Jayalath <chamik...@google.com>
> wrote:
>
>> Update:
>> Cherry-picks are in. Validating the release branch here:
>> https://github.com/apache/beam/pull/13941
>> <https://www.google.com/url?q=https://github.com/apache/beam/pull/13941&sa=D&usg=AFQjCNEZvX6UjOGaS3VUh8FSHf_qlBq0JQ>
>>
>> Thanks,
>> Cham
>>
>> On Wed, Feb 3, 2021 at 6:41 PM Chamikara Jayalath <chamik...@google.com>
>> wrote:
>>
>>> Update: we are down to a single blocker and a fix is in review.
>>>
>>> Thanks,
>>> Cham
>>>
>>> On Fri, Jan 29, 2021 at 5:51 PM Chamikara Jayalath <chamik...@google.com>
>>> wrote:
>>>
>>>> Update:
>>>>
>>>> We have two remaining blockers: https://s.apache.org/beam-2.28.0
>>>> -burn-down
>>>> I hope to build the first RC when the blockers are resolved.
>>>>
>>>> Thanks,
>>>> Cham
>>>>
>>>>
>>>> On Wed, Jan 27, 2021 at 12:51 PM Chamikara Jayalath <
>>>> chamik...@google.com> wrote:
>>>>
>>>>> Release branch was cut:
>>>>> https://github.com/apache/beam/tree/release-2.28.0
>>>>>
>>>>> I'll work with owners of current release blocking JIRAs to cherry-pick
>>>>> fixes before building a RC.
>>>>>
>>>>> Thanks,
>>>>> Cham
>>>>>
>>>>> On Mon, Jan 25, 2021 at 5:20 PM Chamikara Jayalath <
>>>>> chamik...@google.com> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I hope to cut the 2.28.0 release branch on 01/27/2021 as scheduled.
>>>>>>
>>>>>> Please see [1] for the current JIRA burn down for Beam 2.28.0 release.
>>>>>>
>>>>>> If you own any issue in that list, please try to resolve them as soon
>>>>>> as possible (or remove from the list if not critical for this release).
>>>>>>
>>>>>> If you find any new issues that require a critical fix in the Beam
>>>>>> 2.28.0 release, please create a JIRA and add to the burn down list by
>>>>>> changing the Fix Version to 2.28.0.
>>>>>>
>>>>>> Thanks,
>>>>>> Cham
>>>>>>
>>>>>> [1] https://s.apache.org/beam-2.28.0-burn-down
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Jan 14, 2021 at 4:41 PM Ankur Goenka <goe...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Cham!
>>>>>>>
>>>>>>> On Thu, Jan 14, 2021 at 12:26 PM Yichi Zhang <zyi...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thank you, Cham!
>>>>>>>>
>>>>>>>> On Wed, Jan 13, 2021 at 12:58 PM Ahmet Altay <al...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thank you Cham!
>>>>>>>>>
>>>>>>>>> On Wed, Jan 13, 2021 at 12:44 PM Rui Wang <ruw...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks Cham for working on this!
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -Rui
>>>>>>>>>>
>>>>>>>>>> On Wed, Jan 13, 2021 at 11:32 AM Kyle Weaver <kcwea...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thanks for stepping up Cham!
>>>>>>>>>>>
>>>>>>>>>>> Remember to mark critical JIRA issues as release blockers
>>>>>>>>>>> everybody!
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Jan 13, 2021 at 11:25 AM Chamikara Jayalath <
>>>>>>>>>>> chamik...@google.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>
>>>>>>>>>>>> Beam 2.28.0 release is scheduled to be cut on January 27th
>>>>>>>>>>>> according to the release calendar [1]
>>>>>>>>>>>>
>>>>>>>>>>>> I'd like to volunteer myself to be the release manager for this
>>>>>>>>>>>> release. I plan on cutting the release branch on the scheduled 
>>>>>>>>>>>> date.
>>>>>>>>>>>>
>>>>>>>>>>>> Any comments or objections ?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Cham
>>>>>>>>>>>>
>>>>>>>>>>>> [1]
>>>>>>>>>>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com&ctz=America/Los_Angeles
>>>>>>>>>>>>
>>>>>>>>>>>

Reply via email to