> 2.6.32 will be supported as a stable tree release for the next several years and will be shipped with the next RHEL and SLES.
... and probably the next Debian.
I've seen rumors/predictions (based on a leaked internal build name) for RHEL6-may-run-2.6.32; but this seems weak. Do you have more information about that?
That's the first time I've heard about the next SLES using 2.6.32 though. Is this a transcription of something Graned said, an LWN exclusive scoop, or something already known?
Posted Mar 4, 2010 15:38 UTC (Thu) by jake (editor, #205)
[Link]
> That's the first time I've heard about the next SLES using 2.6.32 though.
> Is this a transcription of something Graned said, an LWN exclusive scoop,
> or something already known?
I thought it was reasonably well-known, but could easily be mistaken. It *is* what Pete said, though. (He mentioned both RHEL and SLES).
jake
SCALE 8x: Ubuntu kernel development process
Posted Mar 4, 2010 18:36 UTC (Thu) by BenHutchings (subscriber, #37955)
[Link]
Pete must be confused. SLES 11 is only a year old so SLES 12 isn't due for some time. openSUSE has already moved on to 2.6.33.
SCALE 8x: Ubuntu kernel development process
Posted Mar 4, 2010 20:03 UTC (Thu) by jengelh (subscriber, #33263)
[Link]
And iff there was a new SLES branch right now, I am pretty sure it would use one of the openSUSE kernels - i.e. 2.6.31.
SCALE 8x: Ubuntu kernel development process
Posted Mar 6, 2010 3:59 UTC (Sat) by smoogen (subscriber, #97)
[Link]
I think the SuSE support for 2.6.32 is paying Greg KH to do that work.
Posted Mar 4, 2010 18:39 UTC (Thu) by BenHutchings (subscriber, #37955)
[Link]
... and probably the next Debian.
This was agreed this between the Debian and Ubuntu kernel teams. If the release slips a long way we might have to revisit it, but we are still intending to release with 2.6.32.
I've seen rumors/predictions (based on a leaked internal build name) for RHEL6-may-run-2.6.32; but this seems weak. Do you have more information about that?
My bug report on RHEL requesting a driver update from 2.6.33 was deferred to RHEL 6.1, so as far as I'm concerned this proves they are going with .32. However that bug report is non-public so I can't show you the evidence.