You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not all versioning schemes use SemVer, but their schemes are close enough in some aspects that there can be mappings between them and SemVer. In other words, one could derive the effective SemVer string from that of a foreign scheme if one has sufficient knowledge and confidence in the policies behind that foreign scheme. Such knowledge must be published; immutable; easily discoverable; associated with the given version string, and must be machine and human readable, as well as operable.
To achieve the above, I propose a standard VersionMeta tag that is, or maps to a URI to a version schema that is defined in a standard data format.
The text was updated successfully, but these errors were encountered:
Not all versioning schemes use SemVer, but their schemes are close enough in some aspects that there can be mappings between them and SemVer. In other words, one could derive the effective SemVer string from that of a foreign scheme if one has sufficient knowledge and confidence in the policies behind that foreign scheme. Such knowledge must be published; immutable; easily discoverable; associated with the given version string, and must be machine and human readable, as well as operable.
To achieve the above, I propose a standard VersionMeta tag that is, or maps to a URI to a version schema that is defined in a standard data format.
The text was updated successfully, but these errors were encountered: