potiuk commented on PR #26486: URL: https://github.com/apache/airflow/pull/26486#issuecomment-1307274296
I think we actually differ in assesment whether the current situation is bad or not. It's not at all obvious. I personally think the current situation is not bad. And yes, absolutely. I think it should be discussed in the devlist whether we should change it and in which direction before we do any action. I searched the root cause of this. Converting most of our examples to Functional examples have been done based on this issue https://github.com/apache/airflow/issues/9415 (which I was not an author nor even supporter BTW :) . And many of the changes done there were approved/proposed by vairous people. I could not find any deliberate decision on doing it. I think we are just about to improve our documenatation structure: https://github.com/apache/airflow/pull/27235 and this is perfect opportunity to discuss (in the devlist) what should be general approach for taskflow/classic examples in the documentation. Changing status quo for one exmple without deliberate decision on our approach without discussing in devlist how we should generally approach it is repeating the same mistake where we implemented changes to many examples without thinking if it's good or bad. Let's not repeat the same mistake again - let's just agree on the direction we want to take before we make any change. -- 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]
