GitHub user potiuk added a comment to the discussion: joined task always skipped
I think you are missing the point of issue vs. discussion/ Discussion is not "worse" than issue. In order to get it implemented someone has to have clarity if this is Airflow issue or not. And hopefully - discussion here will lead to that outcome. And if you see there is a related issue - you should comment there - point to that discussion, and hopefully help to reach the conclusion about the issue and it's scope. Then, somene will have to anyhow decide on their own to work on that issue. On their own. As volunteer. The fact whether it's an isue or discussion does not matter, and does not change the chance of things being worked on. This is volunteer, open-source driven project, so you should not treat issues as "list of things that needs to be done". This is basically something maintainers had enough information on to classify as issue. That's it. The fastest way to fix some problem is to contribute a PR fixing is. You are most welcome. Second best is to convince someone it's worth their time and pick their interest. Both of these can be done in issue or discussion and discussion can be converted to issue if there is enough understanding and clerity it is indeed something problematic in Airflow. GitHub link: https://github.com/apache/airflow/discussions/46315#discussioncomment-12019802 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
