You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/11/22 19:36:07 UTC

[GitHub] [airflow] ferruzzi commented on pull request #19725: Adjust built-in base_aws methods to avoid Deprecation warnings

ferruzzi commented on pull request #19725:
URL: https://github.com/apache/airflow/pull/19725#issuecomment-975855003


   @potiuk   I'd ask you 😛       Basically the same thing John said.   I've seen some deprecation warning in other places in the provider packages as well.  
   
   It looks like these were flagged for deprecation a couple months ago in https://github.com/apache/airflow/commit/867e9305f08bf9580f25430d8b6e84071c59f9e6  What's Airflow's policy on this?  How long do we support something after a deprecation warning is pushed?  I presume it's there until the next major version of the provider package?
   
   If they were flagged as deprecated without an actual plan to follow though with removing them, then I guess that's an Issue to tack onto the list?


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org