On Mon, Jul 13, 2015 at 02:21:32PM -0400, Steven Rostedt wrote: > I disagree. I thought next was a place to have integration of new > development, and not just a place to test. Really, how many people test > next compared to Linus's tree? I trip over bugs all the times in > Linus's tree that's been in -next for almost a whole release cycle. > The only bugs that I find that come from -next is integration issues, > where an interface changes and another subsystem stumbles over it. > That's exactly what it was for and what it's good at. In the embedded space it's much more common to track -next as people are often working with multiple subsystems so the integration is important. Most of my code is developed against -next then moved to topic branches for submission. We also catch quite a lot of issues in -next as a result of the work on boot testing that kernelci.org and Olof's bots are doing, hopefully that'll start to build out to include test suites like kselftest (I know there's work in progress there but no ETA as of yet). Things get exposed to a lot more systems and configurations than individual maintainers have access to which can shake out issues in code that deals with hardware. > > I think that this is a small mind-shift from thinking about Linus's tree as > > an integration tree to considering it as mostly bug-free code, and stop > > merging in risky patches. We already have -next for that. > No, we have -next as a way incorporate new code and see how things > interact with other subsystems. I think you're mostly agreeing with each other here (or at least talking about the definition of "mostly") - it's not an either/or thing. Exposure in -next does expand the audience and provide a lot of risk mitigation to what gets sent to Linus' tree as a result of that. That catches more than just integration issues between different trees, it also catches integration issues with a wider range of hardware and usage. Not as wide as you see for Linus' tree but wider.