potiuk commented on code in PR #35492: URL: https://github.com/apache/airflow/pull/35492#discussion_r1384612799
########## dev/README_RELEASE_PROVIDER_PACKAGES.md: ########## @@ -205,6 +215,16 @@ if you only build few packages, run: breeze release-management prepare-provider-packages --package-format both PACKAGE PACKAGE .... ``` +NOTE! When you want to release a suspended provider, package for the provider will not be prepared +when you prepare all packages - you have to specifically use the provider name in a separate +command. For example to prepare documentation for suspended `qubole` provider you need to run +separately this command: + +```shell script +breeze release-management prepare-provider-packages --package-format both qubole Review Comment: According to agreed process of provider's removal process - we should make one LAST release of the provider whch includes information that the provider is not maintained any more: https://github.com/apache/airflow/blob/main/PROVIDERS.rst#removing-community-providers > One last release of the provider is done with documentation updated informing that the provider is no longer maintained by the Apache Airflow community - linking to this page. This information should also find its way to the package documentation and consequently - to the description of the package in PyPI. Both in documentation and in README that goes to PyPI. This is why we want to be able to build and release package and documentation for the suspended provider. I also considered un-suspending provider, releasing and THEN removing, but that would be rather cumbersome and involves for example rebuilding the CI image with all the provider dependencies. I decided that allowing to build docs, publish them and release suspended provider is way more reasonable approach. -- 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]
