[python-committers] improving our code quality [my summary of the "PQM" thread]
A.M. Kuchling
amk at amk.ca
Fri Aug 15 16:54:56 CEST 2008
More information about the python-committers mailing list
Fri Aug 15 16:54:56 CEST 2008
- Previous message: [python-committers] improving our code quality [my summary of the "PQM" thread]
- Next message: [python-committers] improving our code quality [my summary of the "PQM" thread]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Aug 14, 2008 at 11:48:49PM -0300, Facundo Batista wrote: > And, if you pick up that bug six month later, or three year later, you > lose twenty minutes reading the whole discussion, and then realize > that neither you have the expertise to get a decision, and skip to the > next bug. ... > Don't know how to solve this, and I'm pretty sure I'm not pointing out > all the problems: just don't forget to include this in the list. Should we add a 'needsreview' or 'ready-for-review' keyword that could be marked on such bugs? People could check for it before diving into a bug, and the mythical reviewer could use it too. --amk
- Previous message: [python-committers] improving our code quality [my summary of the "PQM" thread]
- Next message: [python-committers] improving our code quality [my summary of the "PQM" thread]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list