dev  

Messages by Thread

• [DISCUSS] Configuration design for REST API & UI metrics tagging Henry Chen
  • Re: [DISCUSS] Configuration design for REST API & UI metrics tagging Zhe-You(Jason) Liu
• Recap and survey results from the 6th Airflow Korea meetup Yeonguk Choo
• [VOTE] Airflow Providers, release preparation date 2026-06-16 Shahar Epstein
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-16 Aaron Chen
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-16 Henry Chen
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-16 Sameer Mesiah
• [REMINDER]: Airflow Dev call on 18th June - agenda [3.3.0 Focus] Kaxil Naik
  • Re: [REMINDER]: Airflow Dev call on 18th June - agenda [3.3.0 Focus] Kaxil Naik
  • Re: [REMINDER]: Airflow Dev call on 18th June - agenda [3.3.0 Focus] Christos Bisias
  • Re: [REMINDER]: Airflow Dev call on 18th June - agenda [3.3.0 Focus] Kaxil Naik
  • Re: [REMINDER]: Airflow Dev call on 18th June - agenda [3.3.0 Focus] Aaron Chen
• 📢 Apache Airflow 3.3.0beta1 is available for testing! 🎉 Rahul Vats
  • Re: 📢 Apache Airflow 3.3.0beta1 is available for testing! 🎉 Kaxil Naik
  • Re: 📢 Apache Airflow 3.3.0beta1 is available for testing! 🎉 Amogh Desai
  • Re: 📢 Apache Airflow 3.3.0beta1 is available for testing! 🎉 Jarek Potiuk
• [LAZY-CONSENSUS] Usage of imperative mode in commits Shahar Epstein
  • Re: [LAZY-CONSENSUS] Usage of imperative mode in commits Shahar Epstein
• [DISCUSS] Taskflow API to set a task as the dag’s “result” Tzu-ping Chung via dev
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Ephraim Anierobi
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Tzu-ping Chung via dev
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Ash Berlin-Taylor
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Vincent Beck
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Tzu-ping Chung via dev
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Ash Berlin-Taylor
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Vincent Beck
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Kaxil Naik
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Shahar Epstein
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Ash Berlin-Taylor
  • Re: [DISCUSS] Taskflow API to set a task as the dag’s “result” Tzu-ping Chung via dev
• Let's not lose the high bar Kaxil Naik
  • Re: Let's not lose the high bar Amogh Desai
  • Re: Let's not lose the high bar Jarek Potiuk
• Better paralllelism of PythonVenv/ExternalPython tests Jarek Potiuk
  • Re: Better paralllelism of PythonVenv/ExternalPython tests Jarek Potiuk
  • Re: Better paralllelism of PythonVenv/ExternalPython tests Kaxil Naik
  • Re: Better paralllelism of PythonVenv/ExternalPython tests Sameer Mesiah
  • Re: Better paralllelism of PythonVenv/ExternalPython tests Jarek Potiuk
