Re: [gentoo-dev] Suggestion about how to tell ATs that a package can be stabilized on all arches at the same time

[Jeroen Roovers]

On Sun, 08 Feb 2015 11:17:19 +0100
Pacho Ramos <pacho@g.o> wrote:

> Many times has raised the question about how we could handle those
> packages (like icon packs, wallpapers...) that are not arch dependent
> and, then, could be stabilized all at the same time by the first arch
> team that is going to stabilize it.

If you do that, then what is the point of having a stable request in
the first place? The many-eyeballs argument is gone then, so what are we
left with?

It isn't a team that is doing the stabilisation, it's a single person
who may or may not have looked at what the new version does and how
well it installs, and may or may not feel some pressure to rush it.

As I said before many times, having more people on more architecture
teams look at the same problem actually helps catch bug at a late
stage but arguably still in time. Removing or weakening that last line
of defence (either by having a single person do stabilisations for
multiple architectures, or by removing most architecture teams from each
single task) will increase the bug rate for stable ebuilds (even more).


     jer