Hello everyone, we will explore a workaround for the issues with the Dataflow worker.
Because of this, the 2.6.0 release is no longer blocked by the Dataflow workers at the moment. I hope to produce a release candidate by end-of-day tomorrow. Please reach out on this thread, or to me directly if you have any concerns or questions. Thanks! -P. On Sun, Jul 29, 2018 at 9:23 PM Reuven Lax <re...@google.com> wrote: > No problem :) I'm not entirely sure why the PR fixed his issue, but it > couldn't cause any harm so I went ahead and merged it. > > On Sun, Jul 29, 2018 at 11:56 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> Yes, it's this one and I planned to do the review tonight. >> >> Just saw that you did the review and merge it. Thanks. >> >> Regards >> JB >> >> On 29/07/2018 19:40, Reuven Lax wrote: >> > Jozef, you reference a pull request in the bug, are you referring to >> > this one? >> > >> > https://github.com/apache/beam/pull/6075/files >> > >> > On Sun, Jul 29, 2018 at 12:13 AM Jozef Vilcek <jozo.vil...@gmail.com >> > <mailto:jozo.vil...@gmail.com>> wrote: >> > >> > Hello, is there a change this bug make it into the release? >> > >> > https://issues.apache.org/jira/browse/BEAM-5028 >> > >> > On Sat, Jul 28, 2018 at 1:38 AM Pablo Estrada <pabl...@google.com >> > <mailto:pabl...@google.com>> wrote: >> > >> > Hello all, >> > I will start daily updates of progress on the 2.6.0 release. >> > As of today, the main release blockers are issues in Dataflow >> > that are preventing us from cutting the Dataflow workers. >> > >> > * One issue in Java SDK related to FnAPI. Specifically PR 5709 >> > requires Dataflow worker changes[1]. >> > * One issue in the Python SDK related to context management. >> > PR 5356 also requires Dataflow worker changes [2]. >> > >> > Please reach out to me if you have any questions. >> > Best >> > -P. >> > >> > [1] https://github.com/apache/beam/pull/5709 >> > [2] https://github.com/apache/beam/pull/5356 >> > >> > >> > On Thu, Jul 26, 2018 at 2:16 PM Pablo Estrada >> > <pabl...@google.com <mailto:pabl...@google.com>> wrote: >> > >> > Hello everyone, >> > I wanted to do an update on the state of the release, as >> > there haven't been news on this for a while. >> > We have found a few issues that broke postcommits a few >> > weeks back, but we hadn't noticed. Some people are tacking >> > these to try to stabilize the release branch[1]. >> > >> > In the meantime, the release has been blocked, but Boyuan >> > Zhang has taken advantage of this to code up a few scripts >> > to try and automate release steps. (Thanks Boyuan!). We will >> > try these as soon as the release is unblocked. >> > >> > Best >> > -P. >> > >> > [1] https://github.com/apache/beam/pull/6072 >> > >> > On Wed, Jul 18, 2018 at 11:03 AM Pablo Estrada >> > <pabl...@google.com <mailto:pabl...@google.com>> wrote: >> > >> > Hello all! >> > I've cut the release branch (release-2.6.0), with some >> > help from Ahmet and Boyuan. From now on, please >> > cherry-pick 2.6.0 blockers into the branch. >> > Now we start stabilizing it. >> > >> > Thanks! >> > >> > -P. >> > >> > On Tue, Jul 17, 2018 at 9:34 PM Jean-Baptiste Onofré >> > <j...@nanthrax.net <mailto:j...@nanthrax.net>> wrote: >> > >> > Hi Pablo, >> > >> > I'm investigating this issue, but it's a little long >> > process. >> > >> > So, I propose you start with the release process, >> > cutting the branch, >> > and then, I will create a cherry-pick PR for this >> one. >> > >> > Regards >> > JB >> > >> > On 17/07/2018 20:19, Pablo Estrada wrote: >> > > Checking once more: >> > > What does the communitythink we should do >> > > >> > about >> https://issues.apache.org/jira/browse/BEAM-4750 ? >> > Should I bump it >> > > to 2.7.0? >> > > Best >> > > -P. >> > > >> > > On Fri, Jul 13, 2018 at 5:15 PM Ahmet Altay >> > <al...@google.com <mailto:al...@google.com> >> > > <mailto:al...@google.com >> > <mailto:al...@google.com>>> wrote: >> > > >> > > >> > Update: >> https://issues.apache.org/jira/browse/BEAM-4784 is >> > not a >> > > release blocker, details in the JIRA issue. >> > > >> > > On Fri, Jul 13, 2018 at 11:12 AM, Thomas Weise >> > <t...@apache.org <mailto:t...@apache.org> >> > > <mailto:t...@apache.org >> > <mailto:t...@apache.org>>> wrote: >> > > >> > > Can one of our Python experts please take >> > a look >> > > >> > at https://issues.apache.org/jira/browse/BEAM-4784 >> > and advise if >> > > this should be addressed for the release? >> > > >> > > Thanks, >> > > Thomas >> > > >> > > >> > > On Fri, Jul 13, 2018 at 11:02 AM Ahmet >> > Altay <al...@google.com <mailto:al...@google.com> >> > > <mailto:al...@google.com >> > <mailto:al...@google.com>>> wrote: >> > > >> > > >> > > >> > > On Fri, Jul 13, 2018 at 10:48 AM, >> > Pablo Estrada >> > > <pabl...@google.com >> > <mailto:pabl...@google.com> >> > <mailto:pabl...@google.com >> > <mailto:pabl...@google.com>>> wrote: >> > > >> > > Hi all, >> > > I've triaged most issues marked >> > for 2.6.0 release. I've >> > > localized two that need a decision >> > / attention: >> > > >> > > >> > - https://issues.apache.org/jira/browse/BEAM-4417 >> - >> > > Bigquery IO Numeric Datatype >> > Support. Cham is not >> > > available to fix this at the >> > moment, but this is a >> > > critical issue. Is anyone able to >> > tackle this / should >> > > we bump this to next release? >> > > >> > > >> > > I bumped this to the next release. I >> > think Cham will be the >> > > best person to address it when he is >> > back. And with the >> > > regular release cadence, it would not >> > be delayed by much. >> > > >> > > >> > > >> > > >> > - https://issues.apache.org/jira/browse/BEAM-4750 >> - >> > > Performance degradation due to >> > some safeguards in >> > > beam-sdks-java-core. JB, are you >> > looking to fix this? >> > > Should we bump? I had the >> > impression that it was an easy >> > > fix, but I'm not sure. >> > > >> > > If you're aware of any other issue >> > that needs to be >> > > included as a release blocker, >> > please report it to me. >> > > Best >> > > -P. >> > > >> > > On Thu, Jul 12, 2018 at 2:15 AM >> > Etienne Chauchot >> > > <echauc...@apache.org >> > <mailto:echauc...@apache.org> >> > <mailto:echauc...@apache.org >> > <mailto:echauc...@apache.org>>> wrote: >> > > >> > > +1, >> > > >> > > Thanks for volunteering Pablo, >> > thanks also to have >> > > caught tickets that I forgot >> > to close :) >> > > >> > > Etienne >> > > >> > > Le mercredi 11 juillet 2018 à >> > 12:55 -0700, Alan >> > > Myrvold a écrit : >> > >> +1 Thanks for volunteering, >> Pablo >> > >> >> > >> On Wed, Jul 11, 2018 at 11:49 >> > AM Jason Kuster >> > >> <jasonkus...@google.com >> > <mailto:jasonkus...@google.com> >> > >> >> > <mailto:jasonkus...@google.com >> > <mailto:jasonkus...@google.com>>> wrote: >> > >>> +1 sounds great >> > >>> >> > >>> On Wed, Jul 11, 2018 at >> > 11:06 AM Thomas Weise >> > >>> <t...@apache.org >> > <mailto:t...@apache.org> <mailto:t...@apache.org >> > <mailto:t...@apache.org>>> wrote: >> > >>>> +1 >> > >>>> >> > >>>> Thanks for volunteering, >> Pablo! >> > >>>> >> > >>>> On Mon, Jul 9, 2018 at 9:56 >> > PM Jean-Baptiste >> > >>>> Onofré <j...@nanthrax.net >> > <mailto:j...@nanthrax.net> >> > >>>> <mailto:j...@nanthrax.net >> > <mailto:j...@nanthrax.net>>> wrote: >> > >>>>> +1 >> > >>>>> >> > >>>>> I planned to send the >> > proposal as well ;) >> > >>>>> >> > >>>>> Regards >> > >>>>> JB >> > >>>>> >> > >>>>> On 09/07/2018 23:16, Pablo >> > Estrada wrote: >> > >>>>> > Hello everyone! >> > >>>>> > >> > >>>>> > As per the previously >> > agreed-upon schedule >> > >>>>> for Beam releases, the >> > >>>>> > process for the 2.6.0 >> > Beam release should >> > >>>>> start on July 17th. >> > >>>>> > >> > >>>>> > I volunteer to perform >> > this release. >> > >>>>> > >> > >>>>> > Here is the schedule >> > that I have in mind: >> > >>>>> > >> > >>>>> > - We start triaging JIRA >> > issues this week. >> > >>>>> > - I will cut a release >> > branch on July 17. >> > >>>>> > - After July 17, any >> > blockers will need to be >> > >>>>> cherry-picked into the >> > >>>>> > release branch. >> > >>>>> > - As soon as tests look >> > good, and blockers >> > >>>>> have been addressed, I >> will >> > >>>>> > perform the other >> > release tasks. >> > >>>>> > >> > >>>>> > Does that seem >> > reasonable to the community? >> > >>>>> > >> > >>>>> > Best >> > >>>>> > -P. >> > >>>>> > -- >> > >>>>> > Got feedback? >> > go/pabloem-feedback >> <https://goto.google.com/pabloem-feedback> >> > <https://goto.google.com/pabloem-feedback> >> > >>>>> >> > <https://goto.google.com/pabloem-feedback> >> > >>>>> >> > >>>>> -- >> > >>>>> Jean-Baptiste Onofré >> > >>>>> jbono...@apache.org >> > <mailto:jbono...@apache.org> >> > <mailto:jbono...@apache.org >> > <mailto:jbono...@apache.org>> >> > >>>>> http://blog.nanthrax.net >> > >>>>> Talend - >> http://www.talend.com >> > >>> >> > >>> >> > > -- >> > > Got feedback? go/pabloem-feedback >> <https://goto.google.com/pabloem-feedback> >> > <https://goto.google.com/pabloem-feedback> >> > > >> > <https://goto.google.com/pabloem-feedback> >> > > >> > > >> > > >> > > -- >> > > Got feedback? go/pabloem-feedback >> <https://goto.google.com/pabloem-feedback> >> > <https://goto.google.com/pabloem-feedback> >> > >> > -- >> > Jean-Baptiste Onofré >> > jbono...@apache.org <mailto:jbono...@apache.org> >> > http://blog.nanthrax.net >> > Talend - http://www.talend.com >> > >> > -- >> > Got feedback? go/pabloem-feedback >> <https://goto.google.com/pabloem-feedback> >> > <https://goto.google.com/pabloem-feedback> >> > >> > -- >> > Got feedback? go/pabloem-feedback >> <https://goto.google.com/pabloem-feedback> >> > <https://goto.google.com/pabloem-feedback> >> > >> > -- >> > Got feedback? go/pabloem-feedback >> <https://goto.google.com/pabloem-feedback> >> > <https://goto.google.com/pabloem-feedback> >> > >> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> > -- Got feedback? go/pabloem-feedback
