On Tue, Jul 25, 2017 at 10:13 AM, Michał Górny <[email protected]> wrote: > > I feel like this is going towards 'anybody can do keywording / > stabilization'. I'd rather not go this route right now, and just let > arch teams recruit people as they see fit. >
I think this depends on the arch team. Back in the early days of amd64 I was an AT and an early adopter in general. There were a lot of bugs with types/etc and broken assumptions. It was helpful to have a team that was familiar with the most common problems and which had the hardware to test things. Now we never see an amd64-specific issue because that is what all the upstream projects do their own QA using. If anything we'd be more likely to see x86 bugs, but most people have learned how to use types correctly/etc, and I suspect this has benefited other architectures as well. I saw an analogous situation with systemd. In the early days we were writing a lot of units. These days it is just dealing with one-offs as much of the work is now upstreamed. I think that the more mainstream something is, the less the need for specialized teams to deal with every issue. Sure, somebody could always escalate a sticky problem, but having an arch team do every stabilization seems like having the gcc team look at every build error. -- Rich
