dstandish opened a new pull request, #31830: URL: https://github.com/apache/airflow/pull/31830
Ok taking another crack at this. So I think I may have come up with something that would allow folks who are _interested_ in ensuring timely removal of deprecated code without overly burdening the release manager. I provide a few mechanisms for marking something as deprecated. If we are emitting a deprecation warning, we can use a wrapper that would document (1) the provider version when the code should be changed, or (2) the airflow version at which which, when it becomes the min airflow version for the provider, the code should be changed, and (3) the user who initiated the deprecation. My current thinking is the list of "pending deprecations" -- i.e. the deprecations which are due to be updated -- would be maintained by pre-commit. Then, when release manager runs generate_issue_content_providers, we would add content that would automatically tag the authors and this would give them a chance to enact the deprecations. It would not block release though. This is just a draft, but just wanted to share the thought since I picked it back up. -- 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]
