dev  

Messages by Thread

• • Re: 📢 Apache Airflow 3.0.0beta1 is available for testing! 🎉 Vikram Koka
  • Re: 📢 Apache Airflow 3.0.0beta1 is available for testing! 🎉 Amogh Desai
  • Re: 📢 Apache Airflow 3.0.0beta1 is available for testing! 🎉 Jarek Potiuk
  • Re: 📢 Apache Airflow 3.0.0beta1 is available for testing! 🎉 Aritra Basu
  • Re: 📢 Apache Airflow 3.0.0beta1 is available for testing! 🎉 Vincent Beck
  • Re: 📢 Apache Airflow 3.0.0beta1 is available for testing! 🎉 Bishundeo, Rajeshwar
  • Re: 📢 Apache Airflow 3.0.0beta1 is available for testing! 🎉 Oliveira, Niko
  • Re: 📢 Apache Airflow 3.0.0beta1 is available for testing! 🎉 Pavankumar Gopidesu
• [ANNOUNCE] Apache Airflow Providers prepared on February 21, 2025 are released Elad Kalif
• [RESULT][VOTE] Airflow Providers - February 21, 2025 Elad Kalif
• [ANNOUNCE] Final (hopefully) woes with IDE integration in the new providers structure solved Jarek Potiuk
  • Re: [ANNOUNCE] Final (hopefully) woes with IDE integration in the new providers structure solved Jarek Potiuk
• [DISCUSS] removing pickling of executor config.... and any others? Daniel Standish
  • Re: [DISCUSS] removing pickling of executor config.... and any others? Ash Berlin-Taylor
  • Re: [DISCUSS] removing pickling of executor config.... and any others? Jarek Potiuk
  • Re: [DISCUSS] removing pickling of executor config.... and any others? Constance Martineau
  • Re: [DISCUSS] removing pickling of executor config.... and any others? Ferruzzi, Dennis
  • Re: [DISCUSS] removing pickling of executor config.... and any others? Vikram Koka
  • Re: [DISCUSS] removing pickling of executor config.... and any others? Amogh Desai
• [VOTE] February 2025 PR of the Month Briana Okyere
  • Re: [VOTE] February 2025 PR of the Month Jed Cunningham
  • Re: [VOTE] February 2025 PR of the Month Jens Scheffler
  • Re: [VOTE] February 2025 PR of the Month Jarek Potiuk
  • Re: [VOTE] February 2025 PR of the Month Vikram Koka
  • Re: [VOTE] February 2025 PR of the Month Wei Lee
  • Re: [VOTE] February 2025 PR of the Month Ankit Chaurasia
  • Re: [VOTE] February 2025 PR of the Month Amogh Desai
  • Re: [VOTE] February 2025 PR of the Month Pierre Jeambrun
  • Re: [VOTE] February 2025 PR of the Month Rahul Vats
  • Re: [VOTE] February 2025 PR of the Month Ryan Hamilton
  • Re: [VOTE] February 2025 PR of the Month Pavankumar Gopidesu
  • Re: [VOTE] February 2025 PR of the Month Vishnu Chilukoori
  • RE: [VOTE] February 2025 PR of the Month Blain David
  • Re: [VOTE] February 2025 PR of the Month Brent Bovenzi
  • Re: [VOTE] February 2025 PR of the Month Shahar Epstein
  • Re: [VOTE] February 2025 PR of the Month Shahar Epstein
• Apache - GSOC'25 projects / Contributions D. Mohith Akshay
  • Re: Apache - GSOC'25 projects / Contributions Bishundeo, Rajeshwar
  • Re: Apache - GSOC'25 projects / Contributions Ryan Hatter
