Taragolis commented on code in PR #37362: URL: https://github.com/apache/airflow/pull/37362#discussion_r1486357161
########## airflow/providers/fab/provider.yaml: ########## @@ -26,7 +26,7 @@ description: | # The provider is not yet ready to be released, we will skip it by default when preparing new release waves # For providers until we think it should be released. -state: not-ready Review Comment: I'm just wondering could we create Release Candidates for `not-ready` states, upload it to pypi but do not release final version? E.g. with this timeline: Wave Provider on YYYY-MM-DD: apache-airflow-providers-fab -> rc1 Wave Provider on YYYY-MM-DD + 2 week : apache-airflow-providers-fab -> rc2 Wave Provider on YYYY-MM-DD + 4 week : apache-airflow-providers-fab -> rc3 State: ready Wave Provider on YYYY-MM-DD + 6 week : apache-airflow-providers-fab -> rc4 -> release Or this would increase complexability of the release process? -- 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]
