hussein-awala commented on PR #37058: URL: https://github.com/apache/airflow/pull/37058#issuecomment-1916322884
> @hussein-awala sure I can do that. Is that also what we want? Shouldn't we bump the requirements of the provider? I understand that this forces people to upgrade but the functionality won't be available or just partially? And does it make sense to have it more fine grained than the provider level? Seems to defeat the purpose of the provider minimum requirements a bit. The check is not for the whole provider, just for the module (or the class of the new XCom backend). If we keep the feature in the core package, the users will not be able to use it before 2.9.0, but after moving it to the provider and consider the core change as a bug fix, they will be able to use it starting from 2.8.2. If you believe that the XCom backend will work without the core changes, and they will just have a problem with the delete, then maybe we can skip adding the check. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
