[python-committers] what's going on with Misc/NEWS?

Eric Snow ericsnowcurrently at gmail.com
Sat May 25 06:01:16 CEST 2013

On Fri, May 24, 2013 at 9:46 PM, Raymond Hettinger
<raymond.hettinger at gmail.com> wrote:
> and it recognizes that users don't really need to look across merge
> boundaries.

This is tricky though for any patch that is forward-ported to a
release branch (a la 3.2->3.3).  How can you tell from MISC/News in
which release (e.g. 3.3.0 or 3.3.1) of that branch the bug was fixed?
The entry would only show up in MISC/News for the previous release
(e.g. 3.2.3).

Granted, this would impact much fewer patches than our current pain point does.


More information about the python-committers mailing list