Hello everyone, I apologize for the inconvenience, but I have to reschedule the Airflow Issue Triage process meeting from this Wednesday to next week. I hope that works for you.
In the meantime, here is an update on the metrics from last week. - *Issue metrics: * - The results on "bugs" (issues of kind:bug) going back to Dec 1, 2020 can be seen at Airflow issue tracking charts <https://docs.google.com/spreadsheets/d/1_B6L2rG5SRAXSX7V7q3o0MRF68wgU1ipCHOUjv_NqPc/edit#gid=1550616951> . - Here is a quick summary of all open bugs reported after Dec 1, 2020 summarized by separately releasable artifacts: - Core 2.x bug 59 Core 1.x bug 27 Providers 31 Kubernetes 23 Upgrade-check 4 Production image 1 CI 4 Dev-tools 1 Dependencies 0 Helm chart 3 pending-response 22 Total = 175 - In the above, Kubernetes bugs are being called since they cross-over between the Kubernetes Executor, the KubePodOperator, and sometimes with Helm chart dependencies. - From the above "Airflow Core" bugs (for both 2.x and 1.x releases) here is the quick breakdown: - API 5 Auth 6 CLI 1 Core Operators 5 Logging 7 Monitoring 1 Serialization 1 Scheduler / Executor 21 UI 8 Upgrade 1 Webserver 1 Other 27 Uncategorized 2 Total = 86 - In the above, the "Other" category consists of issues reported in Core Airflow but could not be broken down into a specific component at this time. These are sometimes related to examples, or DAG execution issues based on the kind of input given as arguments to the DAG, etc. - Core Operators refers to Operators which are bundled into the Core Airflow release such as the BashOperator and PythonOperator. Next meeting details: *Date*: April 14th *Time*: 8.30-9.30 AM Pacific / 4.30 PM GMT *Zoom link*: https://astronomer.zoom.us/j/91979682731?pwd=bWNoTFM3ajRidUlzL25RMXZ4WU96Zz09 <https://www.google.com/url?q=https://astronomer.zoom.us/j/91979682731?pwd%3DbWNoTFM3ajRidUlzL25RMXZ4WU96Zz09&sa=D&source=calendar&ust=1614129343896000&usg=AOvVaw0bgjByDAtA3eNW1BX_H21R> Best regards, Vikram
