| 1 |
Stuart Herbert wrote: |
| 2 |
|
| 3 |
> |
| 4 |
>The introduction of the x86 arch |
| 5 |
>team will, at some point, turn the x86 arch team into a bottleneck (just |
| 6 |
>like all the other arch teams already are) |
| 7 |
> |
| 8 |
> |
| 9 |
A possible way to alleviate this is proactivity on the maintainer's |
| 10 |
part. Our current rule for going testing->stable is 30 days. If we |
| 11 |
could alert the arch teams x number of days in advance they could test |
| 12 |
it before the end of the period minimizing delays. Since all arch teams |
| 13 |
would need this alert a relevant script could be created/modified. |
| 14 |
|
| 15 |
I realize this doesn't help if the arch teams are just plain too busy. |
| 16 |
Hopefully the 'fast arch' losing its speed will show people that we need |
| 17 |
more help in testing and bring more people on board. |
| 18 |
|
| 19 |
-- |
| 20 |
Joshua Baergen |
| 21 |
-- |
| 22 |
gentoo-dev@g.o mailing list |
Archives