@@ -3,11 +3,14 @@ Title: GitHub Issues Migration Plan
33Author: Mariatta <
[email protected] >
44BDFL-Delegate: Barry Warsaw <
[email protected] >
55Discussions-To: https://discuss.python.org/t/13791
6- Status: Draft
6+ Status: Final
77Type: Informational
8- Content-Type: text/x-rst
98Created: 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
1215Abstract
1316========
@@ -200,12 +203,12 @@ Mapping between issues from bpo and GitHub
200203------------------------------------------
201204
202205Usually 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
206209Because we will migrate the issues from bpo to GitHub, we need to have a new
207210field 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
210213For GitHub, we need to add ``origin: https://bugs.python.org/issueXYZ ``.
211214For bpo, add a new field ``moved to:
@@ -309,13 +312,3 @@ Copyright
309312=========
310313
311314This 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