dev  

Messages by Thread

• • 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
• [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
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jens Scheffler
  • Re: [DISCUSS] Turn "tests_common" into separate distribution for development Jens Scheffler
• [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Aritra Basu
  • Re: [DISCUSS] Tests structure for providers Jens Scheffler
  • Re: [DISCUSS] Tests structure for providers Ash Berlin-Taylor
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Ash Berlin-Taylor
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Rahul Vats
  • Re: [DISCUSS] Tests structure for providers Buğra Öztürk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Buğra Öztürk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Ferruzzi, Dennis
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Ferruzzi, Dennis
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
  • Re: [DISCUSS] Tests structure for providers Ferruzzi, Dennis
  • Re: [DISCUSS] Tests structure for providers Jarek Potiuk
• [DISCUSS] Next steps in provider's sub-projects separation Jarek Potiuk
• [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Constance Martineau
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jens Scheffler
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jarek Potiuk
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jens Scheffler
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jarek Potiuk
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jed Cunningham
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Jens Scheffler
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Oliveira, Niko
  • Re: [DISCUSS] Mark Multi Exec Config as stable and remove old hardcoded hybrid execs Amogh Desai
• 📢 Apache Airflow 3.0.0alpha3 is available for testing! 🎉 Utkarsh Sharma
  • Re: 📢 Apache Airflow 3.0.0alpha3 is available for testing! 🎉 Vikram Koka
  • Re: 📢 Apache Airflow 3.0.0alpha3 is available for testing! 🎉 Jarek Potiuk
  • Re: 📢 Apache Airflow 3.0.0alpha3 is available for testing! 🎉 Amogh Desai
• [DISCUSS]: Proposing a "common message queue" abstraction Vikram Koka
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Wei Lee
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Abhishek Bhakat
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Ben Tallman
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Jarek Potiuk
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Jens Scheffler
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Vikram Koka
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Igor Kholopov
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Amogh Desai
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Mehta, Shubham
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Vishnu Chilukoori
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Ankit Chaurasia
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Mehta, Shubham
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Vincent Beck
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Pierre Jeambrun
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Constance Martineau
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Ephraim Anierobi
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Rahul Vats
  • Re: [DISCUSS]: Proposing a "common message queue" abstraction Idris Adebisi
• Updating "zombie task" terminology to "task heartbeat timeout" Karen Braganza
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Ryan Hatter
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Wei Lee
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" kalyan reddy
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Jarek Potiuk
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Abhishek Bhakat
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Daniel Standish
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Mehta, Shubham
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Ryan Hatter
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Mehta, Shubham
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Amogh Desai
  • Re: Updating "zombie task" terminology to "task heartbeat timeout" Kunal Bhattacharya
• [ANNOUNCE] Apache Airflow 2.10.5 Released Utkarsh Sharma
• [RESULT][VOTE] Release Airflow 2.10.5 from 2.10.5rc1 Utkarsh Sharma
• [ANNOUNCE] All providers moved to the new provider's structure ! Jarek Potiuk
  • Re: [ANNOUNCE] All providers moved to the new provider's structure ! Aritra Basu
  • Re: [ANNOUNCE] All providers moved to the new provider's structure ! Zhe You Liu
  • Re: [ANNOUNCE] All providers moved to the new provider's structure ! Amogh Desai
  • Re: [ANNOUNCE] All providers moved to the new provider's structure ! Buğra Öztürk
  • Re: [ANNOUNCE] All providers moved to the new provider's structure ! Shahar Epstein
  • Re: [ANNOUNCE] All providers moved to the new provider's structure ! Vikram Koka
  • Re: [ANNOUNCE] All providers moved to the new provider's structure ! Pavankumar Gopidesu
• [DISCUSS] Better CODEOWNERS - reflecting actual "interest" and "committment" in certain areas Jarek Potiuk
  • Re: [DISCUSS] Better CODEOWNERS - reflecting actual "interest" and "committment" in certain areas Jens Scheffler
  • Re: [DISCUSS] Better CODEOWNERS - reflecting actual "interest" and "committment" in certain areas Amogh Desai
  • Re: [DISCUSS] Better CODEOWNERS - reflecting actual "interest" and "committment" in certain areas Vincent Beck
  • Re: [DISCUSS] Better CODEOWNERS - reflecting actual "interest" and "committment" in certain areas Wei Lee
  • Re: [DISCUSS] Better CODEOWNERS - reflecting actual "interest" and "committment" in certain areas Mehta, Shubham
  • Re: [DISCUSS] Better CODEOWNERS - reflecting actual "interest" and "committment" in certain areas Buğra Öztürk
• [ANNOUNCE] Apache Airflow Providers prepared on February 04, 2025 Jarek Potiuk
• [RESULT][VOTE] Airflow Providers - release of February 04, 2025 Jarek Potiuk
• Unsubscribe me Konstantinos Daniilidis
  • Re: Unsubscribe me Ferruzzi, Dennis
• [ANNOUNCE] Minutes and Recording from February 2025 Airflow Monthly Town Hall Briana Okyere
• Airflow 3 min python version to 3.10 early? Ash Berlin-Taylor
  • Re: Airflow 3 min python version to 3.10 early? Jarek Potiuk
  • Re: Airflow 3 min python version to 3.10 early? Ash Berlin-Taylor
  • Re: Airflow 3 min python version to 3.10 early? Jens Scheffler
  • Re: Airflow 3 min python version to 3.10 early? Jarek Potiuk
  • Re: Airflow 3 min python version to 3.10 early? Jens Scheffler
  • Re: Airflow 3 min python version to 3.10 early? Jarek Potiuk
• [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Blain David
  • Re: [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Jarek Potiuk
  • Re: [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Ash Berlin-Taylor
  • Re: [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Jarek Potiuk
  • RE: [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Blain David
  • Re: [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Ash Berlin-Taylor
  • Re: [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Jens Scheffler
  • Re: [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Jarek Potiuk
  • Re: [PROPOSAL] Remove creation of real Airflow connections in provider unit tests Shahar Epstein

• Earlier messages
• Later messages