potiuk commented on PR #25218: URL: https://github.com/apache/airflow/pull/25218#issuecomment-1192024482
> Interesting they don't include `.0`. Yep. `pypi` does not use SemVer. And while you can use .0 in the first version, th form of X.Y is generally ok for all the projects - not only PyPi https://peps.python.org/pep-0440/. And for `pip` it has some significance if you look how it works. Interesting is that the PEP acknowldeges SemVer as "almost compatible" scheme and one that is "wortth looking at as it solves some problems" but "more strict" than the versioning of `pypi` repository and with slight incompatibilities (but it shows how those can be made compatible - and we are actually following it. The versioning/release/cadence of PIp is a very different from ours: https://pip.pypa.io/en/stable/development/release-process/?highlight=deprecation#deprecation-policy @uranusjr might say more and correct me but from what I understand: * no SemVer - there is completely no releation between version and wheteer it is backwards compatible or not and whether it hass any features. (however patchlevel indicates bugfix) * it's really not obvious (and not mentioned in the doc) how the numbers are assigned (or I could not find it stated explicitly) but following the [changelog](https://pip.pypa.io/en/stable/news/?highlight=versioning#v18-0) note, the version of Pypi seems to be really a variant of calver-with-bugfix (even calver mentions it here https://calver.org/). The 22.2 means second relase in 2022. And relases are quarterly ones (unless there are no new features - then release can be skipped - but I am not entirely sure if it means that .2 is missing or whether .2 will be in 3rd quarter (I assume it will be skipped in such case). The interesting thing is that deprecations are removed after minimum 6 months and you should track the documentation to know what is removed when. And some fast-track-changes can have 3 months deprecation. BTW. I am not judging what's good/bad :). It's just very different from our versioning. This is just description of how I understand it works. -- 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]
