RetroSearch Browse

Tue Jul 14 09:19:24 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140718.html

Nick Coghlan writes:

 > I wonder: should we start putting some of these process details for
 > the different phases in the release PEPs themselves? Larry sent a good
 > summary to python-committers for 3.5 a while back, but they'd be
 > easier to find in the PEPs, and it would also make it clear which
 > aspects a new RM was keeping, and which they wanted to try doing
 > differently.

It may be overkill, but my take would be a BCP PEP that summarizes
consensus best practice as well as option rules for releases, and then
each release would have its own PEP briefly describing any deviations
from the BCP, including both "I use variant A" and "I'm experimenting
with practice Alpha".  The former should be explained in the BCP, the
rationale for the latter in the release PEP.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140718.html below:

[Python-Dev] Freeze exception for http://bugs.python.org/issue23661 ?