jscheffl commented on PR #41567: URL: https://github.com/apache/airflow/pull/41567#issuecomment-2296960236
> CC: @jscheffl -> the only problem with that one is that provider's tests are not run in v2-10-test branch (by definition). > > Which I **think** is not a problem - we already gone through the exercise of fixing all db isolation test failures in providers, and it's unlilkely this will deteriorate over time. WDYT? I'd assume there is a small (but realistic) residual risk that a new provider change/feature will not be working in DB isolation mode. For this you would need to und a backpat compatability check in isolation mode on-top of the existing (to be created?) back-compatability check with Airflow 2.10 line. I think for such cases the specific provider needs to be patched. As long as the core is stable, I am happy. -- 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]
