Re: Bug Summary/Reminder Timeframe - Last Call!
| From: | Helgi Þormar | Date: | Sun, 12 Dec 2004 02:18:08 +0000 |
| Subject: | Re: Bug Summary/Reminder Timeframe - Last Call! | ||
| References: | 1 2 3 4 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-2175@lists.php.net to get a copy of this message | ||
On Sun, 2004-12-12 at 00:23, bertrand Gugger wrote:
> Helgi Þormar wrote:
>
> >On Sat, 2004-12-11 at 21:43, bertrand Gugger wrote:
> >
> >
> >>Hi,
> >>In the present state of PEAR,
> >>what would be the first bunch of messages.
> >>What is the list of packages'bug now more as 4 weeks old ?
> >>
> >>Is it to be sent to "lead" only or everybody responsible on this pckg ?
> >>à+
> >>
> >>
> >
> >This really tells me that you didn't read any of the posts about this.
> >
> >Only Leads and Developers(the state that is) get those emails, it
> >doesn't email 4 weeks old or older bugs only, it just emails all.
> >
> >
> I try to read, was ment as a reminder, as no searchable archives there :-P
>
> >Don't get what you mean with first bunch, but I guess the answer that
> >your looking for is all bugs with the state Open (which has verified,
> >analyzed and more) and also feedback.
> >
> >
> 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.
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