On Mon, Nov 10, 2008 at 04:47:02PM -0000, Teej wrote: > Hi guys, > > As per hggdh's request I have listed some bugs that I have helped to work > on as examples of my triaging abilities. > > 1. https://bugs.launchpad.net/ubuntu/+source/cairo-dock/+bug/296095 > 2. > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/295980 > 3. https://bugs.launchpad.net/ubuntu/+bug/295658 > 4. https://bugs.launchpad.net/ubuntu/+source/postgresql-8.2/+bug/294424 > 5. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/294339 > > 1. I would set this as Low, as it is a minor problem, and does not affect > many users. Also the problem seems like it could be just changing the > debian/control file or changing the menu entries, which shouldn't be a > really big task.
Your work here looks good and I like the fact that you put the exact package version you were testing with in the bug report and of course assigning it to the right package is a huge help! If the bug reporter's description is correct and this is a regression from Hardy to Intrepid I think the importance should be Medium instead of Low. > 2. I would set this as Medium, possibly High if more users report it. It > isn't a "trivial" problem as such, and it is hardware related, possibly > to all of these models of laptop, therefore it could have a bigger effect > than if it was specialised hardware. You've gathered a lot of information here and the bug report looks good to me. I agree with a Medium importance for this bug report and that if the bug receives duplicates or more people experiencing it that it should be bumped. > 3. Low importance, Medium if more users reported the same problem. > Demonstrating patience and helpfulness with newer users to Ubuntu who are > unable to properly file bugs or follow the Debugging Procedures. This looks good. Perhaps the debugging sound problems stock reply or the reporting bugs section of debugging sound problems should be updated so it is clearer to people what to do. > 4. Demonstrating my ability to browse through the log files and if I can, > help the reporter to solve the problem with upgrade/dpkg/apt problems. I > would again set this as Medium as it isn't a trivial problem, and I > believe this version of postgresql needs to be updated to resolve > conflicts between the 2 for future users with the same. Your work here is great and I'm glad you were able to help the reporter. Recently, the bug was marked as a duplicate of bug 294134 in update-manager. In main.log we can see the message "it's in the removal blacklist" which is something provided by update-manager but I don't think that is documented anywhere other than looking at the source for update-manager. > 5. I would set this to High as failure to boot the Live CD is a severe > problem, and I don't think it would affect enough users to be set as > Critical. There are a few things that can be done to improve this bug report a bit more. As the bug is likely hardware specific it would be good to identify the hardware in the bug's title. This might prevent comments from people with different hardware thinking that bug is their bug. This is especially true with a summary as generic as "Live CD does not boot". You can find the type of hardware in dmidecode which is attached to the bug report. Additionally, the kernel team still wants bugs assigned to specific teams - not subscribed as you've done. I agree with the importance you would give the bug report though. I've noticed that you've set quite a few bug reports without a package to a status of Confirmed. As a part of the triaging process it is very important to assign the bug to a package, even if it is a generic package like xorg so that the more knowledgeable people will look at the bug report and either reassign it again or work on fixing the bug. I realize its not always easy to find out what particular package a bug may be related to but there are lots of people who can help. Please e-mail the Bug Squad if you need assistance in determining what package to assign a bug report. I'd like to see you update bug 294339 and also assign the bugs that you've Confirmed without a package to the correct package. After you've completed these items please let us know and we'll be happy to look at your work again! Sincerely, -- Brian Murray @ubuntu.com
signature.asc
Description: Digital signature
_______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bugcontrol Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol More help : https://help.launchpad.net/ListHelp
