Summary: | Test Bug For PulseAudio | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | Colin Guthrie <colin> |
Component: | pavucontrol | Assignee: | Arun Raghavan <arun> |
Status: | RESOLVED FIXED | QA Contact: | pulseaudio-bugs |
Severity: | normal | ||
Priority: | medium | CC: | lennart, tanuk |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Colin Guthrie
2011-05-22 08:07:19 UTC
Testy test tester testington. I got the following mail: https://bugs.freedesktop.org/show_bug.cgi?id=37467 --- Comment #1 from Colin Guthrie <fdo@colin.guthr.ie> 2011-06-12 11:38:45 PDT --- Testy test tester testington. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ pulseaudio-bugs mailing list pulseaudio-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs I noted that the mail claimed that I was the assignee for the bug, but actually pulseaudio-bugs@lists.freedesktop.org is the assignee. Does the bug mailing list require all bugs to be assigned to the list? Can we assign bugs to any real people without breaking the mailing list? (In reply to comment #2) [...] > I noted that the mail claimed that I was the assignee for the bug, but actually > pulseaudio-bugs@lists.freedesktop.org is the assignee. Does the bug mailing > list require all bugs to be assigned to the list? Can we assign bugs to any > real people without breaking the mailing list? One easy way to find out. Testalicious So I guess that broke it sending to the list then :( I guess we cannot do an "always CC" type thing? There's the default CC feature that should work: http://www.bugzilla.org/releases/3.0/new-features.html#v30_feat_cc I don't know how to configure default CC addresses, though. According to the documentation they can be specified when creating a component - if there's a way to edit a component after it's created, I'd expect the default CC list can be edited in the same place. (In reply to comment #6) > There's the default CC feature that should work: > http://www.bugzilla.org/releases/3.0/new-features.html#v30_feat_cc > > I don't know how to configure default CC addresses, though. According to the > documentation they can be specified when creating a component - if there's a > way to edit a component after it's created, I'd expect the default CC list can > be edited in the same place. Hmm, yeah maybe... But perhaps that doesn't happen when the address is the assignee too? Easy enough to fix if we just make a new alias for e.g. "newbugs(at)pulseaudio.org" and make it the default assignee. Adding Tanu to the CC ;) So do the components already have the pulseaudio-bugs ML on CC? I'd imagine it should deal with having the field in assignee and CC just fine. I've asked here: https://bugs.freedesktop.org/show_bug.cgi?id=38283 OK, so as per the above linked bug, Daniel has set the QA contact to the list. Therefore it should always get mails. This should include this ticket too I guess, so hopefully we will see it on the list even tho' the list is not in the CC list. Resetting QA contact Ahh now the QA contact is set up, the list should get all mails :) I think we can close this bug now :D (In reply to comment #13) > Ahh now the QA contact is set up, the list should get all mails :) > > I think we can close this bug now :D How are we going to use the bug states beyond RESOLVED? Do we care about VERIFIED and CLOSED at all? IMO we can just stick to having RESOLVED being the end of the bug since it keeps the flow simple. I'm not very fixed about this, though. I also feel that RESOLVED is a good enough end point. Agreed. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.