RHEL 5.4 released

with a 3-month release cycle, the amount of new things that are found tapers off towards the end of the three months. delaying the release longer doesn't gain as much as you would like to think.

there is usually a 2-3 week time period where there are not many known regressions (there are very seldom none, and it's not unusual for a reported regression to actually be related to a change that was introduced several releases ago), the reason these regressions don't get fixed is that they are hard or impossible for the kernel developers to duplicate. what they can't duplicate they can't fix. if what caused the problem can be identified, but not fixed easily, it's usually reverted (specificly to avoid regressions), the one exception to this is if the fix is deemed 'important' enough (usually a security issue)

note that arguments along the lines of 'but it fixes far more boxes than it breaks' are _not_ allowed.