Re: Bug Summary/Reminder Timeframe - Last Call!
| From: | bertrand Gugger | Date: | Sun, 12 Dec 2004 02:32:00 +0000 |
| Subject: | Re: Bug Summary/Reminder Timeframe - Last Call! | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-2178@lists.php.net to get a copy of this message | ||
Helgi Þormar wrote:
With 1 or 2, could be done, but I think they are aware. By 5 or 10, should be reminded. But one bug by one bug all along the "4 weeks" Toujours à+ -- bertrand Gugger (toggg) >That is if the package has open bugs or bugs in feedback. > >That generates around 200 emails, which is not much I'd say. > > > >>>There is only one email per package, so it won't be a overload, >>> >>> >>> >>The PEAR machinery is actually that quick, it's no machine overload I >>would fear. >>And even if the machines would send only 1 message each second >>then over 4 weeks is time enough to send 2 millions bugs >>PEAR is perhaps bad but never that much :-) >> >> > >Like I said, it's the whole package count - packages that haven't gotten >any open bugs or bugs in feedback mode > > > >>>if >>>leads/developers don't want to get emails for this, then there is a >>>simple solution to that problem, fix those bugs :) >>> >>>Ohh yeah, this bug summary things has nothing to do with the state of >>>PEAR :) (actually what did you mean by state of PEAR, the package ? or >>>?) >>> >>> >>> >>> >>Present state: what bugs are there to be reminded. >> >> > >Uhmm, bugs in the open state or in feedback mode. > >- Helgi > > > > >Just the count of what should be sent now. What's the top for one person (don't tell who's that) ?Ehmm if a developer gets 1x email per package they are Lead/Developer on, then some get 5 some get 2 some get 10 or so. Those with 0 are not reminded.