On Thu, Jan 31, 2013 at 3:58 PM, Ephraim Purcell <[email protected]> wrote: > Hi Rob, I've inputted some comments etc on the bugs assigned to me. Would > appreciate some feedback and another batch if appropriate. Many thanks. >
Hi Ephraim, I reviewed the defect reports you worked on. It looks like your analysis was good on these ones, and you have a couple confirmed bugs for the developers to now look at. Good job! One thing I'd ask you (and everyone else as well) to do is to always be pushing these bugs to resolution, one way or another. We don't want to have them linger too long in the unconfirmed state. They don't help anyone if they are in that state. The OpenOffice project (IMHO) dropped the ball for a period of time and that is why we have a backlog like this. So if you try to reproduce a bug report and you cannot, then you should make a choice: 1) Do you need more information from the user? Maybe additional details in the steps? Maybe a test document? If so, make your request in a comment and set the keyword field to "needsmoreinfo". Every month or so we'll close all old "needsmoreinfo" reports where the user never responded. or 2) If you cannot make the bug occur, and you don't need more info then it is time to resolve the report. Maybe it was fixed already? Maybe the user had something weird going on in their system? Mark the report as Resolved/Irreproducible. or 3) Maybe it is not a bug at all but a request for a new feature or an enhancement. If so, change the issue type to Enhancement of Feature Request. or 4) Maybe it is not a bug at all. The product is working that way intentionally. Or maybe the user is asking a "how to" question and not reporting a bug. if so, point them to the support forums (if appropriate) and close the report as Resolved/Invalid. So one way or another, the bug report is resolved. Either you are waiting for more information from the user, or you are marking the bug as Resolved. That is how we keep the queue managed. So if you could go back and take another look at your unresolved ones, and decide what state they should go into next, that would be great. And I'll get you another batch to look at. Thanks! -Rob > > On Fri, Jan 18, 2013 at 4:54 PM, Rob Weir <[email protected]> wrote: > >> I think I've responded to all requests for batches of bug reports to >> review. But if I missed anyone, or there are any other outstanding >> questions, please let me know. >> >> -Rob >>
