[
https://issues.apache.org/jira/browse/YUNIKORN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474886#comment-17474886
]
Craig Condit edited comment on YUNIKORN-1004 at 1/12/22, 9:34 PM:
------------------------------------------------------------------
I'm following this process for the 0.12.2 release, and so far, so good. I've
tagged everything as v0.12.2-1 and that has worked just fine for go
dependencies. I will plan to retag after the official release is voted on as
v0.12.2 (and leave the existing tags).
was (Author: ccondit):
I'm following this process for the 0.12.2 release, and so far, so good.
> Investigate tagging in GIT and the interaction with go modules
> --------------------------------------------------------------
>
> Key: YUNIKORN-1004
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1004
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: release
> Reporter: Chenya Zhang
> Assignee: Chenya Zhang
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
