uranusjr commented on PR #25218: URL: https://github.com/apache/airflow/pull/25218#issuecomment-1192147059
pip doesn’t do semver because there is not any reasonable point it could ever bump major, and even when we need to make incompatible changes, we need drag all the users to the new version because most of the time they can’t stay on the old version (old pip might not be able to install package releases using new features). So instead we commit to emit deprecation warnings for a certain numbers of versions before comitting to the breaking change. In that sense you might be able to view every YY.X release as a major version bump, but that does not always, only _may_ contain a breaking change (22.2 doesn’t). A user is supposed to be cautious when upgrading to a new YY.X release, even if it does not contain strictly compatibility-breaking changes, but also strongly suggested to upgrade, instead of relying on backport bugfixes forever. -- 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]
