Linux: Reviewing the Development Process

The generally accepted path for introducing new code into the 2.6 Linux kernel is to first have it merged into Andrew Morton [interview]'s -mm kernel, and then after sufficient testing to have it merged into Linus Torvald's mainline kernel. In a recent thread on thelkml, this process was briefly discussed. Linus noted, "one issue is that I actually worry that Andrew will at some point be where I was a couple of years ago - overworked and stressed out by just tons and tons of patches." He went on to acknowledge that Andrew has written and enhanced numerous patch tracking tools, and that git merging helps, "but it still worries me," Linus said. "If Andrew burns out, we'll all suffer hugely."

Andrew replied, "I'm doin OK." He went on to explain, "patch volume isn't a problem [with regards to] the simple mechanics of handling them. The problem we have at present is lack of patch reviewing bandwidth. I'll be tightening things up in that area. Relatively few developers seem to have the stomach to do a line-by-line through large patches, and it would be nice to refocus people a bit on that. Christoph's work is hugely appreciated, thanks." He also suggested that the number of major features lined up for the kernel have been slowing down, hinting that some day the kernel will be a completed project, "as I said, famous last words. But we have to finish this thing one day ;)"