If a new kernel is released with bug fixes for various drivers but none of the hardware is in your computer, then why bother with the update? How many kernel updates have you done that made absolutely no difference to your platform? And each kernel update forces a reboot.
This is a kernel-related issue but would improve ubuntu.
@Auzy, valid point. But I also think it is wrong to push for reboots when not necessary.
Linux used to have long uptimes, now we regularly reboot just like we did with windows boxes.
As Linux supports more hardware, changes to the kernel will become more and more frequent, but how often will they really affect your platform?
Take servers for example, they rarely have new hardware added. Some kernel updates may be essential for a server, but most of the time they won't be. How can you tell without wading through pages and pages of the release notes?
To me, it seems more sensible to be able to check easily whether kernel updates affect a platform. When they do, update as usual; when they don't, allow the end-user decide what is action appropriate.
@MsG: I don't understand your comment. What is "it"?
I think you're all missing the point. Can you tell quickly whether a kernel update affects your platform without wading through pages of release notes? This is easy with a machine readable changelog. But hey lets not innovate.
This idea has been killed off without much thought. I'm close to giving up on brainstorm, most of the successful suggestions are little GUI enhancements. I have had ideas voted into oblivion and trashed only to to discover that the feature was already implemented. For me, brainstorm is braindead. ;-D