Re: Apache Airflow 1.10.6 released!

2019-10-28 Thread Aizhamal Nurmamat kyzy
Thanks Ash and everyone who was involved! On Mon, Oct 28, 2019 at 3:16 PM Kevin Yang wrote: > Releases keeps getting smoothier  And definitely looking forwards to have > DAG serialization, or maybe even stateless webserver? > > > Cheers, > Kevin Y > > On Mon, Oct 28, 2019 at 2:49 PM Jarek

Re: [PROPOSE] Ease future migration path to 2.0 by provider's operators/hook backporting to 1.10.*

2019-10-28 Thread Kevin Yang
Tomasz and Ash got good points about the overhead of having separate repos. But while we grow bigger and more mature, I would prefer to have what was described in AIP-8. It shouldn't be extremely hard for us to come up with good strategies to handle the overhead. AIP-8 already talked about how it

Re: [RESULT] [VOTE] Release 1.10.6 from 1.10.6rc2

2019-10-28 Thread Kevin Yang
Make sense. Would probably prefer weekends 2 months back. Maybe half-half then? On Mon, Oct 28, 2019 at 2:59 PM Jarek Potiuk wrote: > Well. Seems like some of us have more time to spend on Airflow during the > weekends rather than weekdays so I think it's OK to get the voting covering > both -

Re: Apache Airflow 1.10.6 released!

2019-10-28 Thread Kevin Yang
Releases keeps getting smoothier  And definitely looking forwards to have DAG serialization, or maybe even stateless webserver? Cheers, Kevin Y On Mon, Oct 28, 2019 at 2:49 PM Jarek Potiuk wrote: > Great! So now we can now target our efforts towards 1.10.7 with long > awaited DAG

Re: [RESULT] [VOTE] Release 1.10.6 from 1.10.6rc2

2019-10-28 Thread Jarek Potiuk
Well. Seems like some of us have more time to spend on Airflow during the weekends rather than weekdays so I think it's OK to get the voting covering both - week-ends and week-days ;) On Mon, Oct 28, 2019 at 10:51 PM Ash Berlin-Taylor wrote: > :) Given this was no-code-changes since RC1 I

Re: [RESULT] [VOTE] Release 1.10.6 from 1.10.6rc2

2019-10-28 Thread Ash Berlin-Taylor
:) Given this was no-code-changes since RC1 I wasn't worrying about it on this specific vote, but yes point taken :) -ash > On 28 Oct 2019, at 21:49, Kevin Yang wrote: > >  > > Tested core, UI and breeze locally with 3.7.3, all good. +1 (non-binding) > Maybe next time make the voting hours

Re: [RESULT] [VOTE] Release 1.10.6 from 1.10.6rc2

2019-10-28 Thread Jarek Potiuk
Fantastic! On Mon, Oct 28, 2019 at 10:18 PM Ash Berlin-Taylor wrote: > Hello, > > Apache Airflow 1.10.6 (based on RC2) has been accepted. > > 4 “+1” binding votes received: > - Ash Berlin-Taylor (binding) > - Kaxil Naik (binding) > - Fokko Driesprong (binding) > - Jarek Potiuk (binding) > > No

Re: [RESULT] [VOTE] Release 1.10.6 from 1.10.6rc2

2019-10-28 Thread Kevin Yang
 Tested core, UI and breeze locally with 3.7.3, all good. +1 (non-binding) Maybe next time make the voting hours all in weekdays? :P Cheers, Kevin Y On Mon, Oct 28, 2019 at 2:18 PM Ash Berlin-Taylor wrote: > Hello, > > Apache Airflow 1.10.6 (based on RC2) has been accepted. > > 4 “+1”

Re: Apache Airflow 1.10.6 released!

2019-10-28 Thread Jarek Potiuk
Great! So now we can now target our efforts towards 1.10.7 with long awaited DAG serialisation ! And work on 2.0* in parallel. Exciting times :) J, On Mon, Oct 28, 2019 at 10:43 PM Ash Berlin-Taylor wrote: > Dear Airflow community, > > I'm happy to announce that Airflow 1.10.6 was just

Apache Airflow 1.10.6 released!

2019-10-28 Thread Ash Berlin-Taylor
Dear Airflow community, I'm happy to announce that Airflow 1.10.6 was just released. The source release, as well as the binary "sdist" and wheel bundles, are available here: https://dist.apache.org/repos/dist/release/airflow/1.10.6/ We also made this version available on PyPi for

[RESULT] [VOTE] Release 1.10.6 from 1.10.6rc2

2019-10-28 Thread Ash Berlin-Taylor
Hello, Apache Airflow 1.10.6 (based on RC2) has been accepted. 4 “+1” binding votes received: - Ash Berlin-Taylor (binding) - Kaxil Naik (binding) - Fokko Driesprong (binding) - Jarek Potiuk (binding) No other votes were cast. I'll continue with the release process and the release

Re: [PROPOSE] Ease future migration path to 2.0 by provider's operators/hook backporting to 1.10.*

2019-10-28 Thread Jarek Potiuk
We are checking how we can use namespaces in back-portable way and we will have POC soon so that we all will be able to see how it will look like. J. On Mon, Oct 28, 2019 at 1:24 PM Ash Berlin-Taylor wrote: > I'll have to read your proposal in detail (sorry, no time right now!), but > I'm

Re: [PROPOSE] Ease future migration path to 2.0 by provider's operators/hook backporting to 1.10.*

2019-10-28 Thread Ash Berlin-Taylor
I'll have to read your proposal in detail (sorry, no time right now!), but I'm broadly in favour of this approach, and I think keeping them _in_ the same repo is the best plan -- that makes writing and testing cross-cutting changes easier. -a > On 28 Oct 2019, at 12:14, Tomasz Urbaszek

Re: [PROPOSE] Ease future migration path to 2.0 by provider's operators/hook backporting to 1.10.*

2019-10-28 Thread Tomasz Urbaszek
I think utilizing namespaces should reduce a lot of problems raised by using separate repos (who will manage it? how to release? where should be the repo?). Bests, Tomek On Sun, Oct 27, 2019 at 11:54 AM Jarek Potiuk wrote: > Thanks Bas for comments! Let me share my thoughts below. > > On Sun,