michiel-de-muynck commented on issue #73678: URL: https://github.com/apache/airflow/issues/73678#issuecomment-6084943614
The main unresolved issue I see here still is the conflict between: * The [Airflow deprecation policy](https://airflow.apache.org/docs/apache-airflow/stable/release-process.html#deprecation-policy) promising not to make breaking changes in minor versions * The current plan of doing exactly that, for a change that actually breaks real-world code (examples: [1](https://github.com/apache/airflow/issues/73678#issuecomment-5926278647), [2](https://github.com/apache/airflow/pull/72822#issuecomment-5667520076), [3](https://github.com/apache/airflow/pull/73087#issuecomment-5808925697)) There are multiple possible solutions to this: * Update the deprecation policy to reflect reality, that semantic versioning is no longer used * Rename the planned version 3.5 to 4.0 * Make the DAG only invalid if the new features for which these DAG structures are problematic are actually used Just ignoring the discrepancy seems like the worst choice. -- 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]
