Hi,
As Python 3.11.0 beta 1 approaches, we need to start considering the new release manager.
*If you are interested in being the release manager for Python 3.12 (and potentially Python 3.13* *if you wish), please reach out to me.*
Ok, but what does a release manager do?
The release manager is in charge of doing all the Python releases associated with the versions that they are in charge of. This includes normally 7 alphas, 4 betas, 2 release candidates, final versions, bugfix releases every 2 months for approximately 18 months and any source-only security releases for 5 years after the release of the final version. *This means that this is a commitment of at least 5 years. *To get an idea of what's involved in a release, check PEP 101 <https://peps.python.org/pep-0101/>.
The release manager is in charge of ensuring that the releases are stable. This means continuous monitoring of the buildbots, shepherding some issues and release blockers, performance degradation and many other aspects. This means that is very important for the release manager to keep track of the technical details of the development of the versions they are in charge of.
The release manager needs to ensure that release blockers are identified and fixed before the releases are done. This includes coordinating core developers to fix the release blockers or revert the relevant changes in cases fixes are not available in a reasonable amount of time.
The release manager needs to author and maintain the release schedule PEPs. Check PEP 664 <https://peps.python.org/pep-0664/> as an example.
The release manager needs to ensure the "What's new" document for the releases they are in charge of is complete and properly reflects all changes, highlights and additions that are included in the release. This could be done personally by the release manager or coordinated by them.
If you have any questions, please reach out to me (or any other release manager if you want) and we will be happy to answer them :)
Regards from sunny London, Pablo Galindo Salgado