potiuk commented on issue #39801: URL: https://github.com/apache/airflow/issues/39801#issuecomment-2627456149
> I observe a similar behavior in 2.10.4. I filled in a bug report that was unfortunately moved to 'discussion' - https://github.com/apache/airflow/discussions/46315. There is nothing wrong in a discussion being a 'diccussion` - main difference is that it is either not clear that this is an airflow isssue and author should likely try to engage otehrs or provide more information to turn it into a clear "issue" or that there are other issues already. BTW. Having somethign as "issue" also does not absolutely guarantee that it will be taken care of. It might, or might not be fixed if there is somene who will look at it and decide that they want to spend time on fixing it. That's how open-source development works. And if you are really into fixing a problem, the fastest way to fix it is to contribute a fix, second best is to find someone to do it. Otherwise it's there, waiting for someone to fix it. And the better diagnosed and clear it is, the more likely someone will take a look at it Don't mix "issues" here with "service tickets" - things are done here when somene does it. That's it. Issues and discussions just make it easier for those people to show up and fix it, so the more easy it is for them, the better chance they will. But it mostly up to authors to make it easy. Especailly in non-critical issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
