256f4285d6
PEP 581: mention that bpo tickets can be automatically closed. ( #1119 )
2019-07-08 18:50:27 -07:00
5f56c05e07
PEP 581 Updates ( #1114 )
...
- include recent changes to bpo
- clarify the downsides of GitHub
2019-06-27 14:42:57 -07:00
81d2b5ccd7
Accept PEP 581
2019-05-14 18:13:32 -07:00
7519d3280b
Mariatta prefers to be just Mariatta ( #1020 )
2019-05-02 09:14:33 -04:00
b393d4bbfd
Split GitHub migration rationale and plan into two separate PEPs ( #1013 )
2019-04-30 19:51:45 -04:00
63821b0d12
PEP 581: Minor text edits ( #981 )
2019-04-11 14:04:09 -07:00
fb41c35fcb
PEP 581: Add Post-history ( #918 )
...
Posted to Python-dev on March 7, 2019.
2019-03-07 16:31:24 -08:00
08ce9d3c7f
PEP 581: Remove mention of "closing issues in bpo" ( #917 )
...
Issue will be moved to GitHub only when there is interest.
2019-03-07 16:10:57 -08:00
f4f2f158c5
PEP 581: Add info about bug triage team and CLA assistant ( #916 )
2019-03-07 10:22:57 -08:00
373d2ba05b
PEP 581: Mention GitHub's new feature wrt issue template ( #848 )
...
It is now possible to automate issue assignee and labels via templates.
https://blog.github.com/changelog/2018-12-05-issue-template-automation-improvements/
2018-12-05 19:15:50 -08:00
001382733e
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
2018-10-15 07:38:18 -07:00
b991d19bf9
PEP 581: use auto-numbering for footnotes. ( #769 )
2018-09-11 14:39:45 -07:00
45179d1991
PEP 581: Copy editing (GH-757)
2018-08-15 15:20:47 -04:00
4a33866e32
PEP 581: Using GitHub Issues For CPython ( #681 )
...
The first iteration.
2018-08-14 05:15:35 -07:00
Mariatta
Barry Warsaw
Guido van Rossum
James Hamm
Stéphane Wirtel
Ezio Melotti
Harmon