| gf2 | Hello again. I am learning to triage bugs. I have contacted reporters for several old bugs (2008-2009). Some have replied right away to say I should close the bugs which I have. How long should I wait for a response from the others? Perhaps 1 week? Then, what should I do? Should I label the bug as "incomplete" because of the lack of response? | 00:10 |
|---|---|---|
| wxl | gf2: i would advise attempting to reproduce yourself in supported versions. if you can't do so or it's not clear how to do so, that seems appropriate. invalid may also be appropriate if it's only relevant to old versions, but that requires more work to confirm, so i'd avoid it. | 00:12 |
| wxl | gf2: if it's incomplete, it will be closed after 60 days of inactivity automatically | 00:13 |
| gf2 | ok, thanks wxl! I will go with "incomplete" after 1 week. These are all regarding Thunderbird and I have not found any that I could replicate. Many seem to be special situations like a specialized type of email they have received. I am watching for items that I can try to replicate but I haven't found any yet and I have reviewed about 30 bugs. | 00:21 |
| wxl | gf2: it doesn't hurt to render them incomplete at the same time that you ask for an update. if the report was complete for an old unsupported version, it's most likely incomplete for supported ones. do ask them to check the current versions. also, i'd advise doing the "easy" bugs first, i.e. try to avoid the specialized situations. :) | 00:23 |
| gf2 | Thanks for the advice, wxl. I am having a tough time finding *easy* bugs to test/confirm. I thought since I recently installed Thunderbird (2 days ago), I could test thunderbird bugs. But I found all these old ones. But that is a good idea to mark them "incomplete" at the same time as I contact them. I shall do that. | 00:28 |
| wxl | gf2: often times things that involve network protocols can be problematic, as are things that are specific to particular pieces of hardware. you might have better luck working on gui elements or simple applications. | 00:29 |
| gf2 | I have been using this standard wording when I comment the bugs: Hello <name>. Thanks for submitting this bug and reporting a problem with Thunderbird. | 00:29 |
| gf2 | You made this bug report in 2008 regarding Thunderbird and there have been several versions of Thunderbird since then. | 00:29 |
| gf2 | Could you confirm that this is no longer a problem and that we can close the ticket? Or, if it is still a problem, could you come to Launchpad and make a comment to that effect? | 00:29 |
| gf2 | Thank you again for helping make Ubuntu and Thunderbird better. | 00:29 |
| gf2 | G | 00:29 |
| wxl | pretty good | 00:29 |
| wxl | you can see stock responses here: https://wiki.ubuntu.com/Bugs/Responses | 00:29 |
| gf2 | Is that ok? | 00:29 |
| gf2 | ok, good. I will check that responses site. | 00:30 |
| wxl | you also might want to incorporate the likes of: | 00:31 |
| wxl | https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29 | 00:31 |
| wxl | https://wiki.ubuntu.com/Bugs/Responses#Old_untouched_bugs | 00:31 |
| wxl | note at the top that there is a firefox extension available to make use out of those | 00:31 |
| wxl | i'm not sure they still work given firefox has moved to that different add-on format | 00:32 |
| gf2 | oh, ok. I will explore that. I was copying and pasting from a word document. | 00:32 |
| wxl | webextensions | 00:33 |
| wxl | that's what it's called | 00:33 |
| wxl | it's based off of greasemonkey which seems like it shuold work https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ | 00:34 |
| gf2 | ok :) | 00:34 |
| gf2 | thanks again, wxl :) | 00:36 |
| wxl | thank YOU gf2 for helping others help make ubuntu better XD | 00:41 |
| gf2 | :) | 00:50 |
| === alan_g is now known as alan_g_ | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!