jedcunningham commented on PR #42658: URL: https://github.com/apache/airflow/pull/42658#issuecomment-2491574985
I think we should be critical of all "TODOs" etc that were tagged for Airflow 3. We should view them as ideas for potential changes, not hard commitments, especially when breaking changes are involved. We've been pretty lax at throwing "in AF3" around in the past (which is good imo, dream big). In this specific case, I came in and reverted a breaking change that was already merged. Then I left a breadcrumb that we should consider doing the switch when we are doing breaking changes. If I were writing it from scratch? Positional. Is it worth a breaking change for users? Maybe? But we've been more breaking-change-adverse than I imagined we would be 2 years ago, so maybe not. -- 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]
