Ship a Gopkg.toml

[lavalamp]

...to help dep users get the correct version of dependencies (e.g., k8s.io/apimachinery).

[sttts]

To avoid duplicated work, I have prototype code for the publishing bot to do this when a release tag from the kube repo is converted into one of the published repo. Obviously, the Gopkg.toml should not reference sha1 revisions, but tags, for client-go preferably the semver tag.

[lavalamp]

Yeah, maybe I filed this in the wrong place.

…

On Thu, Sep 7, 2017 at 11:15 AM, Dr. Stefan Schimanski < ***@***.***> wrote: To avoid duplicated work, I have prototype code for the publishing bot to do this when a release tag from the kube repo is converted into one of the published repo. Obviously, the Gopkg.toml should not reference sha1 revisions, but tags, for client-go preferably the semver tag. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnglkn4QLhq8SWJWxS3QzQDgOCHb3Lpks5sgDKFgaJpZM4PQJ-y> .

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[sttts]

/assign
/lifecycle frozen

[nikhita]

/remove-lifecycle stale

[nikhita]

We have go.mod now, so closing. :)