Proposed Agenda

Attendees

  • Vikram Koka

  • Jarek Potiuk

  • Vishnu Chilukoori

  • Elad Kalif

  • Jens Scheffler

  • Amogh Rajesh Desai

  • Ryan Hatter

  • Kathikeyan Singaravelan

  • Brent Bovenzi

  • Kaxil Naik

  • Rahul Vats

  • Rajesh Bishundeo

  • Kalyan R

  • Kenten Danas

  • Pierre Jeambrun

  • Faouz El Fassi

  • Zach Gottesman

  • Eugene Kostielev

  • Tim Davis

  • Tamara Fingerlin

  • Michal Modras

  • Bugra Ozturk

  • Ankit Chaurasia

  • Daniel Standish

  • David

  • Ephraim Anierobi

  • Vincent Beck

Summary

  • Follow-up on action items from last call:
    • Edge Provider naming Elad Kalif  Jarek Potiuk:
      • Elad explained that the Edge provider will be called "edge3" for many reasons.
      • It's ready to be used and tested.
      • Once the current Provider vote is closed, Elad will cut a new wave including Git and Edge3 for an extra 24 hours voting period and then these would be released. 
  • Development Updates
    • Test plan and Issue statistics update Rahul Vats and vikram 
      • Rahul shared the current state of testing based on RC3 and said the regression testing on RC3 is ongoing.
      • Rahul felt that the current confidence level is high.
      • Rahul also shared the issue statistics for Airflow 3 with:
        • Alpha releases: 40 issues reported and closed.
        • Beta releases: 129 issues reported and closed.
        • Release candidates: 102 issues reported, with 64 of them already closed. 
      • Rahul also said that there are no currently open blocking issues with the release.
      • He also expressed how many issues were fixed directly in PRs without the issues even being reported.
      • Vikram added that he had a target of at least 200 issues to be reported in the combination of Alpha, Beta, and RCs.
      • He said that seeing a total of 271 issues reported was great to see and gave confidence in testing of the release. 
  • Discussion Topics
    • Dev workflow for 3.0+ Kaxil Naik 
      • Kaxil explained that we now have project milestones for 3.0.1, Airflow 3.1.0, and Airflow 3.1+. 
      • He articulated how these should be used for new work going forward with issue resolutions for 3.0.1, vs. new feature work being targeted for 3.1.0 and 3.1+ 
    • Docs approach towards AF 3 users Elad Kalif 
      • Elad reminded everyone that our docs are versioned and asked everyone to write docs assuming that the users coming are using Airflow 3.0. 
      • Elad asked doc writers to avoid "if Airflow 2, do this" and "if Airflow 3, do this" within the docs, since that would be confusing to the reader. 
    • Ongoing support for Airflow 2 Kaxil Naik 
      • Kaxil brought up the topic of "maintenance support for Airflow 2", once Airflow 3 is released.
      • Kaxil showed that we had supported Core Airflow 1.10.x maintenance releases for 6 months after the release of Airflow 2. 
      • There was significant discussion around this including the separation of maintenance of bug fixes vs. security fixes. 
      • Elad also brought up the separation of maintenance updates for Core Airflow OSS vs. Providers
      • The decision from the team was to take this discussion to the devlist. Kaxil to start a mailing list thread.
  • No labels