Skip to content

Commit df81d28

Browse files
royreznikmethaneezio-melotti
authored
gh-91423: Remove bugs.python.org from bugs.rst (GH-91425)
* Remove bugs.python.org from bugs.rst * Update bugs.rst to the github issue tracker * reflow * Fix a typo and rephrase a sentence. Co-authored-by: Inada Naoki <songofacandy@gmail.com> Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
1 parent f6e43e8 commit df81d28

File tree

1 file changed

+20
-19
lines changed

1 file changed

+20
-19
lines changed

Doc/bugs.rst

+20-19
Original file line numberDiff line numberDiff line change
@@ -40,38 +40,39 @@ though it may take a while to be processed.
4040
Using the Python issue tracker
4141
==============================
4242

43-
Bug reports for Python itself should be submitted via the Python Bug Tracker
44-
(https://bugs.python.org/). The bug tracker offers a web form which allows
45-
pertinent information to be entered and submitted to the developers.
43+
Issue reports for Python itself should be submitted via the GitHub issues
44+
tracker (https://github.com/python/cpython/issues).
45+
The GitHub issues tracker offers a web form which allows pertinent information
46+
to be entered and submitted to the developers.
4647

4748
The first step in filing a report is to determine whether the problem has
4849
already been reported. The advantage in doing so, aside from saving the
49-
developers time, is that you learn what has been done to fix it; it may be that
50+
developers' time, is that you learn what has been done to fix it; it may be that
5051
the problem has already been fixed for the next release, or additional
5152
information is needed (in which case you are welcome to provide it if you can!).
52-
To do this, search the bug database using the search box on the top of the page.
53+
To do this, search the tracker using the search box at the top of the page.
5354

54-
If the problem you're reporting is not already in the bug tracker, go back to
55-
the Python Bug Tracker and log in. If you don't already have a tracker account,
56-
select the "Register" link or, if you use OpenID, one of the OpenID provider
57-
logos in the sidebar. It is not possible to submit a bug report anonymously.
55+
If the problem you're reporting is not already in the list, log in to GitHub.
56+
If you don't already have a GitHub account, create a new account using the
57+
"Sign up" link.
58+
It is not possible to submit a bug report anonymously.
5859

59-
Being now logged in, you can submit a bug. Select the "Create New" link in the
60-
sidebar to open the bug reporting form.
60+
Being now logged in, you can submit an issue.
61+
Click on the "New issue" button in the top bar to report a new issue.
6162

62-
The submission form has a number of fields. For the "Title" field, enter a
63-
*very* short description of the problem; less than ten words is good. In the
64-
"Type" field, select the type of your problem; also select the "Component" and
65-
"Versions" to which the bug relates.
63+
The submission form has two fields, "Title" and "Comment".
64+
65+
For the "Title" field, enter a *very* short description of the problem;
66+
less than ten words is good.
6667

6768
In the "Comment" field, describe the problem in detail, including what you
6869
expected to happen and what did happen. Be sure to include whether any
6970
extension modules were involved, and what hardware and software platform you
7071
were using (including version information as appropriate).
7172

72-
Each bug report will be assigned to a developer who will determine what needs to
73-
be done to correct the problem. You will receive an update each time action is
74-
taken on the bug.
73+
Each issue report will be reviewed by a developer who will determine what needs to
74+
be done to correct the problem. You will receive an update each time an action is
75+
taken on the issue.
7576

7677

7778
.. seealso::
@@ -95,6 +96,6 @@ patching Python in the `Python Developer's Guide`_. If you have questions,
9596
the `core-mentorship mailing list`_ is a friendly place to get answers to
9697
any and all questions pertaining to the process of fixing issues in Python.
9798

98-
.. _Documentation bugs: https://bugs.python.org/issue?@filter=status&@filter=components&components=4&status=1&@columns=id,activity,title,status&@sort=-activity
99+
.. _Documentation bugs: https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocs
99100
.. _Python Developer's Guide: https://devguide.python.org/
100101
.. _core-mentorship mailing list: https://mail.python.org/mailman3/lists/core-mentorship.python.org/

0 commit comments

Comments
 (0)