@@ -44,38 +44,39 @@ though it may take a while to be processed.
4444Using the Python issue tracker
4545==============================
4646
47- Bug reports for Python itself should be submitted via the Python Bug Tracker
48- (https://bugs.python.org/). The bug tracker offers a Web form which allows
49- pertinent information to be entered and submitted to the developers.
47+ Issue reports for Python itself should be submitted via the GitHub issues
48+ tracker (https://github.com/python/cpython/issues).
49+ The GitHub issues tracker offers a web form which allows pertinent information
50+ to be entered and submitted to the developers.
5051
5152The first step in filing a report is to determine whether the problem has
5253already been reported. The advantage in doing so, aside from saving the
53- developers time, is that you learn what has been done to fix it; it may be that
54+ developers' time, is that you learn what has been done to fix it; it may be that
5455the problem has already been fixed for the next release, or additional
5556information is needed (in which case you are welcome to provide it if you can!).
56- To do this, search thebug database using the search boxon the top of the page.
57+ To do this, search thetracker using the search boxat the top of the page.
5758
58- If the problem you're reporting is not already in thebug tracker, go back to
59- the Python Bug Tracker and log in. If you don't already have atracker account,
60- select the "Register" link or, if you use OpenID, one of the OpenID provider
61- logos in the sidebar. It is not possible to submit a bug report anonymously.
59+ If the problem you're reporting is not already in thelist, log in to GitHub.
60+ If you don't already have aGitHub account, create a new account using the
61+ "Sign up" link.
62+ It is not possible to submit a bug report anonymously.
6263
63- Being now logged in, you can submita bug. Select the "Create New" link in the
64- sidebar to open thebug reporting form .
64+ Being now logged in, you can submitan issue.
65+ Click on the "New issue" button in thetop bar to report a new issue .
6566
66- The submission form hasa number of fields. For the "Title"field, enter a
67- * very * short description of the problem; less than ten words is good. In the
68- "Type " field,select the type of your problem; also select the"Component" and
69- "Versions" to which the bug relates .
67+ The submission form hastwo fields, "Title"and "Comment".
68+
69+ For the "Title " field,enter a * very * short description of theproblem;
70+ less than ten words is good .
7071
7172In the "Comment" field, describe the problem in detail, including what you
7273expected to happen and what did happen. Be sure to include whether any
7374extension modules were involved, and what hardware and software platform you
7475were using (including version information as appropriate).
7576
76- Eachbug report will beassigned to a developer who will determine what needs to
77- be done to correct the problem.
78- taken on thebug .
77+ Eachissue report will bereviewed by a developer who will determine what needs to
78+ be done to correct the problem. You will receive an update each time an action is
79+ taken on theissue .
7980
8081
8182..seealso ::
@@ -99,6 +100,6 @@ patching Python in the `Python Developer's Guide`_. If you have questions,
99100the `core-mentorship mailing list `_ is a friendly place to get answers to
100101any and all questions pertaining to the process of fixing issues in Python.
101102
102- .. _Documentation bugs :https://bugs. python.org/issue?@filter=status&@filter=components&components=4&status=1&@columns=id,activity,title,status&@sort=-activity
103+ .. _Documentation bugs :https://github.com/ python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocs
103104.. _Python Developer's Guide :https://devguide.python.org/
104105.. _core-mentorship mailing list :https://mail.python.org/mailman3/lists/core-mentorship.python.org/