[python-committers] changes after 2.7 final

[Brett Cannon]

On Fri, Jul 2, 2010 at 01:57, Antoine Pitrou <solipsis at pitrou.net> wrote:
>
>> > - I will initialize svnmerge from py3k -> 2.7maint.
>>
>> We should probably all get into the habit of making sure that we leave
>> any issues open with Python 2.7 flagged as an effected version to get
>> fixes ported. These then could become "easy" issues for people to
>> contribute through by letting others create a backport patch. Else we
>> could think about introducing a "2.x backport" (or simply "backport")
>> keyword to flag such open issues.
>
> What do you mean by that? Why wouldn't we just do the backports
> ourselves?

People forget or don't view it as important enough to do. Just look at
home many merges Benjamin did last week into py3k from trunk because
people didn't do a merge.

> (I don't understand what "effected" means here)

That should have been "affected".

>
> For the record, the "2.6 backport" keyword on the tracker ended up
> mostly unused.

I supported its removal. =)

>Good practice is to backport just after you commit on
> trunk/py3k, not months later.

Obviously, but people forget or simply choose not to.

-Brett


>
>
>
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> http://mail.python.org/mailman/listinfo/python-committers
>