From 375c964f2d6f58857134714a592cb03343cbee26 Mon Sep 17 00:00:00 2001 From: Sergey B Kirpichev Date: Sat, 12 Oct 2024 00:14:42 +0300 Subject: [PATCH] Cleanup "Reporting an issue" section (#1407) * Cleanup "Reporting an issue" section Now this lists only few examples from actually available options. Closes #1403 * + restore back security item with current wording --- triage/issue-tracker.rst | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-) diff --git a/triage/issue-tracker.rst b/triage/issue-tracker.rst index 63076e7a19..b311a51a74 100644 --- a/triage/issue-tracker.rst +++ b/triage/issue-tracker.rst @@ -55,18 +55,12 @@ box above the list of bugs. If you're not already signed in to GitHub, it will ask you to do so now. First you need to select what kind of problem you want to report. The -available choices are: - -* **Bug report**: an existing feature isn't working as expected; -* **Documentation**: there is missing, invalid, or misleading documentation; -* **Enhancement**: suggest a new feature for Python; -* **Performance**: something should work faster; -* **Security**: there is a specific kind of weakness open to exploitation - through the points of vulnerability; -* **Tests**: something is wrong with CPython's suite of regression tests; -* **Discuss**: you'd like to learn more about Python, discuss ideas for - possible changes to future Python versions, track core development - discussions, or join a specific special-interest group. +available choices include, for example: + + * **Bug report**: an existing feature isn't working as expected. + * **Documentation**: there is missing, invalid, or misleading documentation. + * **Feature or enhancement**: suggest a new feature for Python. + * **Report a security vulnerability**: privately report a security vulnerability. Depending on your choice, a dedicated form template will appear. In particular, you'll notice that the last button actually takes you to