Hi community, Just fyi:
The 2.20.0 release branch should be cut yesterday (02/26) per schedule. However as our python precommit was broken so I didn't cut the branch. I am closely working with PR [1] owner to fix the python precommit. Once the fix is in, I will cut the release branch immediately. [1]: https://github.com/apache/beam/pull/10982 -Rui On Thu, Feb 20, 2020 at 7:06 AM Ismaël Mejía <ieme...@gmail.com> wrote: > Not yet, up to last check nobody is tackling it, it is still unassigned. > Let's > not forget that the fix of this one requires an extra release of the grpc > vendored dependency (the source of the issue). > > And yes this is a release blocker for the open source runners because > people > tend to package their projects with the respective runners in a jar and > this is > breaking at the moment. > > Kenn changed the priority of BEAM-9252 from Blocker to Critical to follow > the > conventions in [1], and from those definitions 'most critical bugs should > block release'. > > [1] https://beam.apache.org/contribute/jira-priorities/ > > On Thu, Feb 20, 2020 at 3:42 AM Ahmet Altay <al...@google.com> wrote: > >> Curions, was there a resolution on BEAM-9252? Would it be a release >> blocker? >> >> On Fri, Feb 14, 2020 at 12:42 AM Ismaël Mejía <ieme...@gmail.com> wrote: >> >>> Thanks Rui for volunteering and for keeping the release pace! >>> >>> Since we are discussing the next release, I would like to highlight that >>> nobody >>> apparently is working on this blocker issue: >>> >>> BEAM-9252 Problem shading Beam pipeline with Beam 2.20.0-SNAPSHOT >>> https://issues.apache.org/jira/browse/BEAM-9252 >>> >>> This is a regression introduced by the move to vendored gRPC 1.26.0 and >>> it >>> probably will require an extra vendored gRPC release so better to give it >>> some priority. >>> >>> >>> On Wed, Feb 12, 2020 at 6:48 PM Ahmet Altay <al...@google.com> wrote: >>> >>>> +1. Thank you. >>>> >>>> On Tue, Feb 11, 2020 at 11:01 PM Rui Wang <ruw...@google.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> The next (2.20.0) release branch cut is scheduled for 02/26, according >>>>> to the calendar >>>>> <https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com> >>>>> . >>>>> I would like to volunteer myself to do this release. >>>>> The plan is to cut the branch on that date, and cherrypick >>>>> release-blocking >>>>> fixes afterwards if any. >>>>> >>>>> Any unresolved release blocking JIRA issues for 2.20.0 should have >>>>> their "Fix Version/s" marked as "2.20.0". >>>>> >>>>> Any comments or objections? >>>>> >>>>> >>>>> -Rui >>>>> >>>>
