potiuk edited a comment on pull request #14477: URL: https://github.com/apache/airflow/pull/14477#issuecomment-786669625
> I do not believe we ever said we would _only_ release providers in batches. I can't find any reference to such a decision in the (admittedly very terse) dev meeting notes, nor AIP-8. Yes. We agreed that we CAN release them separately if there is an actual need to deviate from a regular schedule by default and that we release all providers in batches due to efficiency and overhead for voting process. That's why in my first comment I asked what is justification for releasing it out-of-bands. > Following the question before - Why not also release other providers? There were some changes in other providers as well and we initially discussed releasing 'batches' of the providers every three weeks. Do you plan to have separate voting on this one and separate on the others? I'd love to understand the thinking here, why cncf.kubernetes is going to be released separately from the others. That was my first ask is no reason why cncf.kubernetes should be released separately rather than with the rest of the providers - but apparentlly discussion has deviated from that. So let me repeat again - is there any reason why cncf.kubernetes cannot be released a bit later together with other providers as we agreed before? Is there are critical problem there? If there is a critical problem - are we going also to release backport for that (when we are releasing providers - until end of March we are also releasing backports together with every batch of providers). ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
