potiuk commented on issue #40382: URL: https://github.com/apache/airflow/issues/40382#issuecomment-2186049396
BTW. And just to clarify - as per definition of the ASF release manager's job is purely mechanical (+ single-handedly make decision to exclude certain provides based on the assessment of bug description provided by those who test it). See also here: https://infra.apache.org/release-publishing.html#releasemanager The release manager releases whatever the community decided to merge as "ready to be released". In case of providers "main" is the "ready for release sign" so when you are marking your PR as "ready to be merged" and it passes all tests as an author you are saying "it's ready to be release". That's why also in those "Status of the providers" issue we mark the authors, so that they can verify **just before the release** if there are no blocking bugs. See https://github.com/apache/airflow/issues/40382#issuecomment-2185793983 where @kacpermuda is still evaluating the impact for openlineage provider. But again - this is for bugs only. What goes into the next release is decided at merge time. See also https://github.com/apache/airflow/blob/main/PROVIDERS.rst#community-providers-release-process- where the release process and various aspects of it are explained. -- 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]
