Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Done
-
None
-
None
-
None
Description
Experiment different ways to tag in GIT and its interaction with go modules.
Discussed with wilfreds offline, as soon as we tag a release that tag is fixed and tracked from a go mod point. It cannot be changed. It creates a problem for a release candidate: it needs a special tag and that tag cannot be the real release tag due to the voting. For example, we can have something like a 1.0.0-1 tag for the build and use in go mod. Increase to -2 and -3 etc for each release candidate we build. Then we add an extra tag 1.0.0 as the official release.
Attachments
Issue Links
- relates to
-
YUNIKORN-994 update release procedure for release tagging
- Closed