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

Conformance profiles #1618

Closed
johnbelamaric opened this issue Mar 18, 2020 · 15 comments
Closed

Conformance profiles #1618

johnbelamaric opened this issue Mar 18, 2020 · 15 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@johnbelamaric
Copy link
Contributor

johnbelamaric commented Mar 18, 2020

Enhancement Description

@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 18, 2020
@johnbelamaric
Copy link
Contributor Author

johnbelamaric commented Mar 18, 2020

/sig architecture
/priority important-soon
/assign

@k8s-ci-robot k8s-ci-robot added sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 18, 2020
@johnbelamaric johnbelamaric added this to To Triage in conformance-definition via automation Mar 18, 2020
@johnbelamaric johnbelamaric moved this from To Triage to Needs Review in conformance-definition Mar 18, 2020
@spiffxp
Copy link
Member

spiffxp commented Apr 7, 2020

summary and motivation: #1619

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented May 1, 2020

Hi @johnbelamaric 😄

1.19 Enhancements shadow here. I wanted to confirm that this Enhancement will be graduating in 1.19?

In order to have this part of the release:

The KEP PR must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria.

The current release schedule is:

Monday, April 13: Week 1 - Release cycle begins
Tuesday, May 19: Week 6 - Enhancements Freeze
Thursday, June 25: Week 11 - Code Freeze
Thursday, July 9: Week 14 - Docs must be completed and reviewed
Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

Please let me know and I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

@kikisdeliveryservice kikisdeliveryservice added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 16, 2020
@kikisdeliveryservice kikisdeliveryservice added this to the v1.19 milestone May 16, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented May 16, 2020

Hi John,

I see that the underlying KEP as merged but is marked as provisional, will this be moved to implementable along with test plans by next Tuesday for inclusion in 1.19?

Thanks!

@palnabarun
Copy link
Member

palnabarun commented May 18, 2020

According to conversation with @johnbelamaric on Slack, this won't graduate it 1.19 and instead should be pushed to 1.20.

/milestone v1.20

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.19, v1.20 May 18, 2020
@palnabarun palnabarun added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 18, 2020
@fejta-bot
Copy link

fejta-bot commented Aug 16, 2020

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 Aug 16, 2020
@spiffxp
Copy link
Member

spiffxp commented Aug 24, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 24, 2020
@johnbelamaric johnbelamaric moved this from PRs Needing Review to In Progress PRs in conformance-definition Sep 11, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 11, 2020

Hi @johnbelamaric 😄

Enhancements Lead here. Is this still going for GA in 1.20?

Thanks!
Kirsten

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 25, 2020

Hey @johnbelamaric

Just wanted to double check on this for 1.20? Any plans?

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 30, 2020

As a reminder Enhancements Freeze is October 6th. This KEP is still provisional and lacks graduation criteria. If you would like to be tracked please let me know.

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Oct 7, 2020

Enhancements Freeze is now in effect. If you wish to be included in the 1.20 Release, please submit an Exception Request as soon as possible.

Best,
Kirsten
1.20 Enhancements Lead

@kikisdeliveryservice kikisdeliveryservice removed this from the v1.20 milestone Oct 7, 2020
@fejta-bot
Copy link

fejta-bot commented Jan 5, 2021

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 Jan 5, 2021
@fejta-bot
Copy link

fejta-bot commented Feb 4, 2021

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 Feb 4, 2021
@fejta-bot
Copy link

fejta-bot commented Mar 6, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 6, 2021

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/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.

conformance-definition automation moved this from In Progress PRs to Done Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Development

No branches or pull requests

6 participants