• Created by Unknown User (jscheffl) on May 15, 2026 3 minute read

Proposed Agenda

Attendees

  • Vikram Koka

  • Jarek Potiuk

  • Jens Scheffler

  • Rajeshwar Bishundeo

  • Ephraim Anierobi

  • Rahul Vats

  • Dheeraj Turaga

  • Jed Cunningham

  • Vincent Beck

  • Amogh Rajesh Desai

  • Bugra Ozturk

  • Karthikeyan Singaravelan

  • Brent Bovenzi

  • Pierre Jeambrun

  • Christos Bisias

  • Phani Kumar

  • Cedrik Neumann

  • Shahar Epstein

  • Sean Ghaeli

Summary

  • Development Updates
    • Airflow 3.1.4 patch release update (Ephraim Anierobi)
      • Ephraim shared that the 3.1.4 patch release had around 47 bug fixes, with a total of around 183 pull requests. 
      • Key fixes included task clearing race conditions in backfills when multiple schedulers are active, deadline alert handling, local executor memory leaks and N+1 query improvements. 
      • There are also several UI improvements including task highlighting in the graph view and mobile layout. 
    • Task SDK / Shared libraries update (Amogh Desai)
      • Amogh said that the "shared library" effort is nearly complete now with 7 libraries identified for decoupling Task SDK from Airflow Core. 
      • Out of these seven, five have already been completed and merged. The two remaining are for traces/metrics and listeners. 
      • Amogh and Jarek gave a shoutout to Christos for the work here! 
    • UI E2E Testing framework update (Rahul Vats)
      • Rahul shared that the playwright based framework PR for testing was merged and that CI work is in progress to trigger these tests for UI changes. 
      • Rahul said that he had created a meta issue containing all the test scenarios organized by page and that the plan was to focus on critical flows and recent UI issues such as pagination. 
      • Rahul asked for community contributions here and was considering a phased rollout. 
  • Discussion Topics
    • Providers documented release plan (Jens Scheffler / Jarek Potiuk)
      • Jens said he had created a draft release for providers in Confluence to help coordinate the work between release managers.
      • Jens said that it currently covered Provider releases and could be expanded to others.
      • Jens asked where the Core Airflow releases were documented and Vikram shared that they were documented in the Airflow 3.x wiki page, but was out of date for the 3.1.4 page
      • Jens also asked if there were any objections to moving the provider releases from Thursday to Tuesday to facilitate easier validation on weekdays instead of weekends. The release managers agreed to this. 
    • Helm chart scope and strategy (Jens, Jarek, Jed) 
      • There was a quick reference to the dev list email about dropping support for Airflow 1 in the helm chart and that there would be a lazy consensus follow up to the same
      • There was much longer discussion on the overall scope of the Helm chart, including changes for the embedded database support in the helm chart. There also was a reference to potentially adopting Kustomize as a way to simplify the chart and to extend it for edge cases using Kustomize. There was no immediate agreement here, other than to continue the discussion async on the dev list.  
    • Airflow 3.2 potential scope 
      • Vikram started the discussion saying that it would be good to get an overall scope and plans together for 3.2 release with the target timeline of March 2026. 
      • Vikram also added that Daniel Standish had updated the Asset Partitions AIP with the focus on 3.2. 
      • Vincent added that the multi-team work was progressing and that they would be targeting an experimental release in time for 3.2 to enable user testing and feedback, with a goal of an official release in Airflow 3.3 later in the year. 
      • Rajesh added that Dennis was actively working on the Deadline Alerts sync callback work with a target of 3.2 release.
      • The team noted that there were several large AIPs being discussed and that we need to get some formal scope and planning together in order to identify the interactions between these AIPs. Vikram took the action item to ask and help these AIP authors formalize scope and timelines. 
    • Rookie awards vote (Srabasti)
      • Vikram said that Srabasti Banerjee had wanted to remind the team to vote for the "new budding contributor" awards on the dev list before the deadline.