Uploaded image for project: 'Apache YuniKorn'
  1. Apache YuniKorn
  2. YUNIKORN-1028

move master branches to pseudo versions in go.mod

    XMLWordPrintableJSON

Details

    Description

      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:

      Pseudo-versions may refer to revisions for which no semantic version tags are available. They may be used to test commits before creating version tags, for example, on a development branch.

      Attachments

        Issue Links

          is caused by

          Task - A task that needs to be done. YUNIKORN-1016 Update scheduler-interface dependency to v0.12.2-1 (core)

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. YUNIKORN-1017 Update dependencies to v0.12.2-1 (k8shim)

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. YUNIKORN-371 Document how to manage and update go mod dependencies

          • Major - Major loss of function.
          • Closed
          links to

          Web Link GitHub Pull Request #363

          Web Link GitHub Pull Request #371

          Activity

            People

              ccondit Craig Condit
              wilfreds Wilfred Spiegelenburg
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: