| 1 |
On Tue, Dec 12, 2017 at 12:24 PM, Rich Freeman <rich0@g.o> wrote: |
| 2 |
> On Tue, Dec 12, 2017 at 1:15 PM, Michał Górny <mgorny@g.o> wrote: |
| 3 |
>> |
| 4 |
>> It seems that we've started lacking arch testers for AMD64 architecture. |
| 5 |
>> At this moment, there are already 159 bugs in amd64 backlog, and there |
| 6 |
>> is no noticeable progress. New stabilization requests are usually |
| 7 |
>> handled much faster by x86, sparc and hppa teams! |
| 8 |
>> |
| 9 |
>> If you have a stable AMD64 system and would like to help arch testing, |
| 10 |
>> please do! I don't know what exact rules for that are but I think [1] |
| 11 |
>> could be helpful. If someone knows better, then please share. |
| 12 |
>> |
| 13 |
> |
| 14 |
> As far as I'm aware the standing policy already exists that |
| 15 |
> maintainers can stabilize their own packages on amd64. |
| 16 |
> |
| 17 |
> That said, if somebody wants to organize an AT program for amd64 they |
| 18 |
> should feel free to do so. I could explain how things used to work at |
| 19 |
> least if that is helpful. |
| 20 |
> |
| 21 |
> The old way it used to work is that ATs had to pass the ebuild quiz |
| 22 |
> and they would get editbugs privs to tag bugs as tested. I won't |
| 23 |
> elaborate here unless there is interest... |
| 24 |
> |
| 25 |
|
| 26 |
I would like to know. But on the other hand, anyone interested in |
| 27 |
contributing to packages they work with is likely already doing so. On |
| 28 |
the third (and final?) hand, it may also be that there are people |
| 29 |
looking for direction. |
| 30 |
|
| 31 |
Cheers, |
| 32 |
R0b0t1 |
Archives