| 1 |
On 03/12/2010 10:11 PM, Jeremy Olexa wrote: |
| 2 |
> |
| 3 |
> On Fri, 12 Mar 2010 21:18:03 +0200, Petteri Räty <betelgeuse@g.o> |
| 4 |
> wrote: |
| 5 |
>> There seems to be two different schools on who to assign a keywording |
| 6 |
>> bug with only a single arch. I have myself assigned it to the arch in |
| 7 |
>> question but there's a difference of opinion here: |
| 8 |
>> http://bugs.gentoo.org/show_bug.cgi?id=272160#c5 |
| 9 |
>> Let's get agreed on a single approach and I will add a note here: |
| 10 |
>> http://devmanual.gentoo.org/keywording/index.html |
| 11 |
>> I naturally support the approach I have been doing as I think the arch |
| 12 |
>> team is the one in charge. |
| 13 |
> |
| 14 |
> The "problem" with assigning bugs to arch teams is when the user comments |
| 15 |
> on the bug after it is resolved. If the arch team is CC'd, they remove |
| 16 |
> themselves when done and any comments after the bug is closed goes to |
| 17 |
> someone that is interested. If the arch team is assigned, then the comment |
| 18 |
> basically goes to /dev/null. So, if we are to improve the user experience, |
| 19 |
> assign to maintainer and CC arch team. |
| 20 |
> |
| 21 |
> -Jeremy |
| 22 |
> |
| 23 |
|
| 24 |
When a bug is marked as fixed it doesn't show up in searches developers |
| 25 |
use so it's a matter of who reads the email and acts upon it. I don't |
| 26 |
see why maintainers would be any more likely to act than an arch team |
| 27 |
comprised of multiple people in the case of bigger arches. Let's not |
| 28 |
forget that users are really supposed to open new bugs instead of |
| 29 |
commenting on the resolved ones although I know there are users out |
| 30 |
there who rather comment on a two year old only distantly related bug |
| 31 |
than open a new one. |
| 32 |
|
| 33 |
Regards, |
| 34 |
Petteri |
Archives