Stay on supported Go versions #3744
Comments
|
/sig release architecture |
|
/assign |
|
/milestone v1.27 |
|
/stage stable |
|
Hello @liggitt 👋, v1.27 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would need to update the following:
The status of this enhancement is marked as |
|
The linked PR has lgtm/approve from sig approvers, shadow PRR is complete and it's waiting for an ack from @johnbelamaric.
This KEP is a process KEP, so the answer to almost every PRR question is "no" or "n/a", but sure, I pushed an update to add the new question. As an aside, I copied the KEP template on January 17th... it looks like the template was modified to add that question about a week ago in #3783. It's very frustrating to make the questions that need answering a moving target a handful of days before enhancements freeze. @wojtek-t, would it be possible for PRR to batch updates to the KEP template by the .0 release, to avoid churn for folks working on KEPs for the upcoming release (and avoid churn for release folks checking bookkeeping for every KEP for the upcoming release)? |
|
@liggitt I missed that question as well, to be honest, so I was also caught off-guard since the KEPs I was reviewing seemed to be up-to-date, this is why I explicitly mentioned that question, it was indeed not present even if KEPs that were done very recently :( Thank you for adding that question, that covers everything once #3749 is merged (but I will take another look then). |
|
Hi @liggitt , thank you for your work on this. Here's where this enhancement currently stands (and this is for
This being a process enhancement, I'm assuming (with the information I have right now) that the graduation and PRR are perfectly adequate as-is, since this is either done or not done. With that, I'm marking this as meeting all the requirements to be tracked for v1.27. Thanks! /label tracked/yes |
|
The Kubernetes project currently lacks enough 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 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 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 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-sigs/prow repository. |
Enhancement Description
k/enhancements) update PR(s):k/k) update PR(s):kubernetes/release,kubernetes/community) update PR(s):k/website) update PR(s):The text was updated successfully, but these errors were encountered: