On 01/08/2010 20.43, R. David Murray wrote:
On Sun, 01 Aug 2010 21:28:05 +1000, Nick Coghlan<ncogh...@gmail.com> wrote:
On Sun, Aug 1, 2010 at 5:41 PM, Mark Lawrence<breamore...@yahoo.co.uk> wrote:
I plucked this figure out of the air thinking that if an issue was going to
drop under the radar, this would be the most likely time. I was considering
a worst case scenario where several core triage people are at a big Python
event, others are on holiday [ shame on you :) ], some looking after the
kids, yet more off sick etc. Hum, perhaps 24 hours is too soon, what a bout
a week, opinions anybody? Notifications would go to the bugs mailing list
and/or #python-dev. But this is hypothetical anyway if the message count of
1 query works. Only one way to find out, let's try it.
Perhaps just another number to track in the weekly bug summary?
Better, a table section giving the bugids, titles, and URL. Ezio just
finished reworking the summary script to be more easily modified, so I
bet he would find this easy to add at this point.
--David
FWIW this morning I added a new version of the roundup-summary script
[0] that includes a "Recent issues with no replies" table with bugids,
titles and URLs. (I hope Guido doesn't mind if I used the time machine ;)
[0]: http://psf.upfronthosting.co.za/roundup/meta/issue284
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
