Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-12-10 Thread Ismaël Mejía
Mikhail it seems the SQL module generated pom is broken in 2.17.0. We will probably need to create a new RC. For context https://issues.apache.org/jira/browse/BEAM-8858 and still to confirm https://issues.apache.org/jira/browse/BEAM-8917 Cherry pick PRs coming soon. On Fri, Dec 6, 2019 at 7:04 PM

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-12-06 Thread Mikhail Gryzykhin
UPD: All PRs are merged and tickets are closed. Building RC. --Mikhail On Tue, Nov 26, 2019 at 10:10 AM Mikhail Gryzykhin wrote: > Hello everybody, > > Got release branch green except gradle build that timeout and fails with > go tests that look like flake. > > I'll go over remaining PRs and

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-11-26 Thread Mikhail Gryzykhin
Hello everybody, Got release branch green except gradle build that timeout and fails with go tests that look like flake. I'll go over remaining PRs and Jiras today and do final tests validation. Will start RC process afterwards. --Mikhail On Fri, Nov 22, 2019 at 9:29 PM Jan Lukavský wrote: >

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-11-22 Thread Jan Lukavský
Hi Mikhail,I created PR for [BEAM-8812]. It is linked in the JIRA.JanDne 23. 11. 2019 0:45 napsal uživatel Mikhail Gryzykhin :UPD:on current branch there's timeout on gradle build job, I'm mitigating it by increasing job time. Seems that this job runs most of python tests. We might look into

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-11-22 Thread Valentyn Tymofieiev
https://github.com/apache/beam/pull/10197 will cut some time required to run python unit tests on release branch. There were other recent improvements to Python tests on master, but I think they also happened after a release was cut. On Fri, Nov 22, 2019 at 3:46 PM Mikhail Gryzykhin wrote: >

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-11-22 Thread Mikhail Gryzykhin
UPD: on current branch there's timeout on gradle build job, I'm mitigating it by increasing job time. Seems that this job runs most of python tests. We might look into adjusting the target. Second failure is https://issues.apache.org/jira/browse/BEAM-8812 . I would really appreciate if someone

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-11-19 Thread Kenneth Knowles
I've poked through the bugs and there do seem to be a few that are finished and a few that may not be started that should probably be deferred if they can be triaged to not be blockers. Kenn On Fri, Nov 15, 2019 at 2:13 PM Mikhail Gryzykhin wrote: > Hi everyone, > > There's still an

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-11-15 Thread Mikhail Gryzykhin
Hi everyone, There's still an outstanding cherry-pick PR that I can't merge due to tests failing on it and release branch validation PR . Once I get tests green, I'll send another update and review outstanding open issues. --Mikhail On Fri, Nov 15, 2019

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-11-15 Thread Thomas Weise
Any update regarding the release? The list still shows 10 open issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20fixVersion%20%3D%202.17.0%20and%20resolution%20is%20EMPTY Is the RC blocked on those? On Mon, Oct 28, 2019 at 12:46 PM Ahmet Altay wrote: > > >

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-10-28 Thread Ahmet Altay
On Mon, Oct 28, 2019 at 12:44 PM Gleb Kanterov wrote: > It looks like BigQueryIO DIRECT_READ is broken since 2.16.0, I've added a > ticket describing the problem and possible fix, see BEAM-8504 > [1]. > Should this be added to 2.16 blog post as

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-10-28 Thread Gleb Kanterov
It looks like BigQueryIO DIRECT_READ is broken since 2.16.0, I've added a ticket describing the problem and possible fix, see BEAM-8504 [1]. [1]: https://issues.apache.org/jira/browse/BEAM-8504 On Wed, Oct 23, 2019 at 9:19 PM Kenneth Knowles

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-10-23 Thread Kenneth Knowles
I opened https://github.com/apache/beam/pull/9862 to raise the documentation of Fix Version to the top level. It also includes the write up of Jira priorities, to make clear that "Blocker" priority does not refer to release blocking. On Wed, Oct 23, 2019 at 11:16 AM Kenneth Knowles wrote: >

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-10-23 Thread Kenneth Knowles
I've gone over the tickets and removed Fix Version from many of them that do not seem to be critical defects. If I removed Fix Version from a ticket you care about, please feel free to add it back. I am not trying to decide what is in/out of the release, just trying to triage the Jira data to

Re: [UPDATE] Preparing for Beam 2.17.0 release

2019-10-23 Thread Kenneth Knowles
Wow, 28 release blocking tickets! That is the most I've ever seen, by far. Many appear to be feature requests, not release-blocking defects. I believe this is not according to our normal best practice. The release cadence should not wait for features in progress, with exceptions discussed on

[UPDATE] Preparing for Beam 2.17.0 release

2019-10-23 Thread Mikhail Gryzykhin
Hi all, Beam 2.17 release branch cut is scheduled today (2019/10/23) according to the release calendar [1]. I'll start working on the branch cutoff and later work on cherry picking blocker fixes. If you have release blocking issues for 2.17 please mark their "Fix Version" as 2.17.0 [2]. This