[ Thanks to Jeremy
Andrews for this link. ]
“Andrew Morton posted a lengthy list of items that need to be
done before the 2.5 development kernel tree should be turned into
the 2.6 stable kernel tree. He prefaced his list by noting that
2.6.0 does not mean, ‘it’s finished, ship it,’ alternatively
offering:“‘I’d propose that 2.6.0 means that users can migrate from 2.4.x
with a good expectation that everything which they were using in
2.4 will continue to work, and that the kernel doesn’t crash,
doesn’t munch their data and doesn’t run like a dog. Other
definitions are welcome.’“Andrew’s list does not include ‘regular old bugs’ (which should
be tracked in bugzilla), wishlist items, nor most driver problems.
Instead, ‘Things which we should track here are significantly-sized
outstanding development activities which resolve big bugs or which
address missing features & speedups.’ Read on for the complete
(and lengthy) list, which is broken into three sections: must-fix
bugs, late features and speedups, and important driver bugs…”