Re: [VOTE] July 2022 PR of the Month

Might be difficult. Adding new behaviours (especially for people who have plenty to do) is difficult. I think it's better to make smart use of existing behaviours that are already happening regardless. On Tue, Jul 26, 2022 at 11:28 PM Ross Turk wrote: > > > On Jul 22, 2022, at 3:08 PM, Jarek Pot

Re: [VOTE] July 2022 PR of the Month

> On Jul 22, 2022, at 3:08 PM, Jarek Potiuk wrote: > > Side comment: I wonder when we will start employing AI to select "best pr”… For that we would need a training dataset of some sort. A big one. Perhaps we can start small by tagging PRs that are potentially noteworthy? That would be usefu

Re: [DISCUSS] Airflow Scheduling Delay Metric Definition

Sure On Tue, Jul 26, 2022 at 7:41 PM Ping Zhang wrote: > Hi Jarek, > > Thanks a lot for the thorough response and they are all legitimate > concerns. > > How about that I prepare a more thorough doc to address your concerns and > we can continue the discussion from there? > > Thanks, > > Ping >

Re: [VOTE] July 2022 PR of the Month

Ah ... too late. Also vote on this one :) On Tue, Jul 26, 2022 at 8:19 PM Michael Robinson wrote: > Hey dev list, > > A PR of the Month for the July issue of the newsletter has been chosen by > vote: > > #24989 : Implement > expand_kwargs() by @uranu

Re: [VOTE] July 2022 PR of the Month

Hey dev list, A PR of the Month for the July issue of the newsletter has been chosen by vote: #24989 : Implement expand_kwargs() by @uranusjr (2 write-in votes) Vote thread: https://lists.apache.org/thread/6x7nqr8ol5hs

Re: [DISCUSS] Airflow Scheduling Delay Metric Definition

Hi Jarek, Thanks a lot for the thorough response and they are all legitimate concerns. How about that I prepare a more thorough doc to address your concerns and we can continue the discussion from there? Thanks, Ping Thanks, Ping On Tue, Jul 26, 2022 at 6:53 AM Jarek Potiuk wrote: > If

Re: [DISCUSS] MySQL 5.7 special treatment

> Also, what's our longer term plan for MySQL 5.7 once it reaches EOL? The same we did with Python/Kubernetes - we will drop support for it. We will stop running tests on CI and remove documentation and parts of code that is specifically there to address 5.7 and the next (minor) release after that

Re: [DISCUSS] MySQL 5.7 special treatment

Hi Jarek, Thanks for bringing this up. It is a great topic to discuss. I like the first 2 options. For the 3rd option in the UI, I think it might be too much as the Airflow UI is heavily used by DE/DS, but not the admin of the clusters, or it can be in the Admin tab? Also, what's our longer ter

Re: [DISCUSS] Airflow Scheduling Delay Metric Definition

If I understand correctly, the Idea is to run an additional set of stress tests before releasing a version - without impacting the production version of Airflow. I think if this is something that we want to make part of our release process, then submitting a code somewhere is the last thing to do.