Regression trails are hard to track in development process

[GoogleCodeExporter]

What steps will reproduce the problem?
1. People don't want to be blamed, especially when doing open source work
2. But it is still critical for Python stability to analyze regressions in 
systematic way

What is the expected output? What do you see instead?
Example - http://hg.python.org/cpython/rev/19e6e32db5ec
No parseable reference to distinguish issue as a regression.

Expected is answer how many regressions are fixed for the given Python versions.

Original issue reported on code.google.com by [email protected] on 13 Nov 2012 at 3:09