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. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
