PEP 588 Updates (#1139)
- hire a professional project manager - create playground issue tracker for experiment - test repo for labels - python triage team has been created - devguide update Co-Authored-By: Carol Willing <carolcode@willingconsulting.com>
This commit is contained in:
parent
efa49a74d1
commit
e81fa07b63
38
pep-0588.rst
38
pep-0588.rst
|
@ -24,6 +24,17 @@ Here we outline the tasks, steps, and core decisions we need to make
|
|||
in order to migrate bug tracking to GitHub, with the least impact on
|
||||
CPython developer productivity.
|
||||
|
||||
Hire a professional project manager
|
||||
-----------------------------------
|
||||
|
||||
Having a professional project manager to handle the migration, similar to how
|
||||
the Warehouse project was managed, would help ensure the success of this project.
|
||||
|
||||
Create a playground CPython issue tracker on GitHub
|
||||
---------------------------------------------------
|
||||
|
||||
We should create a playground issue tracker on GitHub where we can experiment
|
||||
and test out the new workflow.
|
||||
|
||||
Backup of GitHub data
|
||||
---------------------
|
||||
|
@ -54,9 +65,12 @@ about this has been started in `core-workflow mailing list
|
|||
as well as on `Discourse
|
||||
<https://discuss.python.org/t/using-cla-assistant-for-python/990>`_.
|
||||
|
||||
This effort `is currently stalled <https://discuss.python.org/t/cla-assistant-is-no-go/2066/>`_
|
||||
because cla-assistant does not yet support CLA signed on behalf of organization.
|
||||
|
||||
Create Bug Triage Team on GitHub
|
||||
--------------------------------
|
||||
|
||||
Create "Python Triage" team on GitHub
|
||||
-------------------------------------
|
||||
|
||||
The bug triagers on bpo are valuable to the core Python workflow, and we
|
||||
definitely would need even more help with triaging issues on GitHub.
|
||||
|
@ -65,10 +79,17 @@ It has been `proposed on Discourse
|
|||
<https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992/5>`_
|
||||
for us to create a "bug triage" team on GitHub to help with closing
|
||||
issues, notifying the appropriate parties, as well as applying labels
|
||||
to issues and pull requests. We can grant the "write" permission to
|
||||
the "bug triage" team, while limiting merging pull requests to
|
||||
"CPython core developer" team on GitHub.
|
||||
to issues and pull requests.
|
||||
|
||||
The new Triage role on GitHub is currently in beta, and the Python organization
|
||||
has been granted access to this role, and we can begin taking advantage of it.
|
||||
|
||||
The "Python Triage" team has been created. A description and expectations of the
|
||||
triage role `have been added to Devguide <https://devguide.python.org/triaging/#python-triage-team>`_.
|
||||
|
||||
Progress of this project can be
|
||||
tracked in `"Adding Triagers" project board
|
||||
<https://github.com/python/core-workflow/projects/3>`_.
|
||||
|
||||
Create labels for issue triage
|
||||
------------------------------
|
||||
|
@ -97,6 +118,8 @@ In addition, we'll create a ``needs triage`` label.
|
|||
The final "labels" to be created can be decided at a later time when
|
||||
it is time to start switching to GitHub issues.
|
||||
|
||||
A test repository containing all possible labels and color schema has been
|
||||
created by Carol Willing and can be reviewed at https://github.com/willingc/test-581/labels.
|
||||
|
||||
Create issue templates
|
||||
----------------------
|
||||
|
@ -137,8 +160,9 @@ the issue.
|
|||
Update the devguide
|
||||
-------------------
|
||||
|
||||
Provide explanation in the devguide about new issue workflow and triage labels.
|
||||
|
||||
Devguide should be updated with information about the new workflow of using GitHub
|
||||
issues. It can be done as a separate branch, and it should be done ahead of the
|
||||
migration, not after.
|
||||
|
||||
Add a button in bpo to migrate the issue to GitHub
|
||||
--------------------------------------------------
|
||||
|
|
Loading…
Reference in New Issue