-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Closed as not planned
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.Categorizes an issue or PR as relevant to SIG Contributor Experience.
Description
Describe the issue
While going through the "development.md" file on GitHub (link: https://github.com/kubernetes/community/blob/master/contributors/devel/development.md), I came across the guidelines on how to raise performance improvement issues. The document provides information on three specific issues that are considered proper for raising performance-related concerns. After reviewing these issues, I gained a rough understanding of how such problems should be reported for performance testing. However, I couldn't find any information regarding the improper ways to publish these issues. It would be helpful to have a list of improper issues as well, as it would provide clarity to readers.
That can be added below this section

Metadata
Metadata
Assignees
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.Categorizes an issue or PR as relevant to SIG Contributor Experience.