Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add go module support to k8s.io/kubernetes #917

Closed
liggitt opened this issue Mar 25, 2019 · 7 comments
Closed

Add go module support to k8s.io/kubernetes #917

liggitt opened this issue Mar 25, 2019 · 7 comments
Assignees
Labels
sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status

Comments

@liggitt
Copy link
Member

liggitt commented Mar 25, 2019

Enhancement Description

Announcement:

Developer experience impact:

  • Before: dependency updates must be performed on a linux machine, took ~30 minutes, and failed frequently (~50% in unscientific local attempts)
  • After: dependency updates can be done on any OS, take ~1-2 minutes, and succeed reliably

Design updates:

Associated changes:

Documentation:

@liggitt liggitt self-assigned this Mar 25, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 25, 2019
@liggitt liggitt added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. labels Mar 25, 2019
@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 25, 2019
@liggitt liggitt added this to the v1.15 milestone Mar 25, 2019
@kacole2 kacole2 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Apr 14, 2019
@daminisatya
Copy link
Member

daminisatya commented May 18, 2019

Hey, @liggitt I'm the v1.15 docs release shadow.

Does this require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions! 😄

@liggitt
Copy link
Member Author

liggitt commented May 18, 2019

The only documentation changes are developer facing and have already merged:

@daminisatya
Copy link
Member

daminisatya commented May 27, 2019

Thank you @liggitt

@mrbobbytables
Copy link
Member

mrbobbytables commented May 28, 2019

Hi @liggitt . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

If you know this will slip, please reply back and let us know. Thanks!

@liggitt
Copy link
Member Author

liggitt commented May 28, 2019

There are no pending PRs

@kacole2
Copy link
Member

kacole2 commented Jul 5, 2019

This has graduated stable so closing it down
/milestone clear
/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jul 5, 2019

@kacole2: Closing this issue.

In response to this:

This has graduated stable so closing it down
/milestone clear
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot removed this from the v1.15 milestone Jul 5, 2019
@kacole2 kacole2 removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
None yet
Development

No branches or pull requests

5 participants