Hello here, *Tl;DR; PMC wants to introduce rotational Release Management and more regular every-2-weeks with a planned schedule.*
We've been discussing it over in private last week, and I think it's a good time to bring it in to devlist . Unfortunately Elad (who bravely and persistently Shepherded our releases for providers for Years) - will not have that much time to do it with regularity it deserves. Elad will take a little step back from those duties (but do not be afraid - Elad is still around and actively working on the Airflow Summit 2026 as we speak - some announcements about that - very, very soon !!!) Elad - with a little of my help and a lot of help from Amogh - has been taking REALLY good care about the process and continuous improvements there, so it's a breeze (pun intended) to take it over by others. >From here I think it's the right time to thank Elad for all the effort, energy into making those releases as regularly as possible and with fantastic dedication :). So - within the PMC we discussed how we want to make it work from now on. We are discussing separately how we can have even more providers, so our processes need to be scalable, robust, and prepared. I've done a few updates to the process in the last round to make it so, also the upcoming ATR (Apache Trusted Releases) platform developed in the ASF will make it easier to prepare, verify and vote on releases. In the future we might decide to modify the cadence depending on the needs, number of providers etc. We might also introduce a way how stakeholders might initiate an ad-hoc release We want to turn Provider release process into rotational release management - with several alternating release managers and *very* regular cadence of "initiating the release" (followed by rc2 etc. as needed). We want to make it very regular - every 2 weeks, Thursday. Of course with exceptions for holidays etc. - which in this case means that 26th of December one will happen a few days later :), but we still want to keep the cadence of initial release. We have now 3 release managers volunteering to take part in the rotation: Jens, Vinc, myself - and we would also love to have still one more PMC member to join us. It's a low-extra-paid (0 :) ), small effort - literally a few hours a month with rotation - job that gives no satisfaction whatsoever ;), except the pure joy of interacting with contributors, engaging and helping with reviews and testing - (yes our community is awesome ;) - so anyone is welcome :D. Sweat and blood and all that. But in reality - yeah - it's really a great way to keep in touch with the community. We prepared an initial draft of the release schedule where we will be signing up for the next releases and where anyone will be able to see what is the next day of release (we will add links to it once we undraft it - we are waiting for Vinc to come back from holidays and settle it down - and maybe one more PMC member to join the team ;) ): https://cwiki.apache.org/confluence/display/AIRFLOW/Release+Plan+DRAFT+-+TO+BE+DISCUSSED Chats/discussions on the process will happen in the #release-management channel on Slack. And once again, Thanks Elad. You are a great Shepherd. But you've done such a good job that you now need at least 3 people to fill-in for you :D J.
