potiuk commented on code in PR #30359: URL: https://github.com/apache/airflow/pull/30359#discussion_r1152811046
########## README.md: ########## @@ -473,6 +477,38 @@ of the contributors to perform the cherry-picks and carry-on testing of the olde The availability of stakeholder that can manage "service-oriented" maintenance and agrees to such a responsibility, will also drive our willingness to accept future, new providers to become community managed. +### Suspending releases for providers + +In case a provider is found to require old dependencies that are not compatible with upcoming versions of +the Apache Airflow or with newer dependencies required by other providers, the provider's release +process can be suspended. + +This means: + +* The provider's status is set to "suspended" +* No new releases of the provider will be made until the problem with dependencies is solved +* Sources of the provider remain in the repository for now (in the future we might add process to remove them) Review Comment: > Also, it may have side effects on other suspended providers, where maintainers will be discouraged to avoid wasting time fixing dependencies at the risk of not taking their changes. IMO we need to be clear on this, the suspension will be lifted once the providers dependencies are up to date. Yep. I think it is quite clear as it is defined now: > The suspension will be lifted when the dependencies of the provider are made compatible with the Apache > Airflow and with other providers. There is no other conditions and the suspension "will" be lifted "when" -> fixing dependencies is the only condition here. -- 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]
