-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
annual report KEP listings are very very wrong #7847
Comments
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
Please see the group list for a listing of the SIGs, working groups, and committees available. 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. |
/area annual-reports |
The generated data is also suggestive and is designed to help SIG leads have a pre-fetched list of KEPs that they can edit when they update the Annual Report for final submission. Many leads had mentioned earlier that Annual Reports were heavy and needed to trim this and help them with information. We will make that more explicit in the section.
Separate discussion: Like the milestone section, which is suggestive and not authoritative, the annual report is also a draft one unless SIG leads submit an updated PR. It is reviewed first inside the SIG and then reviewed by the steering liaisons.
I've taken feedback on this. We will correct it for the next cycle. |
Are you going to remove the ones that don't get updated? Or will the incorrect info just stay there in that case? Adding the autogenerated data inside a comment might be better, to prevent it from being "exposed" if the report never gets updated. |
That is on the cards actually. A few months back we (steering) discussed to remove annual report drafts that were never updated. It makes more sense to not keep them.
This is a good feedback. We can do that update for the next cycle. Thanks @danwinship 🙌🏽 |
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 |
Commit 11d1a66 addressed the following two feedback:
Is it ok to close this issue as completed? OR, |
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 |
Describe the issue
Looking at https://raw.githubusercontent.com/kubernetes/community/88d47c125f9340f6d7733a3b61191591371963e9/sig-network/annual-report-2023.md, there is a big problem with the KEPs. The generator seems to have assumed that the
milestone
sections ofkep.yaml
were authoritative about what has shipped, but the documentation for that field in the templatekep.yaml
says that it is "The milestone at which this feature was, or is targeted to be, at each stage", implying that it's more about hopes and dreams. In particular, whatever generated the list of KEPs appears to have not comparedmilestone
tostage
orlatest-milestone
, and so just cheerfully declared that things like Dual Stack API Server (currently pre-alpha) and AdminNetworkPolicy (currently alpha) are now GA, merely because they had originally been targeted at being GA by now.(Also, the "this was autogenerated" comment appears in the wrong section of the template...)
The text was updated successfully, but these errors were encountered: