The Must-Fix List For 2.6.0

Jeremy Andrews writes "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.""

Comments

You don't say

[Otter]

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.

Actually, accomplishing that would exceed the expectations I've evolved for 2.4.x. (That's the great thing about Linux performance -- if you don't like the VM, wait a day and it will change.)

Re:More lazy editors

[Otter]

In their defense -- the WSJ just pointed out this story about Fareed Zakaria:

Left-Of-Bush Brain Curry Man

Makes even Hemos' most astonishing efforts look lucid.

The Linux Information Minister

[Anonymous Coward]

Things we should not track here are:

- Regular old bugs. Please use bugzilla.

- Wishlist items. This list is not a route for getting commitment for inclusion of $FAVEFEATURE. In fact it's probably a good way of getting the feature shot down ;)

- Driver problems. Most important drivers mostly work OK now. Please use bugzilla.

So, these are all the things that should be fixed in 2.6, except the things that are broke, the things you want, and the things that don't work.

Not only that, if you do ask, they definately won't fix it. Love that open source.

but uhm

[nocomment]

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..."

Shouldn't we wait till the 2.4.x branch does that?