On Wed, Oct 21, 2015 at 08:20:54AM -0700, Guenter Roeck wrote:

> Number of build and runtime breakages in -next is a bit high, and fixes are
> sometimes slow to roll in. At least in part this is because those responsible
> for breakages are not informed, but I have also seen problems which were
> known for weeks to propagate into mainline before they got fixed, even if
> the culprit was informed. This could use some improvement, though I am not
> really sure how we could get there. Make more noise ?

Noise is probably a large part of it, having a human following up about
issues seems to help a lot.

I've seen some active resistance to pushing fixes to mainline without
lengthy soaks in -next in a very rules based fashion which isn't super
awesome when it takes out other testing due to the breakage.  As the
test coverage improves this is going to be getting to be more and more
of an issue as failures to build or boot will cause gaps in other
testing.