Which uses a [Non-digit].[alpha-numeric] combination.
As the above example is from the spring framework. How do you suggest we handle such cases while comparing versions?
Originally created by @sourabhsparkala on GitHub (May 4, 2021).
Original GitHub issue: https://github.com/semver/semver/issues/697
There are cases like
- https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-dependencies/
Which uses a [Non-digit].[alpha-numeric] combination.
As the above example is from the spring framework. How do you suggest we handle such cases while comparing versions?
Do note that while SemVer is a pretty ubiquitous versioning scheme, it is not the only one around and it does not have the objective of being the reference versioning scheme for all use-cases. The Spring Framework version you are talking about here is not SemVer-compatible. As a consequence, I am not sure how to answer your question, as I am not sure how to interpret it. Are you suggesting the definition of SemVer should handle such cases?
<!-- gh-comment-id:832526054 -->
@klehelley commented on GitHub (May 5, 2021):
Do note that while SemVer is a pretty ubiquitous versioning scheme, it is not the only one around and it does not have the objective of being the reference versioning scheme for all use-cases. The Spring Framework version you are talking about here is not SemVer-compatible. As a consequence, I am not sure how to answer your question, as I am not sure how to interpret it. Are you suggesting the definition of SemVer should handle such cases?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @sourabhsparkala on GitHub (May 4, 2021).
Original GitHub issue: https://github.com/semver/semver/issues/697
There are cases like
Which uses a [Non-digit].[alpha-numeric] combination.
As the above example is from the spring framework. How do you suggest we handle such cases while comparing versions?
@klehelley commented on GitHub (May 5, 2021):
Do note that while SemVer is a pretty ubiquitous versioning scheme, it is not the only one around and it does not have the objective of being the reference versioning scheme for all use-cases. The Spring Framework version you are talking about here is not SemVer-compatible. As a consequence, I am not sure how to answer your question, as I am not sure how to interpret it. Are you suggesting the definition of SemVer should handle such cases?