| Report new bug | New search | Development Roadmap | Status: Open | Feedback | All |
| Request #562 | send bug summary to pear-qa | ||
|---|---|---|---|
| Submitted: | 2004-01-13 10:33 UTC | ||
| From: | smith at backendmedia dot com | Assigned: | dufuz |
| Status: | Closed | Package: | Bug System |
| PHP Version: | Irrelevant | OS: | Irrelevant |
| Roadmaps: | (Not assigned) | ||
[2004-01-13 10:33 UTC] 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.
Comments
[2004-02-20 14:40 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send MANUAL CONFIRMATION IS NOT POSSIBLE. Write a message to pear-dev@lists.php.net to request the confirmation link. All bugs/comments/patches associated with this email address will be deleted within 48 hours if the account request is not confirmed!
[2004-02-20 15:14 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send MANUAL CONFIRMATION IS NOT POSSIBLE. Write a message to pear-dev@lists.php.net to request the confirmation link. All bugs/comments/patches associated with this email address will be deleted within 48 hours if the account request is not confirmed!
[2004-02-20 16:00 UTC] neufeind at php dot 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 16:16 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send MANUAL CONFIRMATION IS NOT POSSIBLE. Write a message to pear-dev@lists.php.net to request the confirmation link. All bugs/comments/patches associated with this email address will be deleted within 48 hours if the account request is not confirmed!
[2004-02-20 16:29 UTC] neufeind at php dot 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 17:31 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send MANUAL CONFIRMATION IS NOT POSSIBLE. Write a message to pear-dev@lists.php.net to request the confirmation link. All bugs/comments/patches associated with this email address will be deleted within 48 hours if the account request is not confirmed!
[2004-04-27 03:38 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send MANUAL CONFIRMATION IS NOT POSSIBLE. Write a message to pear-dev@lists.php.net to request the confirmation link. All bugs/comments/patches associated with this email address will be deleted within 48 hours if the account request is not confirmed!
[2004-12-22 14:32 UTC] User who submitted this comment has not confirmed identity
If you submitted this note, check your email.If you do not have a message, click here to re-send MANUAL CONFIRMATION IS NOT POSSIBLE. Write a message to pear-dev@lists.php.net to request the confirmation link. All bugs/comments/patches associated with this email address will be deleted within 48 hours if the account request is not confirmed!