[Python-Dev] Bugfix porting policy (was Re: Doc nits question)
musiccomposition at gmail.com
Thu Oct 2 22:26:20 CEST 2008
On Thu, Oct 2, 2008 at 3:18 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>> 2. Do bugfixes in trunk, and merge them to maint via svnmerge.
>>> Arguments as for 1, but reversed: many blocks, but less problems with 3k.
> I'm not so sure that we need to block all the changes that we don't
> want, though: it would be sufficient to just not merge them, right?
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.
> (of course, somebody could go over it from time to time and block
> everything older than a month that was still available, just to prevent
> accidental merging)
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/musiccomposition%40gmail.com
"There's no place like 127.0.0.1."
More information about the Python-Dev