• Two Hard Things: Deadline Alerts Edition Ferruzzi, Dennis
  • Re: Two Hard Things: Deadline Alerts Edition Jarek Potiuk
  • Re: Two Hard Things: Deadline Alerts Edition Tzu-ping Chung
  • Re: Two Hard Things: Deadline Alerts Edition Vincent Beck
  • Re: Two Hard Things: Deadline Alerts Edition Akash Sharma
  • Re: Two Hard Things: Deadline Alerts Edition Mehta, Shubham
  • Re: Two Hard Things: Deadline Alerts Edition Jarek Potiuk
  • Re: Two Hard Things: Deadline Alerts Edition Ferruzzi, Dennis
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Wei Lee
  • Re: Two Hard Things: Deadline Alerts Edition Amogh Desai
  • Re: Two Hard Things: Deadline Alerts Edition Pavankumar Gopidesu
  • Re: Two Hard Things: Deadline Alerts Edition Ankit Chaurasia
  • Re: Two Hard Things: Deadline Alerts Edition Ash Berlin-Taylor
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Jarek Potiuk
  • Re: Two Hard Things: Deadline Alerts Edition Daniel Standish
  • Re: Two Hard Things: Deadline Alerts Edition Ferruzzi, Dennis
• [Meeting Notes] Airflow 3.0 dev call - 20 Feb 2025 Vikram Koka
  • Re: [Meeting Notes] Airflow 3.0 dev call - 20 Feb 2025 Amogh Desai
