| 1 |
On Mon, May 8, 2017 at 12:49 PM, Mikle Kolyada <zlogene@g.o> wrote: |
| 2 |
> Against. Do not touch things you are not working on, council has already |
| 3 |
> dropped m68k s390 and sh to exp few years ago. Now we have a big mess |
| 4 |
> there and only, while ia64 sparc and co have slow but progress and |
| 5 |
> mature enough stable profiles. |
| 6 |
|
| 7 |
Obviously we should prevent big messes from happening. But it's a |
| 8 |
mistake that things I don't work on don't affect me -- work left over |
| 9 |
by lagging arch teams can affect me in many ways, in terms of having |
| 10 |
to keep older versions of my packages working and in the tree, and |
| 11 |
having to keep track of many more KEYWORDREQs and STABLEREQs. |
| 12 |
|
| 13 |
To me it's likely that the pace of stabilization for everyone is |
| 14 |
affected by the slower arches, in the sense that maintainers are less |
| 15 |
likely to stabilize newer versions if they see that arches can't keep |
| 16 |
up with previous requests. This means that even stable amd64 users are |
| 17 |
affected to some extent by ppc being slow to stabilize. |
| 18 |
|
| 19 |
Cheers, |
| 20 |
|
| 21 |
Dirkjan |
Archives