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.""
Come on guys. I only had to stare at this story for a couple of seconds before I figured out that you're talking about the Linux kernel. But I shouldn't have to! Stop being so lazy!
What is people's hang up with 3.0? It will be that exact same code, except uname -v (do I remember the command line options?) will report 2.6.0 instead of 3.0.0.
Norris/Palin 2012
Fact: We deserve leaders who can kick your ass and field dress your carcass.
Regarding stability, I'm going to wait until at least 2.6.5 (give or take) before I upgrade my desktop machine. I like features, but I like stability more. For what it's worth (nothing), 2.4.20 has been quite stable for me, except that something on my computer leaks memory like a sieve (I'm guessing the binary nVidia drivers, but I'm not sure), so I have to reboot at least once a week, which is very annoying.
It's free software. Use 2.2 until something better (maybe 2.6, maybe the mythical 3.0, maybe the Hurd) evolves.
How about BSD?
Regular bugs and driver bugs are other people's departments. This list is for the Choosen Few who can actually write kernel code. I'm kinda surprised they even posted it here where all the idiots can harass those poor souls. Of course Wishlist items were out a while ago at feature freeze--again, don't waste their time-someone already decided what was in and what was out. They're looking for heavy duty programming that needs done. Systems to toss out and rewrite just because it won't work anymore. Bug fixes that have Fscked the system. Not petty requests from us!
It's a huge project. I mean they have to keep up with 2.4 patches, then adapt all the 2.4 things to 2.5 along the way, then add new features that break a bunch of stuff, then fix what they broke, then try to optimize things for stability and speed, then rewrite it because it's hosed, fix more stuff they broke...etc. It's a vicious cycle and few people in the world can do it!
So stop Whineing!