[python-committers] improving our code quality [my summary of the "PQM" thread]
Facundo Batista
facundobatista at gmail.com
Fri Aug 15 17:53:25 CEST 2008
More information about the python-committers mailing list
Fri Aug 15 17:53:25 CEST 2008
- Previous message: [python-committers] improving our code quality [my summary of the "PQM" thread]
- Next message: [python-committers] Fw: Releasing beta 3's tonight
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2008/8/15 A.M. Kuchling <amk at amk.ca>: > 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. *Maybe*. It'd be the fourth keyword there. But I don't want to start populating that option, and reach the same issue we have now with "Resolution", without fixing first that issue. (I'm deliberately trying to avoid getting into how to fix that, we should leave this for after the releases...) Regards, -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/
- Previous message: [python-committers] improving our code quality [my summary of the "PQM" thread]
- Next message: [python-committers] Fw: Releasing beta 3's tonight
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list