potiuk commented on PR #36391: URL: https://github.com/apache/airflow/pull/36391#issuecomment-1874605531
> Quick question: why marking fab provider as not ready? To me, the code migration is done and the only remaining piece is https://github.com/apache/airflow/pull/36232 but no breaking change is expected now onwards in fab provider. Not ready is only used to skip the package from being released. The thing is that we do not want to release FAB provider **just yet**. And when we prepare providers for release we prepare all packages that are eligible to be released. But it makes no sense to relase FAB yet - as we might find bugs and issues that make such relased package not really suitable and we will have to yank them. We had somewhat similar problem with common.io which we released quite a bit too early as it had some breaking changes that made them unusable. Result: <img width="1322" alt="Screenshot 2024-01-02 at 22 43 16" src="https://github.com/apache/airflow/assets/595491/44aad36a-01d1-4f2f-ad7a-1d6a8f97d289"> I think we should removre the "not-ready" flag some two weeks before Airflow 2.9 alpha/beta relase, to give us enough time to relase it in the regular provider's wave a week/two before Airflow needs it. -- 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]
