-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 08/05/2017 15:49, Michał Górny wrote: > Dnia 8 maja 2017 15:27:18 CEST, Dirkjan Ochtman <d...@gentoo.org> > napisał(a): >> On Mon, May 8, 2017 at 12:49 PM, Mikle Kolyada >> <zlog...@gentoo.org> wrote: >>> Against. Do not touch things you are not working on, council >>> has >> already >>> dropped m68k s390 and sh to exp few years ago. Now we have a >>> big mess there and only, while ia64 sparc and co have slow but >>> progress and mature enough stable profiles. >> >> Obviously we should prevent big messes from happening. But it's >> a mistake that things I don't work on don't affect me -- work >> left over by lagging arch teams can affect me in many ways, in >> terms of having to keep older versions of my packages working and >> in the tree, and having to keep track of many more KEYWORDREQs >> and STABLEREQs. >> >> To me it's likely that the pace of stabilization for everyone is >> affected by the slower arches, in the sense that maintainers are >> less likely to stabilize newer versions if they see that arches >> can't keep up with previous requests. This means that even stable >> amd64 users are affected to some extent by ppc being slow to >> stabilize. > > Plus the usual mess of having to keep up with multiple large > stablereqs for stuff where we need to stabilize newer while some > arches are still two stabilizations behind. > > Not to mention when we want to stabilize a new version but the > arches still haven't even keyworded it...
That ! We can all face that our latency is not good for our traction on a wider user base. Freeing ourselves from this kind of latency is energy saving and thus a positive move imho. > >> >> Cheers, >> >> Dirkjan > > -----BEGIN PGP SIGNATURE----- iHUEAREIAB0WIQSqwxDKv5211qJQBiIqJBJLtlj6EwUCWRHIfQAKCRAqJBJLtlj6 EwmzAPwP2a6MgG3aE6EdSuPLjsabytT+qRskanNMJtiVsQqWpwD+NsGzWk9ff1RS 2mZYazWC5U9HBD3MzPG65jhX8Dl43jA= =h+5a -----END PGP SIGNATURE-----
