potiuk commented on PR #29785: URL: https://github.com/apache/airflow/pull/29785#issuecomment-1447003499
> I thought _all_ Airflow components in a particular major release were [more or less protected by semver](https://airflow.apache.org/docs/apache-airflow/stable/release-process.html). If the database schema is not necessarily protected by semver, does it make sense to add a caveat to https://airflow.apache.org/docs/apache-airflow/stable/release-process.html to indicate as much? This is exactly what https://github.com/apache/airflow/blob/main/docs/apache-airflow/public-airflow-interface.rst is addressing - it explains what IS and waht IS NOT covered by our intent of backwards compatibility. Database had never been intended to be backwards compatible, we just never clearly stated it. In general it is impossible to keep "ideal backwards comatibility" because no such thing exists. As extensively discussed in this devlist thread: https://lists.apache.org/thread/1by8ko8jrrp1xwxt5781bwn2tokxjodl, very nicely explained by [Hyrum's Law](https://www.hyrumslaw.com/) and very succintly explained by this XKCD comic:  So with https://github.com/apache/airflow/blob/main/docs/apache-airflow/public-airflow-interface.rs we will attempt to explain what is supposed to be seen as "Public interface of Airflow" and what is not. -- 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]
