On Dec 19, 2020, at 16:55, Guido van Rossum <gu...@python.org> wrote: > I take it that PEP 101 is updated whenever the recipe changes in any way?
Yes, that’s the intent. And over the years, “the recipe” has become rather a multi-course banquet meal with all of the steps and systems now involved in putting out a release. I should point out that PEP 101 describes the mechanics of putting out a release. It is by no means a complete description of the role that a release manager plays in our development process. Perhaps a brief description could be written up and added to the devguide. That would be of much more value, I think. > >> On Sat, Dec 19, 2020 at 1:41 PM Ned Deily <n...@baybryj.net> wrote: >> >> On Dec 19, 2020, at 14:57, joannah nanjekye <nanjekyejoan...@gmail.com> >> wrote: >> > I got to know from Pablo that the release process is documented in a PEP >> > here: https://www.python.org/dev/peps/pep-0101/ >> > >> > I wonder if it makes sense for us to formalize this process by documenting >> > it on devguide, and adding any extra/missing information? >> >> PEP 101 is intended to be the primary documentation of the release process >> steps from the perspective of a release manager. It is not aimed at any >> other audience. There is release cycle information, aimed at developers, in >> various parts of the devguide. It could certainly be improved. Are there >> some things in particular of value to core developers that are missing or >> could use work there? > -- Ned Deily n...@python.org -- []
_______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/RNKQ375P2PZRXQ6R2ZKMW3IYL5TD4X6F/ Code of Conduct: https://www.python.org/psf/codeofconduct/
