2.6 and 2.7 Release Management

An anonymous reader writes: "A recent discussion on the Linux kernel mailing list debated whether the upcoming 2.6 and 2.7 kernels should be released at the same time instead of first stabilizing the 2.6 'stable tree' then branching the 2.7 'development tree.' The theory behind the proposition is to keep "new" things from going into 2.6 once it is released, focusing instead only on making it stable. On the flip side of this argument is the possibility that with a 2.7 kernel in development, there will be too little focus on stabilizing the 2.6 kernel. The resulting debate makes for an interesting read."

Comments

In with the new, out with the old

[electricmonk]

It can only lead to improvement. Remember the whole affair of dropping in a completely new VM right in the middle of the supposedly "stable" 2.4 kernel branch? BSD has never had problems like these, and it pains me to see Linux doing silly stuff like that. I await the day when I can safely assume that something located in the "stable" branch really is stable.