If you give such a person a CD labeled 2.8.0, it will be viewed with much more suspicion than one labeled 2.6.40, and rightly so.
Why would the CD be labeled 2.8.0? It would be labeled RHEL 7 or Debian 7 or Ubuntu 12.4 LTS. It would not mention the kernel version at all.
Linux kernels have been stable at release for years. They don't do development releases anymore. They're all stable, incremental upgrades (there are development branches, but no devel releases that would ever make it into distributions or anything).
Neither of those groups will be negatively impacted by setting the kernel version to 2.8 (or 3.0)
(Y'all may be amused to hear that IBM never releases x.0 versions at all; they go straight to x.1.)
It's irresponsible of anyone paid to know this kind of thing to not be aware of how a project handles version numbers.
Linus is the kind of guy that would go to 2.8 just "because it's time" in his mind rather than some big feature jump. Whether or not a person agrees, it would be good for people to at least inform themselves.
Not all of our customers live up to your standard, however.
Linux 2.6.0 is 8 years older than Linux 2.6.38. But it's hard to tell. Linux 2003.12 vs Linux 2011.04 tells it all.
I routinely deploy software right off the version control. Exhaustively tested but, still, "pre-alpha".
When you need add features faster than you can exhaustively (as in aerospace-grade) test them, it's an act of balance. It has to work well enough to be useful, but it also needs to have the coolest features.
And it's not like, say, Windows, after about a quarter of a century, has been fully debugged.
Linux has not been extraordinarily successful at penetrating the desktop market. Where a lot of Linux lives is in the datacenter or the server farm. And if I'm a corporate IT drone, I want to know what is a major, disruptive upgrade and what is a minor upgrade. If you give such a person a CD labeled 2.8.0, it will be viewed with much more suspicion than one labeled 2.6.40, and rightly so. If you give one labeled 3.0, it will be filed in the dustbin until those zeros have become twos. Nobody's going to deploy a dot zero in a production environment.
Thus, giving the kernel what appears to be a big version bump for what is effectively a minor upgrade is going to freak out a lot of IT guys for no good reason. I remember IT shops which still ran 2.4 back in 2005ish because 2.6 was still 'too new'.
(Whether this attitude is legitimate or not is another question entirely).