What language does this apply to?
Whole repo
Describe the problem you are trying to solve.
For example, the commit 3d4adad has multiple tags, such as v31.0, v4.31.0, and v6.31.0.
Looking at the documentation regarding versioning, the intent seems to be that major version sare language specific: only the minor & patch numbers (31.0 in this case) are common across all languages.
However, having repo-wide tags, even for the same commit, with versions that should be language specific is confusing, especially to newcomers (like me)
For example: 'Is this 4.31 or 6.31?', 'a more recent commit (f5de0a0) has a lower major number (v3.29.5) what is the ordering between them?' etc.
Describe the solution you'd like
The repo only uses minor/patch versions as tags/releases (v31.0, etc)
Describe alternatives you've considered
If necessary, then please at least add the language name to the tag (e.g. v6.31.0-cpp instead of v6.31.0) to clarify that the version tag is not repo-wide.
Additional context
N/A
What language does this apply to?
Whole repo
Describe the problem you are trying to solve.
For example, the commit 3d4adad has multiple tags, such as v31.0, v4.31.0, and v6.31.0.
Looking at the documentation regarding versioning, the intent seems to be that major version sare language specific: only the minor & patch numbers (
31.0in this case) are common across all languages.However, having repo-wide tags, even for the same commit, with versions that should be language specific is confusing, especially to newcomers (like me)
For example: 'Is this 4.31 or 6.31?', 'a more recent commit (f5de0a0) has a lower major number (v3.29.5) what is the ordering between them?' etc.
Describe the solution you'd like
The repo only uses minor/patch versions as tags/releases (
v31.0, etc)Describe alternatives you've considered
If necessary, then please at least add the language name to the tag (e.g.
v6.31.0-cppinstead ofv6.31.0) to clarify that theversiontag is not repo-wide.Additional context
N/A