I've begun the task of assessing the 2.6 commits, but the job is unexpectedly large.
What I did:
* Took the output of 'svn log -r60999:66717'. (2.5.2 was branched from rev. 60999, so I'm ignoring commits to the trunk before 2.5.2 was branch, which may miss some things.)
* Wrote a little script to explode the log into a separate file for each commit. This resulted in about 2200 files.
* Did a long series of 'grep' and 'rm' commands to remove irrelevant files. For example, if the commit touches abc.py, bytesobject.c, bytearrayobject.c, etc. it was removed.
* Wrote a little script to find commits that only touch the docs, and moved them aside.
At this point I still have 1191 files left. Many of these commits are still irrelevant, but this is a lot for me to look through. A tarball with the remaining commits is at
http://www.amk.ca/files/python/2.6-changes.tgz
Can we parallelize the job? One person could take commits starting with '01', another with '02', etc. Or each person could assess the commits they made.
--amk
On Tue, Oct 07, 2008 at 08:44:09PM -0400, A.M. Kuchling wrote:
At this point I still have 1191 files left. Many of these commits are still irrelevant, but this is a lot for me to look through. A tarball with the remaining commits is at
http://www.amk.ca/files/python/2.6-changes.tgz
On the metro this morning, I worked on this some more and now have only 858 files for consideration. At this point I think we have to look at commits individually. I'll turn the lists of commits into a set of wiki page that we can examine and edit down in parallel.
(I've updated the above tarball in the meantime.)
--amk
On Wed, Oct 08, 2008 at 08:06:09AM -0400, A.M. Kuchling wrote:
look at commits individually. I'll turn the lists of commits into a set of wiki pages that we can examine and edit down in parallel.
I decided to put them in SVN instead, in sandbox/py2.5.3/ .
How do we want to assess these commits for possible inclusion in 2.5.3?
--amk
-
A.M. Kuchling