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
Feature, NodeConformance, NodeFeature, and Feature Gate labels cleanup #3041
Comments
/sig node |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
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. |
/remove-lifecycle rotten |
@spiffxp: Reopened this issue. In response to this:
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. |
@rhockenbury I apologize for the last minute KEP added to be tracked. The KEP was in reviews for a long time and we lost track whether it has all the proper labels. This KEP is not a product change, just an alignment of test tags in k8s. It doesn't really have stages like alpha/beta/GA nor requires a test plan. The KEP process was suggested mostly for visibility across SIGs and scheduling of work. I sent a PR to update the status to Would it be ok to ignore other requirements and return it back to the milestone? |
hm, |
e2e.test is technically a binary artifact in the release (which, definitely gets usage, consider the conformance program for example), so it's a bit iffy IMHO EDIT: to be clear I lean towards yes this is fine, but I'm not certain. |
@SergeyKanzhelev, we'll get you answer from the PRR reviewers on Slack - https://kubernetes.slack.com/archives/CPNHUMN74/p1665177817264029 |
Based on feedback from the discussion on Slack and with #3602 merged, we have this marked as /label lead-opted-in |
Hi @SergeyKanzhelev Checking in once more as we approach the 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022. Please ensure the following items are completed:
For this enhancement, I could not locate any k/k PRs. Please plan to get PRs out for all k/k code so it can be merged up by code freeze. If you do have k/k PRs open, please link them to this issue. As always, we are here to help should questions come up. Thanks! |
Hello @SergeyKanzhelev This enhancement is marked as ‘Needs Docs’ for 1.26 release. Thank you! |
Hello Unfortunately, this enhancement did not meet requirements for code freeze. If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks! /milestone clear |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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. |
Enhancement Description
NodeConformance, NodeFeature, and Feature Gate labels cleanup
#3042
The text was updated successfully, but these errors were encountered: