potiuk commented on issue #46569: URL: https://github.com/apache/airflow/issues/46569#issuecomment-2655034867
> Thanks for your comment! I’ve also subscribed to the dev list and will participate in the discussions on provider releases. Also you can add your questions and concerns in the #release-management of Airlfow Slack (see community page in Airflow website). Generally - you have to remember that we are all volunteers here - even if some of us have jobs related to Airflow. And if you care about somethign in airflow - asking them to take additional responsibility on things you thinnk are important is not the best way. The best way is that you take the responsibility on your own shoulders, follow up and respond and take part in release proces. Which I heartily encourage @MikhailKulikov-db :). So ... if you care, from now on make sure you watch all related communication and make sure others (including release manager) will not make mistakes and miss it. It's on your shoulders, now to follow up and monitor it's followed. -- 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]
