Document the release process on devguide?
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?
Happy to help.
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*
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@baybryj.net -- []
I take it that PEP 101 is updated whenever the recipe changes in any way?
On Sat, Dec 19, 2020 at 1:41 PM Ned Deily nad@baybryj.net 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@baybryj.net -- []
python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@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/B... Code of Conduct: https://www.python.org/psf/codeofconduct/
On Dec 19, 2020, at 16:55, Guido van Rossum guido@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 nad@baybryj.net 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 -- []
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 -- []
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 -- []
On Dec 19, 2020, at 16:26, joannah nanjekye nanjekyejoannah@gmail.com wrote:
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.
The info in PEP 101 is very specialized and we have enough trouble keeping it up-to-date in one place :) I don't see any value in trying to have it in two places. And I'm sure most people would find it tediously boring :)
Am assuming, that any core dev has the potential to be a release manager in the future.
Perhaps we could add a few sentences to the devguide about the role of the release manager, with a link to PEP 101 for those interested in getting more of a feel for the mechanics (although that is about to change somewhat anyway thanks to Pablo's work at further automating the process), and with who to contact if one is interested in becoming a release manager for a future release (today, that would be the current and past release managers).
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
-- Ned Deily nad@python.org -- []
participants (4)
-
Guido van Rossum -
joannah nanjekye -
Ned Deily -
Ned Deily