Skip to content

Commit 13d6ca8

Browse files
authored
PEP 588: Mark as Final (#4086)
1 parent b0198fa commit 13d6ca8

File tree

1 file changed

+7
-14
lines changed

1 file changed

+7
-14
lines changed

peps/pep-0588.rst

Lines changed: 7 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,14 @@ Title: GitHub Issues Migration Plan
33
Author: Mariatta <[email protected]>
44
BDFL-Delegate: Barry Warsaw <[email protected]>
55
Discussions-To: https://discuss.python.org/t/13791
6-
Status: Draft
6+
Status: Final
77
Type: Informational
8-
Content-Type: text/x-rst
98
Created: 27-Mar-2019
109

10+
.. canonical-doc:: `psf/gh-migration#13 <https://github.com/psf/gh-migration/issues/13>`__
11+
12+
The migration was carried out in April 2022.
13+
1114

1215
Abstract
1316
========
@@ -200,12 +203,12 @@ Mapping between issues from bpo and GitHub
200203
------------------------------------------
201204

202205
Usually when we reference an issue from bpo, we use bpo-XYZ but with
203-
Github, we will have a new reference with this format
206+
GitHub, we will have a new reference with this format
204207
``https://github.com/python/cpython/issue/XYZ``.
205208

206209
Because we will migrate the issues from bpo to GitHub, we need to have a new
207210
field on bpo for the reference to the issues on GitHub, and the same thing on
208-
Github for the 'eventual' reference from bpo.
211+
GitHub for the 'eventual' reference from bpo.
209212

210213
For GitHub, we need to add ``origin: https://bugs.python.org/issueXYZ``.
211214
For bpo, add a new field ``moved to:
@@ -309,13 +312,3 @@ Copyright
309312
=========
310313

311314
This document has been placed in the public domain.
312-
313-
314-
..
315-
Local Variables:
316-
mode: rst
317-
indent-tabs-mode: nil
318-
sentence-end-double-space: t
319-
fill-column: 70
320-
coding: utf-8
321-
End:

0 commit comments

Comments
 (0)