Re: Bug Reminders - Feedback
| From: | Jan Schneider | Date: | Mon, 12 Jul 2004 18:37:55 +0000 |
| Subject: | Re: Bug Reminders - Feedback | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-31953@lists.php.net to get a copy of this message | ||
Zitat von Helgi Þormar <helgi@trance.is>:
On Mon, 2004-07-12 at 13:53, Jan Schneider wrote:The latter. But if you are volunteering to write the more complex solution and noone objects, by all means. Jan. -- Do you need professional PHP or Horde consulting? http://horde.org/consulting.phpZitat von Helgi Þormar <helgi@trance.is>:Hi guys I know ya all want to end this thread, but since this heated discussion came up about this, then I want ya feedback on how you guys want the bug reminders to work. At the moment the idea is to send 1 email to dev for each package he's a developer or lead in (okey I saw few people were against getting 1x email per package), the other idea was that each dev got one email with all bugs for all packages (takes quite much resources from the machine to pull this one off I'd think)Why don't you make it a single summary sent to pear-dev, just like the php bug report sent to internals? Should be done in a few minutes, is only one message per developer, shouldn't be annoying if sent once per month, and if you like so, has the side effect or creating a bit of pressure because everyone is seeing every bug of every package. Unless some developers feel offended by retrieving bug reports of packages they don't develop. Or by knowing that other see the bugs they didn't fix. Or by retrieving any qa messages at all. Or by pears being green.Well if ya read my other email, then the summary will also be sent ;) Or are you suggesting we only go with the summary ?