Re: [VOTE] Airflow Providers prepared on April 16, 2024

2024-04-20 Thread Hussein Awala
+1 (binding) On Thursday, April 18, 2024, Jarek Potiuk wrote: > +1 (binding): checked reproducibility, licences, signatures, checksums - > all look good. > > On Thu, Apr 18, 2024 at 12:27 PM Pankaj Singh > wrote: > > > +1 (non-binding) tested my changes. > > > > Thanks > > Pankaj > > > > > > >

Re: [HUGE DISCUSSION] Airflow3 and tactical (Airflow 2) vs strategic (Airflow 3) approach

2024-04-20 Thread Vikram Koka
A wonderful and exciting Saturday morning discussion! Thank you Jarek for bringing the offline conversations into the mailing list. I completely agree on the necessity of Airflow 3. I also agree that Gen AI is the trigger i.e. the answer to "Why now"? Having been thinking about this for a while

Re: [DISCUSS] DRAFT AIP-68 Extended Plugin Interface + AIP-69 Remote Executor

2024-04-20 Thread Jarek Potiuk
Hey Jens, I looked at the AIPs when you created them and I very much like the directions put there - but it also got me into a lot of thinking on the future of Airflow and AIPs. See the thread I started https://lists.apache.org/thread/3chvg9964zvh15mtrbl073f4oj3nlzp2 - about Airflow 3. I think

Team id as dag_id prefix: (was [VOTE] AIP-67)

2024-04-20 Thread Jarek Potiuk
Hey Ash and Daniel (and others unconvinced), I split the discussion here so that we do not clutter the VOTE thread. I hope I can convince you that yes, it makes sense to approach it this way and that you withdraw the veto Ash. It needs a bit of context and the separate discussion I started on

[HUGE DISCUSSION] Airflow3 and tactical (Airflow 2) vs strategic (Airflow 3) approach

2024-04-20 Thread Jarek Potiuk
Hello here, I have been thinking a lot recently and discussing with some people and I am more and more convinced it's about the time we - as a community - should start doing changes considering "Airflow 2" current and "Airflow 3" future. *TL;DR: I think we should seriously start work on Airflow