Withdraw the Kallithea PEPs
This commit is contained in:
parent
3c4459393c
commit
e1002b4865
14
pep-0462.txt
14
pep-0462.txt
|
@ -3,7 +3,7 @@ Title: Core development workflow automation for CPython
|
||||||
Version: $Revision$
|
Version: $Revision$
|
||||||
Last-Modified: $Date$
|
Last-Modified: $Date$
|
||||||
Author: Nick Coghlan <ncoghlan@gmail.com>
|
Author: Nick Coghlan <ncoghlan@gmail.com>
|
||||||
Status: Deferred
|
Status: Withdrawn
|
||||||
Type: Process
|
Type: Process
|
||||||
Content-Type: text/x-rst
|
Content-Type: text/x-rst
|
||||||
Requires: 474
|
Requires: 474
|
||||||
|
@ -23,11 +23,15 @@ experience for other contributors that are reliant on the core team to get
|
||||||
their changes incorporated.
|
their changes incorporated.
|
||||||
|
|
||||||
|
|
||||||
PEP Deferral
|
PEP Withdrawal
|
||||||
============
|
==============
|
||||||
|
|
||||||
This PEP is currently deferred pending acceptance or rejection of the
|
This PEP has been `withdrawn by the author
|
||||||
Kallithea-based forge.python.org proposal in PEP 474.
|
<https://mail.python.org/pipermail/core-workflow/2015-October/000227.html>`_
|
||||||
|
in favour of the GitLab based proposal in PEP 507.
|
||||||
|
|
||||||
|
If anyone else would like to take over championing this PEP, contact the
|
||||||
|
`core-workflow mailing list <https://mail.python.org/mailman/listinfo/core-workflow>`_
|
||||||
|
|
||||||
|
|
||||||
Rationale for changes to the core development workflow
|
Rationale for changes to the core development workflow
|
||||||
|
|
13
pep-0474.txt
13
pep-0474.txt
|
@ -3,7 +3,7 @@ Title: Creating forge.python.org
|
||||||
Version: $Revision$
|
Version: $Revision$
|
||||||
Last-Modified: $Date$
|
Last-Modified: $Date$
|
||||||
Author: Nick Coghlan <ncoghlan@gmail.com>
|
Author: Nick Coghlan <ncoghlan@gmail.com>
|
||||||
Status: Draft
|
Status: Withdrawn
|
||||||
Type: Process
|
Type: Process
|
||||||
Content-Type: text/x-rst
|
Content-Type: text/x-rst
|
||||||
Created: 19-Jul-2014
|
Created: 19-Jul-2014
|
||||||
|
@ -23,6 +23,17 @@ This PEP does *not* propose any changes to the core development workflow
|
||||||
for CPython itself (see PEP 462 in relation to that).
|
for CPython itself (see PEP 462 in relation to that).
|
||||||
|
|
||||||
|
|
||||||
|
PEP Withdrawal
|
||||||
|
==============
|
||||||
|
|
||||||
|
This PEP has been `withdrawn by the author
|
||||||
|
<https://mail.python.org/pipermail/core-workflow/2015-October/000227.html>`_
|
||||||
|
in favour of the GitLab based proposal in PEP 507.
|
||||||
|
|
||||||
|
If anyone else would like to take over championing this PEP, contact the
|
||||||
|
`core-workflow mailing list <https://mail.python.org/mailman/listinfo/core-workflow>`_
|
||||||
|
|
||||||
|
|
||||||
Proposal
|
Proposal
|
||||||
========
|
========
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue