"We used to have these big and painful development releases that took several years, and it worked reasonably well. . .but it had serious downsides too.
Basically, a multi-year development cycle simply doesn't work. . . with 2.6, the base kernel is in good shape, and we've improved our development process. . .So instead of having two or three years between stable releases, we now have two or three months. Which means that the vendor kernels are much closer to the development kernels, and avoids a lot of the problems we used to have. Everybody is happier. So we'll probably stay with that model unless something really radical happens, and that means that we'll keep with the "2.6.x" codebase, and just incrementally improve on it."
|