potiuk commented on PR #35861: URL: https://github.com/apache/airflow/pull/35861#issuecomment-1826819752
I wonder - what others think about it. Especially those who were in Airflow when we migrated to Airflow 2. from 1.10.15. And just to add a bit more context. We did release https://pypi.org/project/apache-airflow-upgrade-check/ when we started Airflow 1.10 -> Airflow 2 version. And that was not even a migration tool, that was a checker that checked if you are ready to migrate. And my concerns are heavily based on experienced we had then. The more we limit and constraint the users, the less "black" or even "gray" box our migration tool will be, the better for any kind of issues. If we RELEASE something that looks like ready-to-use-CLI-tool, users will expect it to works as a generic tool, simply. The more we make it "do-it-yourself" solution, the more likely it is they will look inside and fix it, knowing that this is is what they are supposed to do. -- 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]
