You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Vikram Koka <vi...@astronomer.io.INVALID> on 2021/03/27 22:58:13 UTC

[Meeting Notes] Airflow issue triage process call - Mar 24, 2021

Hello everyone,

Here is the summary of our meeting earlier this week.
Thank you all who joined the call, really appreciate your participation and
you taking the time!  Please correct anything that I missed.
To all those who did not join, please voice your opinion if you disagree
with anything.

Overall Summary
Key points discussed:

   - *Publishing the contributing process document: *
   - Paola has been working on this document based on the draft created by
   Elad and her. Please review the draft PR
   <https://github.com/apache/airflow/pull/14176/>.
   - One element discussed was the creation of a folder structure for
   contributing documentation, so that the contributions instructions for docs
   vs. providers vs. code could be simpler and self-contained. During the
   discussion, the team agreed with the concept as long as there was a top
   level 'CONTRIBUTING.rst' doc at the top level in the Github repo.
   - There were two examples discussed for this: documented in an Airflow
   issue <https://github.com/apache/airflow/issues/11180> and the Ansible
   model for doc changes
   <https://docs.ansible.com/ansible/latest/dev_guide/index.html>.



   - *Issue metrics: *
   - In the interests of making it easier for committers and contributors
   to identify issues based on areas of interest, we have been triaging them
   into component areas.
   - 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=1740918256>
   .


   - Here is a quick summary of all open bugs reported after Dec 1, 2020
   summarized by separately releasable artifacts:
   -
   Core 2.x bug 63
   Core 1.x bug 30
   Providers 34
   Kubernetes 19
   Upgrade-check 4
   Production image 1
   CI 6
   Dev-tools 2
   Dependencies 1
   Helm chart 5
   pending-response 22
   Total = 187
   - 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 4
   Auth 7
   CLI 3
   Core Operators 2
   Logging 7
   Monitoring 1
   Serialization 1
   Scheduler / Executor 20
   UI 11
   Upgrade 1
   Webserver 2
   Other 33
   Uncategorized 1
   Total = 93
   - 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.



   - *Automation*
   - Stale PRs are getting closed as a result of the fix made by Kaxil to
   the "stale bot".



   - *Next steps*
   -  Build work to make the 'doc builds' spell checks run only for changed
   files is still upcoming and is being tracked in this issue
   <https://github.com/apache/airflow/issues/11180>.
   - Continue going back beyond Dec 1, 2020 and publish similar metrics to
   include older bugs and features.
   - Help accelerate resolution of issues.


*Meeting notes*:
https://docs.google.com/document/d/1Fx46SoOnNLiqZKtrC-tOHj3zFlZfQwWuR2LRFXJnWqw/

Next meeting details:
*Date*: March 7th
*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