potiuk commented on a change in pull request #12416:
URL: https://github.com/apache/airflow/pull/12416#discussion_r525872358



##########
File path: airflow/providers/google/ADDITIONAL_INFO.md
##########
@@ -0,0 +1,26 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ -->
+
+## Additional limitations
+
+The [2020.11.13 release](#release-20201113) of this provider is only usable 
with Apache Airflow >= 1.10.12 version due to refactorings implemented in

Review comment:
       One comment here @leahecole -> I think it's not precise.
   
   The package, in general, should be usable and installable with <1.10.12 - 
only the GKEPodOperator has some problems with <1.10.12. This is because 
cncf.kubernetes provider cannot be installed on airflow < 1.10.11 (and there 
were some known issues with cncf.kubernetes + 1.10.11). The cncf.kubernetes 
backport provider is an optional cross-dependency for the google backport 
provider). So we have actually not limited the google package to >=1.10.12 - 
you can still install it with airflow 1.10.9 and it will continue to work 
(except the GKEPodOperator)




----------------------------------------------------------------
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:
[email protected]


Reply via email to