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

Seeking consensus on 3rd party content in documentation #1326

Closed
sftim opened this issue Oct 20, 2019 · 4 comments
Closed

Seeking consensus on 3rd party content in documentation #1326

sftim opened this issue Oct 20, 2019 · 4 comments
Labels
sig/docs Categorizes an issue or PR as relevant to SIG Docs. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@sftim
Copy link
Contributor

sftim commented Oct 20, 2019

Enhancement Description

  • One-line enhancement description (can be used as a release note): [Reach and] document a consensus on what types of third party content are appropriate for inclusion in Kubernetes documentation
  • Kubernetes Enhancement Proposal: TBD
  • Primary contact (assignee): @STIM
  • Responsible SIGs: SIG Docs
  • Enhancement target (which target equals to which milestone): n/a

/sig docs

@k8s-ci-robot k8s-ci-robot added the sig/docs Categorizes an issue or PR as relevant to SIG Docs. label Oct 20, 2019
@mrbobbytables mrbobbytables added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Oct 29, 2019
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Jan 14, 2020

Hey there @sftim -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha|beta|stable in 1.18?
The current release schedule is:
Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released
To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined.
If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍
We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements
Thanks!

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Jan 21, 2020

As a reminder @sftim :

Tuesday, January 28th EOD PST - Enhancements Freeze

Enhancements Freeze is in 7 days. If you seek inclusion in 1.18 please update as requested above.

Thanks!

@zacharysarah
Copy link
Contributor

zacharysarah commented Mar 18, 2020

Closed by #1327.

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 18, 2020

@zacharysarah: Closing this issue.

In response to this:

Closed by #1327.

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/docs Categorizes an issue or PR as relevant to SIG Docs. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

No branches or pull requests

5 participants