| 1 |
On 03/14/2010 10:56 AM, Ryan Hill wrote: |
| 2 |
> On Sat, 13 Mar 2010 19:07:41 +0200 |
| 3 |
> Petteri Räty <betelgeuse@g.o> wrote: |
| 4 |
> |
| 5 |
>> When a bug is marked as fixed it doesn't show up in searches developers |
| 6 |
>> use so it's a matter of who reads the email and acts upon it. I don't |
| 7 |
>> see why maintainers would be any more likely to act than an arch team |
| 8 |
>> comprised of multiple people in the case of bigger arches. |
| 9 |
> |
| 10 |
> Hasn't the running theme for the last couple weeks been about not touching |
| 11 |
> packages you don't maintain and aren't throughly familiar with? ;) |
| 12 |
> |
| 13 |
> Anyways, it's simply not the arch team's job to fix the issues that pop up |
| 14 |
> unless they somehow caused them. If there's a bug in the ebuild an arch |
| 15 |
> tester missed it's the maintainer who is responsible for fixing it. |
| 16 |
> |
| 17 |
|
| 18 |
You misunderstood what I meant. The action I am talking about is |
| 19 |
reopening the bug. Any developer who notices that a bug should be |
| 20 |
reopened should reopen it so it gets noticed. |
| 21 |
|
| 22 |
Regards, |
| 23 |
Petteri |
Archives