On Wed, Jun 23, 2010 at 01:52:25PM -0500, Serge E. Hallyn wrote: > # Do you promise to be polite to bug reporters even if they are rude to you > or Ubuntu? > Yes > * Have you signed the Ubuntu Code of Conduct? > Yes > > * Have you read Bugs/HowToTriage, Bugs/Assignment, Bugs/Status and > Bugs/Importance? > Yes > > * Do you have any questions about that documentation? > Yes (But I've sent a separate email to ubuntu-bugsquad) > > * What sensitive data should you look for in a private Apport crash report bug > before making it public? See Bugs/HowToTriage for more information. > > Passwords/keys/CC#s/personal information in coredumps and > stack traces. > > # Is there a particular package or group of packages that you are interested > in > helping out with? > > Server bugs, qemu-kvm/libvirt, ecryptfs, lxc, kernel > > # Please list five or more bugs which you have triaged. These bugs should > demonstrate your understanding of the triage process and how to properly > handle > bugs. If there is a bug in your list that does not have an importance indicate > what importance (and explain the reasoning) you would give it after becoming a > member of Ubuntu Bug Control. Please use urls in your list of bugs. > > https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/597510 > I would have placed this one at low priority, as it > was not really a bug.
This seems fine and I'd agree with a low priority here. You might also look at http://launchpad.net/bugs/581959 as it is an apport-package bug report with the same exit status. > https://bugs.launchpad.net/ubuntu/lucid/+source/qemu-kvm/+bug/588293 I'd modify the title of this bug report to be very specific as it is likely to draw comments about the same symptom with different root causes. Additionally, someone may end up reopening it after it is fixed when they see a memory leak in qemu-kvm. I really appreciate the verbosity of your comments in this bug report and documenting tests. > https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/595427 > I'd place this at low priority, because it can be > worked around (by installing the distro). I'd disagree with the priority for this particular bug as getting people to test Ubuntu, which testdrive is one way to do, is very important additionally system lock ups like this should be a high priority. I wonder if this is a problem on real hardware. > https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/595388 > I'd place this at low priority, because it can be > worked around. This seems fine. > https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/594836 > I'd leave this at undecided since we don't yet > know whether it can be reproduced. Your work here looks good. Due to the large volume of bug reports about Ubuntu I recommend setting the importance of a bug report as soon as possible, even if you have not been able to recreate it, so that you have another mechanism for sorting bug reports. It is quite easy to downgrade the importance later. Based on the quality of your work I am happy to approve your membership in the Ubuntu Bug Control team. -- Brian Murray
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
