#1171 [Opn]: Bug system should send email to lead(s) when new bug reported
| From: | jmcastagnetto@php.net | Date: | Mon, 12 Apr 2004 07:23:25 +0000 |
| Subject: | #1171 [Opn]: Bug system should send email to lead(s) when new bug reported | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-27436@lists.php.net to get a copy of this message | ||
ID: 1171
Updated by: jmcastagnetto@php.net
Reported By: jmcastagnetto@php.net
Status: Open
Bug Type: Bug System
PHP Version: Irrelevant
New Comment:
Daniel,
I would not have submitted a bug report if what you say had happened,
as it is I did not receive any email from the bugs related to the
packages I lead.
You should've checked my latest CVS commits fixing bugs #822, #883,
#884, #885, #886, and #895.
Just in case you also did not see, check the list of the package I lead
at:
http://pear.php.net/user/jmcastagnetto
Every single one of the bugs mentioned above were generated by the
PEAR-QA team when checking for possible compatibility problems of PEAR
packages with PHP 5. In the case of the packages to which the bugs
above applied, all were related to the use of get_class().
Hopefully someone from the PEAR-QA team can clarify why not one of
their bug reports generated an email to the packages I maintain.
Previous Comments:
------------------------------------------------------------------------
[2004-04-09 23:35:15] danielc at analysisandsolutions dot com
The bug system does send an email to all developers listed for a
package. Emails are sent each time an action is taken (creation,
updates, comments, etc).
Perhaps you're not properly registered as the lead for the package in
question or your php.net forwarding address is messed up, or???
------------------------------------------------------------------------
[2004-04-09 22:30:10] jmcastagnetto@php.net
Description:
------------
The bug system should send an email to the lead(s) of the package for
which the bug is being reported.
It can be done for each new bug, or every time a bug report is
updated.
Perhaps the bugs should also be assigned to the lead when it is
reported?
(If I had not checked today to see if there were bugs for one of my
packages, I could've easily missed the QA team bug reports).
Apparently something broke since the *fix* mention in bug #40
------------------------------------------------------------------------
--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=1171&edit=1