Something that is NOT mentioned here is the importance of filing every single bug encountered, even if you're not sure what package is actually the cause.
A good example is this: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1041625 I honestly don't think it's an "openchrome" problem so much as how we now handle non-3D-capable graphics since Ubuntu dropped unity-2d and metacity. But we all owe Lars a big round of applause for filing the original bug :^) I've added lots of info but there's still no response from someone knowledgeable enough to try and nail down the problem. I can't help but feel that posts like this are trying to scapegoat the testing community while the real problem lies with design and development :^( Lance --- On Thu, 8/30/12, Phill Whiteside <[email protected]> wrote: From: Phill Whiteside <[email protected]> Subject: [Lubuntu-qa] Fwd: Reporting Bugs To: [email protected] Date: Thursday, August 30, 2012, 2:38 PM Hi Guys, I know for some this is second nature; but for us mere mortals do take a read of the below. Regards, Phill. ---------- Forwarded message ---------- From: Nicholas Skaggs <[email protected]> Date: 30 August 2012 16:56 Subject: Reporting Bugs To: Ubuntu QA <[email protected]> I'm happy to report we're doing excellent work on finding bugs :-) Up until now, many of our bugs have been filed only against ubiquity, which then requires someone to manually triage if it's not a ubiquity bug. Since we know it's important to file the bug properly in order to get the bug seen and fixed, I worked with one of the ubiquity developers to put together a handy chart to help you when filing iso tracker bugs. This way, you can file it against the proper package and increase the odds it will be seen by the right developers in order to be worked and fixed. With that in mind, check out an example of what the bug reporting page now looks like: http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/22117/buginstructions Additionally, I would encourage all of you to read some of the bugsquad documentation on reporting bugs; https://help.ubuntu.com/community/ReportingBugs https://wiki.ubuntu.com/Bugs/FindRightPackage Think of this as essential reading for being a better bug reporter :-) Don't worry! I'm also still learning, and I trust I'm becoming better with each bug I file. The key is to put forth your best effort each time, and keep filing bugs. You'll learn as time goes on. Also, note that the bugsquad maintains an IRC channel as well #ubuntu-bugs, and can help support you should you run into some specific trouble on filing. As always, everyone on this list is also here to help. I hope these instructions clear some of the confusion surrounding what to do when something breaks during iso testing. Thanks! Nicholas -- Ubuntu-qa mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa -- https://wiki.ubuntu.com/phillw -----Inline Attachment Follows----- -- Mailing list: https://launchpad.net/~lubuntu-qa Post to : [email protected] Unsubscribe : https://launchpad.net/~lubuntu-qa More help : https://help.launchpad.net/ListHelp
-- Mailing list: https://launchpad.net/~lubuntu-qa Post to : [email protected] Unsubscribe : https://launchpad.net/~lubuntu-qa More help : https://help.launchpad.net/ListHelp
