potiuk commented on PR #30727: URL: https://github.com/apache/airflow/pull/30727#issuecomment-1534576105
> @potiuk We already voted and accepted [Move K8S / Celery (and related) executors to respective providers](https://lists.apache.org/thread/4mmzwpf9zfkkx03l1rswxfmq75hzhpk4) then why do we consider waiting for 2.7? The cherry picking issue goes away once we migrate the executor to providers also it reduce the risk significantly. Providers releases are more agile. We can do them faster and scope to a very localized change. If needed yanking provider has smaller blast radius. For the very same reason. I will wait with the move to providers to be very close to cut-off-branch time. I have not had time to work on it before, the last cut-off so I decided to wait for it until the next one. Voting and approving something does not mean "let's implement it now". Timing is important. We had a number of changes and AIPs thaat have been voted and approved and they were (or even still are) waiting for good time, In fact, if anything - we should corrdinate both thing - optimisations and moving stuff to providers to be around the same time. All that I am telling is that when we decide on merging stuff we could consider not only our own needs and work but also the impact it has on others (i.e. empathy). Merging this change has the potential of making either life of our release managers or our users more difficult, at the expense of merging a change faster. Choosing the right timing to merge is all about thinking about the potential impact it might have and consciously choosing the best time, that has least potential to impact other's work. That's all what I am saying. -- 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]
