Hey everyone,

Here is the summary of our meeting earlier this week..
Thank you all who joined the call, really appreciate it and 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:

   - From the issue flow over the last month, a good number of issues are
   being raised with Airflow 2.0. This is good to see from an adoption
   standpoint. Several issues are also related to documentation, since people
   don't necessarily know about the changes and therefore what to expect. More
   details on this below.
   - Since incoming issues are now being consistently tagged with labels,
   it is good to expand to assigning priorities as well if there is good (>
   80%) confidence and also appropriately assign them to the next patch
   release milestone. These can be reviewed by the release managers and more
   experienced members as part of the release process. This is to help make
   sure that we don't miss important issues.
   - In addition to the 2.0.x patch release cadence of every few weeks, it
   would be good to have an expectation around the cadence for Provider
   releases. Since this is generally automated, the proposal floated was to
   have Providers releases automatically created every two weeks. This would
   include changes to existing providers as well as new providers.

Here are some interesting statistics for those keeping score:

   - It has been exactly one month since we released Airflow 2.0.
   - In this month, we have had a total of 101 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+>
   ]
   - Out of these, we have 54 issues [38 open + 16 closed] reported on
   Airflow version 2.0.0.  [link
   
<https://github.com/apache/airflow/issues?page=1&q=is%3Aissue++label%3Akind%3Abug++created%3A%3E%3D2020-12-17+-label%3Ainvalid+-label%3Aduplicate+label%3Areported_version%3A2.0>
   ]
   - Which translates to: 53% of issues reported in the last month were on
   Airflow 2.0


   - Also, as Elad pointed out in our meeting:
   - Since December, we have closed 128 issues that didn't have linked PRs


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

Next meeting in 2 weeks.
*Date*: January 27th
*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

Reply via email to