[Python-Dev] Bugfix porting policy (was Re: Doc nits question)

Georg Brandl g.brandl at gmx.net
Thu Oct 2 22:33:49 CEST 2008

Martin v. Löwis schrieb:
>> A large merge queue would accumulate making hard for someone to pick
>> out the bugfixes. Of course, people could just merge fixes right after
>> they apply it to the trunk, though.
> I think they should. To my knowledge, nobody goes through the changelog
> anymore trying to find out what needs backporting. Tracking what still
> needs merging should happen in the bug tracker, by leaving the report
> open until merging has been done. Every change that isn't immediately
> merged and doesn't have an open issue just won't get merged at all.

This is why it's good to track what was merged and what not via svnmerge,
because it cannot miss commits. It also is easy for someone to select
which stuff to merge if the commit message on the trunk indicates
backportable fixes.


Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

More information about the Python-Dev mailing list