iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 581: Mapping issues, read-only mode for migrated issues (#809) 

* PEP 0581: Add a new status to bpo

* PEP 0581: When a bpo issue is migrated, this one should be in read-only

* PEP 0581: Add a section for the mapping between github and bpo issues
This commit is contained in:
Stéphane Wirtel 2018-10-15 16:38:18 +02:00 committed by Guido van Rossum
parent b77032006c
commit 001382733e
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
pep-0581.rst
View File

@ -230,6 +230,8 @@ this is much less than a complete overhaul.
We will create a button in bpo, that will copy over the issue description We will create a button in bpo, that will copy over the issue description
and associated comments into a GitHub issue. and associated comments into a GitHub issue.
We need to add a new status: "moved" with the url of the GitHub issue.
We should not be moving all open issues to GitHub. Issues with little or no We should not be moving all open issues to GitHub. Issues with little or no
activity should just be closed. Issues with no decision made for years should activity should just be closed. Issues with no decision made for years should
just be closed. just be closed.
@ -237,6 +239,12 @@ just be closed.
If a core developer is still interested in the issue, they can indicate so in If a core developer is still interested in the issue, they can indicate so in
the bpo issue, and later use the button to migrate it over to GitHub. the bpo issue, and later use the button to migrate it over to GitHub.
Migrated issues
---------------
When an issue is marked as "moved", this issue should be in read-only mode. bpo
should forbid the edition of the issue.
Make bpo read-only Make bpo read-only
------------------ ------------------
@ -244,6 +252,19 @@ This should be the final step. Once we start using GitHub issues, make bpo
read-only, instead of shutting it down. read-only, instead of shutting it down.
Do not accept new registrations. Do not allow comments or issues to be created. Do not accept new registrations. Do not allow comments or issues to be created.
Mapping between issues from bpo and GitHub
------------------------------------------
Usually when we reference an issue from bpo, we use bpo-XYZ but with Github, we
will have a new reference with this format https://github.com/python/cpython/issue/XYZ.
Because we will migrate the issues from bpo to GitHub, we need to have a new
field on bpo for the reference to the issues on GitHub, and the same thing on
Github for the 'eventual' reference from bpo.
For GitHub, we need to add "origin: https://bugs.python.org/issueXYZ".
For bpo, add a new field "moved to: https://github.com/python/cpython/issue/XYZ"
TBD and additional concerns TBD and additional concerns
=========================== ===========================