potiuk commented on PR #43021: URL: https://github.com/apache/airflow/pull/43021#issuecomment-2413833889
Yes. Crating an issue and referring to it in the comment just above the dependency (as we do for other cases like that) is the way we do it. This makes it later very easy to check "has this issue been followed? What is the status? Should we do something with it"? This is all very difficult if we do not know what's the reason of upper-binding a dependency, so our rule-of-thumb is that we never upper-bind any dependency without a comment explaining why, what is the condition of removing the binding and linking to appropriate issue. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