• [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Jarek Potiuk
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Jarek Potiuk
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
  • Re: [DISCUSS] New Provider for Gremlin Jarek Potiuk
  • Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
  • Re: [DISCUSS] New Provider for Gremlin Jarek Potiuk
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • Re: [DISCUSS] New Provider for Gremlin Paul King
  • Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
  • Re: [DISCUSS] New Provider for Gremlin Ahmad Farhan
  • RE: Re: [DISCUSS] New Provider for Gremlin Stephen Mallette
• [VOTE] Airflow Providers prepared on February 21, 2025 Elad Kalif
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Jens Scheffler
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Oliveira, Niko
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Amogh Desai
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Jarek Potiuk
  • Re: [VOTE] Airflow Providers prepared on February 21, 2025 Vishnu Chilukoori
• [DISCUSS] Proposal to enhance the PR template Amogh Desai
  • Re: [DISCUSS] Proposal to enhance the PR template Ankit Chaurasia
  • Re: [DISCUSS] Proposal to enhance the PR template Daniel Standish
  • Re: [DISCUSS] Proposal to enhance the PR template Daniel Standish
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
  • Re: [DISCUSS] Proposal to enhance the PR template Wei Lee
  • Re: [DISCUSS] Proposal to enhance the PR template Amogh Desai
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
  • Re: [DISCUSS] Proposal to enhance the PR template Ferruzzi, Dennis
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
  • Re: [DISCUSS] Proposal to enhance the PR template Ferruzzi, Dennis
  • Re: [DISCUSS] Proposal to enhance the PR template Ferruzzi, Dennis
  • Re: [DISCUSS] Proposal to enhance the PR template Amogh Desai
  • Re: [DISCUSS] Proposal to enhance the PR template Ferruzzi, Dennis
  • Re: [DISCUSS] Proposal to enhance the PR template Jarek Potiuk
• 📢 Apache Airflow 3.0.0apha4 is available for testing! 🎉 Jed Cunningham
  • Re: 📢 Apache Airflow 3.0.0apha4 is available for testing! 🎉 Vikram Koka
• [REMINDER]: Airflow 3 Dev call on 20th February - agenda Vikram Koka
  • Re: [REMINDER]: Airflow 3 Dev call on 20th February - agenda Jarek Potiuk
• [DISCUSS] Python 3.13 support Jarek Potiuk
  • Re: [DISCUSS] Python 3.13 support Jarek Potiuk
  • RE: [DISCUSS] Python 3.13 support Damian Shaw
  • Re: [DISCUSS] Python 3.13 support Tzu-ping Chung
  • RE: [DISCUSS] Python 3.13 support Damian Shaw
  • Re: [DISCUSS] Python 3.13 support Jarek Potiuk
  • Re: [DISCUSS] Python 3.13 support Jarek Potiuk
• [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jarek Potiuk
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jarek Potiuk
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Daniel Standish
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jed Cunningham
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jens Scheffler
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jarek Potiuk
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Buğra Öztürk
  • Re: [DISCUSS] Getting rid of regular expressions (and getting rid of re2 as result of it) ? Jarek Potiuk
• [DISCUSS] Time to say goodbye to the old UI? Jed Cunningham
  • Re: [DISCUSS] Time to say goodbye to the old UI? Wei Lee
  • Re: [DISCUSS] Time to say goodbye to the old UI? Amogh Desai
  • Re: [DISCUSS] Time to say goodbye to the old UI? Shubham Raj
  • Re: [DISCUSS] Time to say goodbye to the old UI? Rahul Vats
  • Re: [DISCUSS] Time to say goodbye to the old UI? Ankit Chaurasia
  • Re: [DISCUSS] Time to say goodbye to the old UI? Abhishek Bhakat
  • Re: [DISCUSS] Time to say goodbye to the old UI? Michał Modras
  • Re: [DISCUSS] Time to say goodbye to the old UI? Ash Berlin-Taylor
  • Re: [DISCUSS] Time to say goodbye to the old UI? Michał Modras
  • Re: [DISCUSS] Time to say goodbye to the old UI? Abhishek Bhakat
  • Re: [DISCUSS] Time to say goodbye to the old UI? Jed Cunningham
  • Re: [DISCUSS] Time to say goodbye to the old UI? Vincent Beck
  • Re: [DISCUSS] Time to say goodbye to the old UI? Vikram Koka
  • Re: [DISCUSS] Time to say goodbye to the old UI? Kaxil Naik
  • Re: [DISCUSS] Time to say goodbye to the old UI? Karthikeyan
  • Re: [DISCUSS] Time to say goodbye to the old UI? Ferruzzi, Dennis
  • Re: [DISCUSS] Time to say goodbye to the old UI? Brent Bovenzi
  • Re: [DISCUSS] Time to say goodbye to the old UI? Brent Bovenzi
  • Re: [DISCUSS] Time to say goodbye to the old UI? Jarek Potiuk
  • Re: [DISCUSS] Time to say goodbye to the old UI? Buğra Öztürk
  • Re: [DISCUSS] Time to say goodbye to the old UI? Pavankumar Gopidesu
  • Re: [DISCUSS] Time to say goodbye to the old UI? Jed Cunningham
  • Re: [DISCUSS] Time to say goodbye to the old UI? Jarek Potiuk
  • Re: [DISCUSS] Time to say goodbye to the old UI? Constance Martineau
• Re: Airflow should deprecate the term "DAG" for end users Wei Lee
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Omkar P
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Aritra Basu
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Wei Lee
  • Re: Airflow should deprecate the term "DAG" for end users Daniel Imberman
  • Re: Airflow should deprecate the term "DAG" for end users Ash Berlin-Taylor
  • Re: Airflow should deprecate the term "DAG" for end users Wei Lee
  • Re: Airflow should deprecate the term "DAG" for end users Ephraim Anierobi
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Constance Martineau
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Brent Bovenzi
  • Re: Airflow should deprecate the term "DAG" for end users Ambika Garg
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Brian Greene
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Brian Greene
  • Re: Airflow should deprecate the term "DAG" for end users Daniel Standish
  • Re: Airflow should deprecate the term "DAG" for end users Daniel Standish
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Jens Scheffler
  • Re: Airflow should deprecate the term "DAG" for end users Ferruzzi, Dennis
  • Re: Airflow should deprecate the term "DAG" for end users Ryan Hatter
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Jarek Potiuk
  • Re: Airflow should deprecate the term "DAG" for end users Vikram Koka
• [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Alexander Shorin
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Vincent Beck
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Amogh Desai
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ash Berlin-Taylor
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ash Berlin-Taylor
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ash Berlin-Taylor
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ash Berlin-Taylor
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Ferruzzi, Dennis
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Oliveira, Niko
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Vincent Beck
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jarek Potiuk

• Earlier messages
• Later messages