Proposed Agenda

Attendees

  • Vikram Koka

  • Ash Berlin-Taylor

  • Shahar Epstein

  • Jens Scheffler

  • David

  • Jarek Potiuk

  • Pavan Kumar

  • Vishnu Chilukoori

  • Rajesh Bishundeo

  • Bugra Ozturk

  • Cedrik Neumann

  • Ephraim Anierobi

  • Amogh Rajesh Desai

  • Tamara Fingerlin

  • Vincent Beck

  • Rahul Vats

  • Phani Kumar

  • Karthikeyan Singaravelan

  • Pierre Jeambrun

  • Jed Cunningham

  • Brent Bovenzi

  • Eugene Kostielev

  • Kenten Danas

  • Daniel Imberman

  • Daniel Hegberg

  • Shubham Mehta

Summary

  • Follow-up on action items from the last call
  • Development Updates and Presentations:
    • Update on AIP-72 Task Execution Interface aka Task SDK Ash Berlin-Taylor Amogh Desai
      • Ash walked through a demo of the Triggerer support with the new TaskSDK. He shared how this was largely in place, with the exception of connection access.
      • Ash mentioned that the Triggerer is now split into two processes, using the supervisor pattern from the Task SDK. 
      • Amogh gave an impromptu demo of the Kubernetes Executor now working with the TaskSDK. 
    • Update on AIP-66 DAG Bundles & Parsing Daniel Standish  
      • Daniel Standish shared a recording of the demo covering the stale DAG bundle cleanup process.
      • Since Workers now pull code from remote sources to run tasks and since this is stored locally to reduce latency, there is cleanup required to avoid these piling up on the worker nodes. 
      • He said that "old / stale" could be defined by time or number of older versions.
    • Test plan update Rahul Vats 
      • Rahul covered the testing status as documented in the Airflow 3 Test Plan
      • Rahul covered the testing status of Alpha 3 and the confidence levels of the different areas including the UI and CLI. He mentioned that these are still in progress, since development is still ongoing. 
      • He mentioned that they have started testing with focus on specific AIPs and are now reporting status by AIPs as well.
      • He asked the AIP owners to review the test cases and validate them as they make changes. And for the AIP owners to ensure that there was at least one run on each before the beta releases as well. 
    • AIP-81 CLI Update Buğra Öztürk
      • Bugra covered the updated design for the Authentication work for the CLI. 
      • Bugra asked for help from the committers on the call to review the PRs coming in for the CLI AIP, since some of the PRs were sitting for a while in review status.
      • Bugra commented that some of the authentication work would probably need to come in Airflow 3.1, rather than in 3.0. 
    • Update on AIP-38 Modern Web Application Brent Bovenzi 
      • Brent demonstrated an updated UX in the Airflow UI, with the Grid View or Graph View (based on the user preference) on the left hand of the page to give a consistent view with the modal views on the right hand side. 
      • The updated UX drew a very positive response from the team on the call. 
      • Brent showed how the new UX addressed color-blindness issues with icons and was more accessible. 
  • Discussion topics:
    • Python 3.13 (not only) -driven dependency issues Jarek Potiuk 
      • Jarek highlighted these three issues with 3.13.
      • Pendulum: He said that the Pendulum maintainer got back to him and we don't have to do anything in this area. 
      • google-re2 → can we replace "root" usage in UI: Jarek said that Google-re2 issue is a bit more pervasive in Airflow and that after speaking with Bugra is solvable in the CLI. He was concerned about its use in the UI and API. Brent and Pierre said that this was no longer being used, so it is not needed anymore.
      • FAB (and sqlalchemy and pandas) → to FAB or not to FAB: The dependency conflict between SqlAlchemy, Pandas and FAB requires us to probably take out FAB as quickly as possible from Core Airflow. 
    • Removing the old UI Jedidiah Cunningham 
      • Jed said that he is targeting next week to remove the old UI, before we ship Beta 1. 
      • Jed also proposed moving that branch to the main repo for easier collaboration from the larger team and there was general agreement.  
    • Bump minimum version for Airflow 3.0 to Python 3.10 (~6months ahead of EoL schedule) Ash Berlin-Taylor
      • Ash proposed this and asked if there were any strong feelings against it. 
      • There was significant discussion about what this meant for Airflow 2.x vs. 3.x including the implications for Provider releases going forward. 
      • The decision was to take this to the mailing list. 
  • No labels