> Jarek - thank you for the suggestions - those are great suggestions in > enhancing the proposal... Regarding your first point - how does deprecating > an existing feature work for Airflow? Do we need to give a grace period of a > minor or major patch over which we continue to support the feature after > marking it for deprecation? Or do we remove them right away on a major > version / minor version update?
We raise a deprecation warning. You can see a number of examples in a number of places. We cannot remove them in minor. We have not yet discussed the timeline for Airflow 3 - but that is the first time when things can get removed. > Also, do you folks have any thoughts on my last point listed in 'Other > Considerations' section? I've highlighted the section to make it easier to > identify, and I think it's an edge case that would be worth thinking about. responded in the doc. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
