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
Ubuntu-qa@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
