Depends on how fast it stabilizes... Sent from my iPhone
> On 7 Sep 2017, at 21:11, Sergei Iakhnin <[email protected]> wrote: > > The Kubernetes features would be exciting to have. Do you think these will > make it into this release? > >> On Thu, Sep 7, 2017 at 8:22 PM Bolke de Bruin <[email protected]> wrote: >> >> Would be appreciated! >> >> Op 7 sep. 2017 8:06 p.m. schreef "Chris Riccomini" <[email protected] >>> : >> >>> @Bolke, I can wait to cut the test branch until that PR is merged, if you >>> like. >>> >>> On Thu, Sep 7, 2017 at 10:19 AM, Bolke de Bruin <[email protected]> >> wrote: >>> >>>> One of my team members is preparing a comprehensive PR that reworks all >>>> logging to use the standard framework that was recently introduced. It >> is >>>> expected to be become public tomorrow. So please don't cut too early >> ;-). >>>> In addition it would be nice to have a PR clean up? Some PRs have been >>>> waiting for some time. >>>> >>>> BTW: we will maintain 1.8.X for bug fixes until 1.10/2.0 comes along. >>>> >>>> Cheers >>>> Bolke >>>> >>>> Sent from my iPhone >>>> >>>>> On 7 Sep 2017, at 18:55, Chris Riccomini <[email protected]> >>> wrote: >>>>> >>>>> Hey all, >>>>> >>>>> The workflow is documented here: >>>>> >>>>> >> https://cwiki.apache.org/confluence/display/AIRFLOW/Releasing+Airflow >>>>> >>>>> I'll probably cut the 1.9.0 test branch today or tomorrow, depending >> on >>>>> schedule. I'll let folks know when it's cut via dev@. >>>>> >>>>>> Once the branch is cut does that mean no more PRs will be included >> in >>>> the >>>>> release, or can some changes still be cherry-picked/merged in? >>>>> >>>>> We can still cherry-pick PRs in. Very quickly, though, we begin >>> rejecting >>>>> any PRs that aren't bug fixes. It's a big exercise to stabilize these >>>>> releases, so I will start rejecting merging non-bug fix PRs pretty >>>> quickly. >>>>> Probably within a couple of weeks. >>>>> >>>>> Cheers, >>>>> Chris >>>>> >>>>> On Thu, Sep 7, 2017 at 9:31 AM, Ash Berlin-Taylor < >>>>> [email protected]> wrote: >>>>> >>>>>> What is the workflow? Once the branch is cut does that mean no more >>> PRs >>>>>> will be included in the release, or can some changes still be >>>>>> cherry-picked/merged in? >>>>>> >>>>>> (Is this documented somewhere I can read?) >>>>>> >>>>>> Oh, and thing someone in gitter chat pointed out: the CHANGELOG on >>>> master >>>>>> doesn't include entries for 1.8.2. >>>>>> >>>>>> -ash >>>>>>> On 7 Sep 2017, at 17:28, Andrew Chen <[email protected]> >>>> wrote: >>>>>>> >>>>>>> Any estimate when branch 1.9 will be cut? >>>>>>> >>>>>>> On Thu, Sep 7, 2017 at 9:25 AM, Maxime Beauchemin < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Go for it! Still trying to wrap up 1.8.2 ... >>>>>>>> >>>>>>>> Max >>>>>>>> >>>>>>>> On Thu, Sep 7, 2017 at 8:31 AM, Bolke de Bruin <[email protected] >>> >>>>>> wrote: >>>>>>>> >>>>>>>>> Awesome! >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 7 Sep 2017, at 17:04, Chris Riccomini <[email protected] >>> >>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Hey all, >>>>>>>>>> >>>>>>>>>> I want to get the ball rolling on 1.9.0, now that 1.8.2 is out >> the >>>>>>>> door. >>>>>>>>>> >>>>>>>>>> @Max, I recall you mentioning driving this, but if you're burnt >>> out >>>>>>>> after >>>>>>>>>> the 1.8.2 work, Joy and I can drive 1.9.0. Just let me know. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Chris >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>> >>> >> > -- > > Sergei
