[jira] [Resolved] (YUNIKORN-1028) move master branches to pseudo versions in go.mod

["Craig Condit (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YUNIKORN-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Condit resolved YUNIKORN-1028.
------------------------------------
    Fix Version/s: 1.0.0
       Resolution: Fixed

Merged into master on core and k8shim.

> move master branches to pseudo versions in go.mod
> -------------------------------------------------
>
>                 Key: YUNIKORN-1028
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1028
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - common, shim - kubernetes
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Craig Condit
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.0.0
>
>
> The current go.mod for both the core and the k8shim point to a release tag of our own repositories. This is not correct.
> The master branches should not point to a release tag as they can move while we go through our development process. Go provides the option to use a pseudo version for this and we should stick to that for master as per this comment https://go.dev/ref/mod#pseudo-versions:
> {quote}Pseudo-versions may refer to revisions for which no [semantic version tags|https://go.dev/ref/mod#glos-semantic-version-tag] are available. They may be used to test commits before creating version tags, for example, on a development branch.
> {quote}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org