Posted May 24, 2011 6:33 UTC (Tue) by corsac (subscriber, #49696)
In reply to: Date based by dlang
Parent article: 2.8.0?
> if you think that the latest 2.6.32 really has all the fixes that are in 2.6.39 you are sadly mistaken.
If you read again, you'll see I didn't say that.
> yes, 2.6.39 contains some bugs that aren't in 2.6.32.x as well, and each organization should balance the risk of new bugs vs the risk of bugfixes not getting backported.
2.6.39 (and all release since 2.6.33) are just that: new releases, with tons of new stuff added, stuff removed, lot of changes etc. 2.6.32 is *stable* release, which is something people really needed, especially at the kernel level. And it does get a lot of fixes, either directly or backported when needed.
On top of that, distributions do a good job filling the gap of the new hardware support by carefully backporting some drivers changes when needed.