On Sun, Aug 1, 2010 at 5:41 PM, Mark Lawrence <breamoreboy at 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 about > 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? Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4