potiuk commented on PR #39908: URL: https://github.com/apache/airflow/pull/39908#issuecomment-2164664097
WHY: This is generally a `serious deployment` change for a number of users - but since it's a deployment and not `DAG authoring` change, it's likely a good candidate for one of the Airlfow 3 incompatibilities. But we now need to seriously plan what is in and out of Airflow 3 incompatibilities, and if our plan is to make a backwards-incompatible change in Airflow 3, we should warn our users before (via deprecations) and make sure this is captured in our Airflow 3 discussions. I think it would be good to have someone who will be "championing" that - i.e. making sure it's remembered, properly docuemented, good warnings raised and people are aware of this as incompatibility - each of the "workstreams" there will have a lead/champion so having someone who will be advocating and leading that through Airlfow 3 transition (with all the consequences/documentation/making sure that it's properly communicated to our users and that there is a transition plam, including some guidelines of what our users should do) is a good idea. -- 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]
