[Python-Dev] Need Survey Answers from Core Developers

Nick Coghlan ncoghlan at gmail.com
Sat May 19 13:40:12 CEST 2007

Jeff Rush wrote:
> Time is short and I'm still looking for answers to some questions about
> cPython, so that it makes a good showing in the Forrester survey.
> 1) How is the project governed?  How does the community make decisions
>    on what goes into a release?
>    You know, I've been a member of the Python community for many years
>    -- I know about PEPs, Guido as BDFL, and +1/-1.  But I've never
>    figured out exactly how -final- decisions are made on what goes
>    into a release.  I've never needed to, until now.  Can someone
>    explain in one paragraph?

As others have already pointed out, the ultimate authority rests with 
GvR. For any given release, Guido delegates a fair bit of authority to 
the release manager, and will often defer to the release manager's 
judgment (especially for maintenance releases).

The current status of a release (including naming names for the release 
team) is tracked using an Informational track PEP. The initial Python 
2.5 release was tracked in PEP 356. The Python 2.6 release is being 
tracked in PEP 361.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list