On 23 March 2014 08:23, "Martin v. Löwis" <mar...@v.loewis.de> wrote: > Am 22.03.14 23:05, schrieb Donald Stufft: >> I think the pep doesn't mandate that someone does. It still requires someone >> to care enough to actually write the patch. It just allows such a patch to >> be merged. > > Does it actually? Unfortunately, I never got around to writing the PEP > on security-only branches, so the terminology of PEP 466 is unclear. > It says "maintenance brances", which could mean three things: > - all branches that have ever been made off default in > hg.python.org/cpython (i.e. back to 2.0). This would be the > traditional definition of "maintenance branch" in a version control > system, but is probably not intended by the PEP > - all branches from which still releases are made (whether security-only > or bug fix) > - all bug fix branches > > Clarification of this is just a minor nit, though - although the > maintainers of the old maintenance branches should (IMO) have a say > whether they accept a certain change on a certain branch.
Both good points, I'll clarify them in the PEP. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
