ubuntu-bugcontrol team mailing list archive

[C de-Avillez <hggdh2@xxxxxxxxxx>]

On Wed, 25 Aug 2010 15:39:10 +0100
Jack Leigh <leighmanthegreat@xxxxxxxxxxx> wrote:

(reformatted to more clearly show responses)

> 
> ~ Do you promise to be polite to bug reporters even if they are rude
> to you or Ubuntu? Have you signed the Ubuntu Code of Conduct?

> Yes
> 
> ~ Have you read Bugs/HowToTriage, Bugs/Assignment, Bugs/Status and
> Bugs/Importance? Do you have any questions about that documentation?

> Yup as well as https://wiki.ubuntu.com/WineTeam/Contributing and
> talking to Scott Richie.  No immediate questions.
> 
> ~ What sensitive data should you look for in a private Apport crash
> report bug before making it public? See Bugs/HowToTriage for more
> information.

> Make sure there is never a Coredump.gz and check that
> stacktraces don't contain any personal details

> ~ Is there a particular package or group of packages that you are
> interested in helping out with?

> Wine -- upstreaming as well as triaging bugs for the 'wine' package,
> seeing whether they are still relevant to current/'wine1.2' release
> and upstreaming. Many have upstream bugs but are not marked as
> triaged.

> ~ 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.

> Would set importance according
> to https://wiki.ubuntu.com/WineTeam/Contributing, setting upstreamed
> bugs to Triaged

Actually, no, You are expected to set the importance according to
*Ubuntu* rules [1]. Upstream's importance does not really play here
(although, most of the times, Ubuntu and upstream do match).

But, anyway, you did not indicate what importance you would have set
on any of the bugs below.
 
> https://bugs.edge.launchpad.net/ubuntu/+source/wine1.2/+bug/607970

Thank you for upstreaming this bug. Good work (and I also frankly
doubt if it will be resolved, but who knows).

> https://bugs.edge.launchpad.net/ubuntu/+source/wine1.2/+bug/614546

Why did you mark it Fix Released for wine-1.2 (Ubuntu)? Have we
already published the fix on Maverick? I do not think so, since the
fix is on Wine 1.3.1. The actual stati should be:

Fix Released for the upstream
Triaged for the Ubuntu task.

A bug is only considered Fix Released on Ubuntu when we publish the
fixed version.

> https://bugs.edge.launchpad.net/ubuntu/+source/wine1.2/+bug/479223
> -- added link to already filed upstream

Thank you for the upstream link.

> https://bugs.edge.launchpad.net/ubuntu/+source/wine1.2/+bug/601715

OK. What was triaged here?

> https://bugs.edge.launchpad.net/ubuntu/+source/wine1.2/+bug/502375
> -- duped a number of bugs which display the same symptoms to it,
> requested more information about other sound-related bugs which
> don't seem immediately linked to this

Ugh! Sound bugs are nasty. It might be worth the time to check with
the sound/pulseaudio experts. The only issue I have here is the fact
that there are three different releases of Ubuntu (and two-ish of Wine)
playing, not counting the sound stack.

All in all, a nice work, but needs more attention to the triaging
documentation. I still want like to know what would you set as
Importance on these bugs.

Vote as of now is, then,

0.

Cheers,

[1] https://wiki.ubuntu.com/Bugs/Importance

-- 
C de-Avillez
IRC: hggdh

This email (and any attachments) is digitally signed using GNUpg
(http://gnupg.org). The public key is available at http://pgp.mit.edu.
The key Id is 0xD3133E56.

Attachment: signature.asc
Description: PGP signature