On Sat, 28 Jun 2003, Sascha Schumann wrote:
>> But if the summaries contain only screened (== verified) reports,
>> and sent one per category? Better ideas would be appreciated, of course.
>
> Well, I pretty much embrace the idea that reports ought to
> fall through the cracks, if they don't bother developers
> enough to address them. Otherwise, reports just accumulate
> and accumulate without having any effect.
Currently you don't get any mails from the reports unless someone
touches them. So they do 'fall through the cracks' already, sort of.
By adding the 'rotting' feature will make this a bit more effective.
Just thinking whether or not there should be a notification
for the submitter when a report rots. Comments?
Getting all the emails from [EMAIL PROTECTED] is really
too much traffic, that's why I was thinking about adding some
headers to the mails to make it easier to filter out those you
really want to see.
Some short cut URLs would do this already though, using the
web interface and search..but it's not quite the same. :)
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
