Feedback on bug reports

Hasan Aljudy hasan.aljudy at gmail.com
Sun Mar 11 22:13:34 PDT 2007


Maybe because the current bug-tracking system is a bit messy and not 
very user-friendly. (or is it just me?)

David Ferenczi wrote:
> Hi Walter,
> 
> do you see it possible to give some more feedback on reported bugs?
> 
> There are quite many bug reports (some of them are fairly old) left without
> any comment, confirmation/rejection. This leaves the reporter in
> uncertainity (will it be fixed?, how long will it take?), which isn't
> really inspitring.
> 
> IMO the following would greatly improve the process:
> 
> 1. If a new bug is reported, it should be confirmed or rejected shortly
> after it's been reported. This is also a good occasion to ask the reporter
> for further information or action, if they are needed. This makes a good
> impression on the reporter, that the bug is taken care of.
> 
> 2. If the bug is confirmed it should be also (re)prioritised. This helps the
> reporter to estimate how long will it take to fix the bug. Is it due in one
> of the following releases or maybe someday?
> 
> 3. Special attention to older bug reports or reconsidering the priorities
> from time to time may help not to have these aging bugs around.
> 
> 
> I hope that the above ideas may be applied for your day to day work without
> major effort.
> 
> 
> Regards,
> David
> 
> 
> 
> 
> 
> 



More information about the Digitalmars-d mailing list