Skip to content

Commit 375c964

Browse files
authored
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
1 parent 8ec03f9 commit 375c964

File tree

1 file changed

+6
-12
lines changed

1 file changed

+6
-12
lines changed

triage/issue-tracker.rst

Lines changed: 6 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -55,18 +55,12 @@ box above the list of bugs. If you're not already signed in to GitHub, it
5555
will ask you to do so now.
5656

5757
First you need to select what kind of problem you want to report. The
58-
available choices are:
59-
60-
* **Bug report**: an existing feature isn't working as expected;
61-
* **Documentation**: there is missing, invalid, or misleading documentation;
62-
* **Enhancement**: suggest a new feature for Python;
63-
* **Performance**: something should work faster;
64-
* **Security**: there is a specific kind of weakness open to exploitation
65-
through the points of vulnerability;
66-
* **Tests**: something is wrong with CPython's suite of regression tests;
67-
* **Discuss**: you'd like to learn more about Python, discuss ideas for
68-
possible changes to future Python versions, track core development
69-
discussions, or join a specific special-interest group.
58+
available choices include, for example:
59+
60+
* **Bug report**: an existing feature isn't working as expected.
61+
* **Documentation**: there is missing, invalid, or misleading documentation.
62+
* **Feature or enhancement**: suggest a new feature for Python.
63+
* **Report a security vulnerability**: privately report a security vulnerability.
7064

7165
Depending on your choice, a dedicated form template will appear.
7266
In particular, you'll notice that the last button actually takes you to

0 commit comments

Comments
 (0)