PEP 101 is intended to be the primary documentation of the release process steps from the perspective of a release manager.
I think am talking about the documentation aimed at the release manager. And yes whether it makes sense to move the details to devguide too.
Am assuming, that any core dev has the potential to be a release manager in the future.
On Sat, Dec 19, 2020 at 5:22 PM Ned Deily nad@python.org wrote:
On Dec 19, 2020, at 14:57, joannah nanjekye nanjekyejoannah@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 nad@python.org -- []
-- Best, Joannah Nanjekye
*"You think you know when you learn, are more sure when you can write, even more when you can teach, but certain when you can program." Alan J. Perlis*