[GitHub] [airflow] vikramkoka commented on issue #11879: Describe how pip and versioning interacts with the provider versions.

[GitBox <gi...@apache.org>]

vikramkoka commented on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-722684511


   @potiuk 
   Here are the questions that I have seen come up and please let me know if I should be adding these to a document some place instead of here. 
   
   Q. When upgrading to a new Airflow version such as 2.0, but possibly 2.0.1 and beyond, is the best practice to also upgrade provider packages at the same time? 
   
   Q. I have an Airflow version (1.10.12) running and it is stable. However, because of a Cloud provider change, I would like to upgrade the provider package. If I don't need to upgrade the Airflow version anymore, how do I know that this provider version is compatible with my Airflow version? 
   
   Q. I have an older version of my provider package which we have lightly customized and is working fine with my MSSQL installation. I am upgrading my Airflow version. Do I need to upgrade my provider, or can I keep it as it is. 
   
   
   
   
   
   I hope this helps, will be happy to clarify and add more as I encounter them. 
   


----------------------------------------------------------------
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.

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