Kernel 3.14 is the latest longterm release, would be nice to also stabilize the headers to this release.
3.16 is already stable (bug #528902).
(In reply to Jeroen Roovers from comment #1) what Jeroen said
Why would I install headers 3.16 for kernel 3.14?
(In reply to Tomas Mozes from comment #3) having a version of kernel headers newer than the actual kernel you're running shouldn't be a problem
Don't take me wrong, but is there anythink blocking marking the longterm headers as stable? I think it's kind of strange to have linux-headers 3.9, 3.13. 3.16 stable (those kernels are EOL) along with stable gentoo-sources 3.10, 3.12, 3.14, 3.17 (that is actually correct as those are mostly the longterm releases). Yes, anyone can unmask 3.10, 3.12 or 3.14 linux-headers but shouldn't we rather encourage using the same stable packages (not mixing stable and unstable)? I know that using newer linux-headers should not cause problems, but why should anyone try and not use what's more probable to work (same headers, same kernel)? Besides, those headers have been in the tree for months.
(In reply to Tomas Mozes from comment #5) headers are tracked independent of the kernel itself. we often stabilize the headers ahead of the kernel. versions older than the current stable are thus irrelevant.
