Quick question, for a release, would you rather go...
# team-maintainers
m
Quick question, for a release, would you rather go for a
1.2.3
tag or a
v1.2.3
tag?
m
doesn’t matter IMO, as long as it’s consistent across pipelines
m
I agree with you
I think most pipelines go the
1.2.3
way, should we make it a rule for all future releases?
m
isn’t that already a rule/convention? The template adds a
v
prefix wherever the version is printed
👍 1
👍🏻 1
m
convention probably, rule not sure
m
If it’s not in the guidelines, then it should definitly be added, that way we avoid stuff like https://github.com/nf-core/pacvar/issues/15
m
Release version tags must be numerical only (no v prefix) and should follow semantic versioning rules: [major].[minor].[patch]
m
Good!