For Programmers: Free Programming Magazines  


Home > Archive > PHP PEAR Questions and Answers > July 2004 > Re: [PEAR-QA] Suggestion for bug reminders (pearweb)









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: [PEAR-QA] Suggestion for bug reminders (pearweb)
Lukas Smith

2004-07-12, 3:59 pm

Klaus Guenther wrote:

> Perhaps a good solution would be to provide the following options on the
> dev account page:
>
> * Reminders for all categories of reports (Bug + Feature Request)
> * Reminder for only Bug category


I dont think providing options is the way to go. Just makes the system
needlessly complex.

> Do not remind unless a report is more than ... old:
> * one w
> * two ws
> * four ws
>
> That way, you'd only get reminders if you've got something older than
> you want to deal with.
>
> Also, we could add a severity level to the bugs like they have on
> sourceforge. And there would be different classes of severity (e.g.,
> 0-9) but the developer could only suppress bugs under severity 5(he
> could select from 0 - 5) from the reminders. Bugs with severity 8 or 9
> would get wly reminders, with bimonthly reminders for less critical
> bugs and only a monthly reminder for feature requests (if that is
> selected). When a bug gets submitted, it automatically gets assigned
> priority 0. Logged in developers could assign a priority to ensure that
> major bugs have a higher priority than minor bugs.
>
> I think this would satisfy most developers who may not even need the
> reminders.


Helgi could you list the concept that you proposed to me?

Anyways I dont think we need wly reminders. But maybe bi-wly or
monthly should be enough. The critical issues we spot we can maintain on
our own. I dont know how much performance this might eat but ideal would
be 1 single reminder email per developer. If this eats too much
performance then 1 email per package. These mails would use a similar
format as people might know from the internals summary email.

regards,
Lukas Smith
smith@backendmedia.com
_______________________________
BackendMedia
www.backendmedia.com
berlin@backendmedia.com

Linn Zwoch Smith GbR
Pariser Str. 44
D-10707 Berlin

Tel +49 30 83 22 50 00
Fax +49 30 83 22 50 07
David Costa

2004-07-12, 3:59 pm


On Jul 12, 2004, at 3:05 PM, Lukas Smith wrote:
[color=darkred]
> Klaus Guenther wrote:
>
>
> I dont think providing options is the way to go. Just makes the system
> needlessly complex.
>


What about having the bugs report by severity ( time based..how long
the bug has been outstanding etc) on the qa list mailed wly ? a sort
of report as the one used on php-internals ?

That would make very easy to me and every QA member/developer to
"bother" the developers with critical/long pending bugs and leave alone
the new ones.

Cheers
David Costa

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com