Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-03-23 Thread Ahmet Altay
On Mon, Mar 23, 2020 at 10:45 AM Steve Niemitz wrote: > https://issues.apache.org/jira/browse/BEAM-9557 should also be a blocker > IMO, as it breaks existing pipelines. > +Reuven Lax +Rehman - Could you look at this reported issue? > On Mon, Mar 23, 2020 at 1:17 PM Maximilian Michels wrote:

Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-03-23 Thread Steve Niemitz
https://issues.apache.org/jira/browse/BEAM-9557 should also be a blocker IMO, as it breaks existing pipelines. On Mon, Mar 23, 2020 at 1:17 PM Maximilian Michels wrote: > Just mentioning that we have discovered > https://issues.apache.org/jira/browse/BEAM-9566 and >

Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-03-23 Thread Maximilian Michels
Just mentioning that we have discovered https://issues.apache.org/jira/browse/BEAM-9566 and https://issues.apache.org/jira/browse/BEAM-9573 which are blockers for the release. I'm currently fixing those. PR will be out later today. -Max On 28.02.20 20:11, Rui Wang wrote: > Release branch 2.20.0

Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-02-28 Thread Rui Wang
Release branch 2.20.0 is already cut. Currently there should be only one blocking Jira: https://issues.apache.org/jira/browse/BEAM-9288 But there is a newly added Jira: https://issues.apache.org/jira/browse/BEAM-9322 I will coordinate on those two Jira. -Rui On Thu, Feb 27, 2020 at 3:18

Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-02-27 Thread Rui Wang
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

Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-02-20 Thread Ismaël Mejía
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

Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-02-19 Thread Ahmet Altay
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 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

Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-02-14 Thread Ismaël Mejía
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

Re: [PROPOSAL] Preparing for Beam 2.20.0 release

2020-02-12 Thread Ahmet Altay
+1. Thank you. On Tue, Feb 11, 2020 at 11:01 PM Rui Wang wrote: > Hi all, > > The next (2.20.0) release branch cut is scheduled for 02/26, according to > the calendar > > . > I would like to

[PROPOSAL] Preparing for Beam 2.20.0 release

2020-02-11 Thread Rui Wang
Hi all, The next (2.20.0) release branch cut is scheduled for 02/26, according to the calendar . I would like to volunteer myself to do this release. The plan is to cut the branch on that date,