planoe commented on PR #27866: URL: https://github.com/apache/airflow/pull/27866#issuecomment-1329144832
> BTW. If you want to still keep the compatibiliyt for Airlfow < 2.3. it is perfectly for fine you to do it - but then it has to be maintained and released as "Cloudera" project. Hello @potiuk, thanks for providing the details here, it is completely understood that if we want to maintain backwards compatibility, then we have to maintain the code on our own. What is not 100% clear from the documentation in our case is that Cloudera provider would be introduced with a min dependency of 2.3.0. In the case we want to maintain compatibility for older versions, we would have to open a PR with this provider against an older version of Airflow, and it would automatically be released (however only technically, only supported by the maintainer and not the community) with the next wave of provider release along with the latest version of the provider, which is supported by the community? Is this statement correct? Of course we would still have our existing Clouder-owned pip package, but it would be much easier for the users to rely onto one package name, and pip would automatically resolve to the best fitting one. -- 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]
