[Meeting Notes] Airflow issue triage process - Call #7 - Jan 27, 2021

[Vikram Koka <vi...@astronomer.io>]

Hey everyone,

Here is the summary of our meeting yesterday.
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:

   - Elad and Paola presented the draft of the updated process document to
   the team. This will be published in the next few days.
   - General feedback is that the issue triage process is working well
   now, though there is room for improvement.
   -
   - Specifically, how do we categorize issues which are NOT a priority?
   - For example, there are Windows specific issues or MSSQL specific
   issues which are not currently a priority for the core project committers.
   - Should we tag these as "priority:low" and "milestone:someday" similar
   to how it is done in some other open source projects to indicate issues
   which are not a priority for the core project, but that others can handle
   if they desire?
   -
   - Another kind of issue, which would be nice to segregate are "todos"
   opened by some of the core committers to indicate "work to be done" as part
   of a meta-issue. These are neither bugs nor feature requests opened by the
   community and therefore don't need to be triaged and can be excluded from
   incoming issue metrics. Any objections to categorizing these?
   -
   - Finally, we would also propose to fold "enhancement requests" into
   "feature" issues, since the vast majority of all incoming issues tagged as
   "feature" are in fact "enhancements" to existing features.

Here are some interesting statistics for those keeping score:

   - It has been exactly about 6 weeks since we released Airflow 2.0.
   - During this time, we have had a total of 143 issues of type:bug
   reported in Airflow [link
   <https://github.com/apache/airflow/issues?q=is%3Aissue++label%3Akind%3Abug++created%3A%3E%3D2020-12-17+-label%3Ainvalid+-label%3Aduplicate+-label%3Aarea%3Adev-tools+-label%3Aarea%3Aci>
   ]
   - Out of these, we have 74 issues [49 open + 25 closed] reported on
   Airflow version 2.0.0.  [link
   <https://github.com/apache/airflow/issues?q=is%3Aissue++label%3Akind%3Abug++created%3A%3E%3D2020-12-17+-label%3Ainvalid+-label%3Aduplicate+-label%3Aarea%3Adev-tools+-label%3Aarea%3Aci+label%3Areported_version%3A2.0+>
   ]
   - Which translates to: 52% of issues reported in the last month were on
   Airflow 2.0


   - Also, to encourage contributions including first time contributions,
   we talked about tracking PRs and encouraging quick review and assistance
   for early contributors.
   - As it stands now (Jan 28, 2021), we have a total of 228 open PRs. Out
   of these, 87 are relatively new, created after Airflow 2.0 was released.

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

Next meeting in 2 weeks.
*Date*: February 10th
*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=1611099036290000&usg=AOvVaw3Bvkh2-jZ-eVEC2T_cbnZD>

Best regards,

Vikram