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

Relocate reference generation tooling from Kubernetes Incubator #13904

Closed
4 tasks done
jimangel opened this issue Apr 20, 2019 · 4 comments · Fixed by #16632 or kubernetes-sigs/reference-docs#93
Closed
4 tasks done
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@jimangel
Copy link
Member

jimangel commented Apr 20, 2019

@mrbobbytables brought to my attention during the 1.14 cycle that the Kubernetes Incubator repo is sort of "pre-retirement."

Given that our reference-docs tooling lives there, we should consider moving it out to a SIG or Core repository described in the above link.

Also, since we rely heavily on those tools for the release process this might be a slightly larger undertaking to migrate. I don't see any need to make this an urgent priority, but wanted to open an issue for tracking.

TODO:

/cc @tengqm @zacharysarah @makoscafee

@jimangel jimangel added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 20, 2019
@zacharysarah
Copy link
Contributor

/cc @steveperry-53

@fejta-bot
Copy link

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.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 23, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 22, 2019
@mrbobbytables
Copy link
Member

/remove-lifecycle rotten
ref: kubernetes/community#1922 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants