#562 [Opn]: send bug summary to pear-qa

ID: 562 Updated by: neufeind@php.net Reported By: smith at backendmedia dot com Status: Open Bug Type: Bug System Operating System: Irrelevant PHP Version: Irrelevant New Comment: Well, I don't see why such a summary would be helpful. You can easily browse the bugs (by relevance, by package, ...) via the bug-system from time to time. And what would "who closed the bugs" be needed for? There might be several people involved in the solution - so imho it doesn't really matter who actually closed the bug. Previous Comments: ------------------------------------------------------------------------ [2004-02-20 10:14:12] toby@php.net I guess just routing all bug mails to pear-qa would last, shouldn't it? The header and subject additions of the bug-system should enable everyone to filter them out. Otherwise I'd prefer a normal new mailinglist instead of a summary, since each bug is a single topic and and bug-actions should be viewable grouped by bug (threads). ------------------------------------------------------------------------ [2004-02-20 09:40:10] lsmith@php.net alternatively I guess a dedicated bug list would also do, if the summary is too much effort to implement. QA really needs to know what is going on. Who closes bugs, how many open etc. ------------------------------------------------------------------------ [2004-01-13 05:33:26] smith at backendmedia dot com Description: ------------ Would it be possible to send a summary of all open bugs to pear-qa? What would be even nicer is to also add all bug reports that have changed. The time interval should probably be weekly. ------------------------------------------------------------------------ -- Edit this bug report at http://pear.php.net/bugs/bug.php?id=562&edit=1