#562 [Asn]: send bug summary to pear-qa
| From: | helgi at trance dot is | Date: | Tue, 27 Apr 2004 03:38:08 +0000 |
| Subject: | #562 [Asn]: send bug summary to pear-qa | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-28397@lists.php.net to get a copy of this message | ||
ID: 562
Updated by: helgi@trance.is
Reported By: smith at backendmedia dot com
Status: Assigned
Bug Type: Bug System
Operating System: Irrelevant
PHP Version: Irrelevant
-Assigned To: mj
+Assigned To: dufuz
New Comment:
I assigend my self to this one since I'm making a bug reminder/summary
script... Should be added sooner the later ;)
Martin what's the status on pear-bugs and pear-announce ? :)
Previous Comments:
------------------------------------------------------------------------
[2004-02-20 12:31:24] mj@php.net
So to sum it up:
* Weekly summaries will be send to pear-qa
* A copy of all bug reports and the appendant comments will be send to
pear-bugs.
If that is the way to go, I'll take care of getting the stuff set up.
(I'm also working towards having a announcement list, but did not get a
response from the people in charge yet.)
------------------------------------------------------------------------
[2004-02-20 11:29:37] neufeind@php.net
Already yeah. After a clarifying discussion I've agreed with Lukas that
a mailinglist would be best. However neither pear-dev nor pear-qa
should be flooded with messages, since others might suffer from that
"noise". So we propose to open a pear-bug-list (similar to pear-cvs)
which everbody interested is invited to join. We expect >40 mails per
week ..
------------------------------------------------------------------------
[2004-02-20 11:16:41] toby@php.net
I personally prefer mailinglists. :) Getting the latest issues
directly aggregated inside one application is quite cool! :) Maybe a
seperated mailinglist pear-bugs is the best solution.
------------------------------------------------------------------------
[2004-02-20 11:00:20] neufeind@php.net
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.
------------------------------------------------------------------------
[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).
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://pear.php.net/bugs/bug.php?id=562
--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=562&edit=1