[Python-Dev] List of candidate 2.4.4 bugs?

A.M. Kuchling amk at amk.ca
Wed Sep 27 19:35:42 CEST 2006

On Wed, Sep 27, 2006 at 06:56:14PM +0200, "Martin v. Löwis" wrote:
> I don't think so. Also, I see little chance that many bugs will be fixed
> that aren't already. People should really do constant backporting,
> instead of starting backports when a subminor release is made.


One reason I often don't backport a bug is because I'm not sure if
there will be another bugfix release; if not, it's wasted effort, and
I wasn't sure if a 2.4.4 release was ever going to happen.  After
2.4.4, will there be a 2.4.5 or is that too unlikely?

I've done an 'svn log' on the modules I'm familiar with (curses, zlib,
gzip) and will look at backporting the results.

Grepping for 'backport candidate' in 'svn log -r37910:HEAD' turns up
30-odd checkins that contain the phrase:

r51728 r51669 r47171 
r47061 r46991 r46882 r46879
r46878 r46602
r46589 r45234 r41842
r41696 r41531 r39767 r39743 r39739 r39650
r39595 r39594 r39491
r39135 r39044 r39030 r39012 r38932
r38927 r38887 
r38826 r38781
r38772 r38745


More information about the Python-Dev mailing list