• [ANNOUNCE] Apache Airflow Mypy 0.1.0 released Hussein Awala
• [RESULT][VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Hussein Awala
  • Re: [RESULT][VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Jarek Potiuk
  • Re: [RESULT][VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Shahar Epstein
• [ANNOUNCE] Apache Airflow Providers prepared on 2026-06-08 are released Jarek Potiuk
• [RESULT][VOTE] Airflow Providers - release preparation date 2026-06-08 Jarek Potiuk
• [DISCUSS] Promoting airflowctl to 1.0.0 Buğra Öztürk
  • Re: [DISCUSS] Promoting airflowctl to 1.0.0 Ash Berlin-Taylor
  • Re: [DISCUSS] Promoting airflowctl to 1.0.0 Buğra Öztürk
• [ANNOUNCE] Apache Airflow Go SDK v1.0.0-beta2 available for testing Zhe-You(Jason) Liu
• [DISCUSS] What do we do with unreviewed PRs - data based discussion Jarek Potiuk
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Elad Kalif
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Jarek Potiuk
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Sameer Mesiah
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Jarek Potiuk
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Amogh Desai
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Jarek Potiuk
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Ghaeli, Sean
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Ghaeli, Sean
  • Re: [DISCUSS] What do we do with unreviewed PRs - data based discussion Sameer Mesiah
• Rebase your PRs for faster CI times* Kaxil Naik
  • Re: Rebase your PRs for faster CI times* Jarek Potiuk
  • Re: Rebase your PRs for faster CI times* Amogh Desai
  • Re: Rebase your PRs for faster CI times* Jarek Potiuk
  • Re: Rebase your PRs for faster CI times* Rahul Vats
  • Re: Rebase your PRs for faster CI times* Aaron Chen
  • Re: Rebase your PRs for faster CI times* Henry Chen
  • Re: Rebase your PRs for faster CI times* Jarek Potiuk
• Quick feedback on UI for Deadlines Ghaeli, Sean
  • Quick feedback on UI for Deadlines Sameer Mesiah
  • Re: Quick feedback on UI for Deadlines Kaxil Naik
  • Re: Quick feedback on UI for Deadlines Sameer Mesiah
  • Re: Quick feedback on UI for Deadlines Kaxil Naik
  • Re: Quick feedback on UI for Deadlines Kaxil Naik
  • Re: Quick feedback on UI for Deadlines Kaxil Naik
  • Re: Quick feedback on UI for Deadlines Sameer Mesiah
  • Re: Quick feedback on UI for Deadlines Kaxil Naik
• [VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Hussein Awala
  • Re: [VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Buğra Öztürk
  • Re: [VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Jarek Potiuk
  • Re: [VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Hussein Awala
  • Re: [VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Buğra Öztürk
  • Re: [VOTE] Release Apache Airflow Mypy 0.1.0 based on 0.1.0rc2 Jens Scheffler
• Note to reviewers: Please review every PR as if it was the committers/contributtors/PMC first Ash Berlin-Taylor
  • Re: Note to reviewers: Please review every PR as if it was the committers/contributtors/PMC first Jarek Potiuk
• [VOTE] Airflow Providers, release preparation date 2026-06-08 Jarek Potiuk
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Shahar Epstein
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Niko Oliveira
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Elad Kalif
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Niko Oliveira
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Jens Scheffler
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Aaron Chen
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Wei Lee
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Jarek Potiuk
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Niko Oliveira
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Amogh Desai
  • Re: [VOTE] Airflow Providers, release preparation date 2026-06-08 Buğra Öztürk
• 💌 Airflow Summit 2026: Discover the available discounts Teyza Ponce
• Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Ash Berlin-Taylor
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Ash Berlin-Taylor
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) fm
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) 陳弘逸
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Amogh Desai
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Ash Berlin-Taylor
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Ash Berlin-Taylor
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Tzu-ping Chung via dev
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Pierre Jeambrun
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Vincent Beck
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Amogh Desai
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Shahar Epstein
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jens Scheffler
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) 김준영
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) 김준영
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) 김준영
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Przemysław Mirowski
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Kaxil Naik
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Shahar Epstein
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Kaxil Naik
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Kaxil Naik
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Shahar Epstein
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Ash Berlin-Taylor
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Przemysław Mirowski
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Przemysław Mirowski
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Sameer Mesiah
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Yeonguk Choo
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Jarek Potiuk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Kaxil Naik
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Sameer Mesiah
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Ash Berlin-Taylor
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Buğra Öztürk
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Shahar Epstein
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Przemysław Mirowski
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Sameer Mesiah
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Shahar Epstein
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Sameer Mesiah
  • Re: Discuss/proposal: Update our AI coding policy to "forbid" agents opening PRs (not banning LLM generated-code) Pierre Jeambrun
• [ANNOUNCEMENT] i18n completeness check for Airflow 3.3.0 RC Rahul Vats
• [ANNOUNCE] Apache Airflow Java SDK 1.0 SNAPSHOT prepared on 2026-06-08 is released Tzu-ping Chung via dev
  • Re: [ANNOUNCE] Apache Airflow Java SDK 1.0 SNAPSHOT prepared on 2026-06-08 is released Zhe-You(Jason) Liu
  • Re: [ANNOUNCE] Apache Airflow Java SDK 1.0 SNAPSHOT prepared on 2026-06-08 is released Jens Scheffler
  • Re: [ANNOUNCE] Apache Airflow Java SDK 1.0 SNAPSHOT prepared on 2026-06-08 is released Tzu-ping Chung via dev
• [ANNOUNCE] Apache Airflow Providers prepared on 2026-06-02 are released Jarek Potiuk
• [RESULT][VOTE] Airflow Providers - release preparation date 2026-06-02 Jarek Potiuk
• Preparing for Airflow 3.3.0 Release Rahul Vats
  • Re: Preparing for Airflow 3.3.0 Release Elad Kalif
  • Re: Preparing for Airflow 3.3.0 Release Jens Scheffler
  • Re: Preparing for Airflow 3.3.0 Release Rahul Vats
  • Re: Preparing for Airflow 3.3.0 Release Jarek Potiuk
  • Re: Preparing for Airflow 3.3.0 Release Rahul Vats
  • Re: Preparing for Airflow 3.3.0 Release Amogh Desai
  • Re: Preparing for Airflow 3.3.0 Release Jarek Potiuk
• [DISCUSS] Behavior change for get_last_dagrun and get_previous_dagrun for nullable logical_date (AIP-39) Subham Sangwan
• [ANNOUNCE] June 2026 Airflow Monthly Town Hall Recording Briana Steel via dev
  • Re: [ANNOUNCE] June 2026 Airflow Monthly Town Hall Recording Zhe-You(Jason) Liu
• [VOTE] AIP-85: DAG importer Dilnaz Amanzholova via dev
  • Re: [VOTE] AIP-85: DAG importer Jarek Potiuk
  • Re: [VOTE] AIP-85: DAG importer Jarek Potiuk
  • Re: [VOTE] AIP-85: DAG importer Dilnaz Amanzholova via dev
  • Re: [VOTE] AIP-85: DAG importer Jake McGrath via dev
  • Re: [VOTE] AIP-85: DAG importer Vikram Koka via dev
  • Re: [VOTE] AIP-85: DAG importer Igor Kholopov via dev
  • Re: [VOTE] AIP-85: DAG importer Zhe-You(Jason) Liu
  • Re: [VOTE] AIP-85: DAG importer Dilnaz Amanzholova via dev
  • Re: [VOTE] AIP-85: DAG importer Tzu-ping Chung via dev
  • Re: [VOTE] AIP-85: DAG importer Dilnaz Amanzholova via dev
  • Re: [VOTE] AIP-85: DAG importer Dilnaz Amanzholova via dev
  • Re: [VOTE] AIP-85: DAG importer Kaxil Naik
  • Re: [VOTE] AIP-85: DAG importer Dilnaz Amanzholova via dev
  • Re: [VOTE] AIP-85: DAG importer Kaxil Naik
  • Re: [VOTE] AIP-85: DAG importer Dilnaz Amanzholova via dev
• [ANNOUNCE] Apache Airflow Python Client 3.2.2 Released Rahul Vats
• [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Blain David
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Tzu-ping Chung via dev
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Jens Scheffler
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Jarek Potiuk
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Blain David
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Sameer Mesiah
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Natanel
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Ash Berlin-Taylor
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Jarek Potiuk
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Kaxil Naik
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Jarek Potiuk
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Blain David
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive David Blain
  • Re: [DISCUSS] Choose a better name for Dynamic Task Partitioning and thus the partition primitive Tzu-ping Chung via dev
• [ANNOUNCE] Apache Airflow Helm Chart version 1.22.0 Released Jarek Potiuk
• [RESULT][VOTE] Release Apache Airflow Python Client 3.2.2 from 3.2.2rc1 Rahul Vats
• [REMINDER]: Airflow Dev call on 4th June - agenda Vikram Koka via dev
• [RESULT][VOTE] Release Apache Airflow Helm Chart 1.22.0 based on 1.22.0rc1 Jarek Potiuk
• [ANNOUNCE] Apache Airflow CTl 0.1.5 from 0.1.5rc1 released Buğra Öztürk
  • [ANNOUNCE] Apache Airflow CTl 0.1.5 from 0.1.5rc1 released Buğra Öztürk
  • Re: [ANNOUNCE] Apache Airflow CTl 0.1.5 from 0.1.5rc1 released Buğra Öztürk

• Earlier messages