Kind of sucks that the kernel has only one real release cycle that's effectively forced upon everybody , even those who don't run "debian stable" so to speak, and have such hardcore stability needs that they would rather delay applying a patch that fixes something known to be broken in order to avoid the much smaller possibility of a regression.
I say "effectively" forced upon everyone because nobody has the time to maintain a branch for backporting DRM and legitimate, "lower risk" fixes which just happen to land in the middle of a release cycle. Now that zen-unstable is dead, and linux-next isn't in what I'd call a usable state for most people, there aren't a lot of alternatives to the vanilla kernel.
There are release schedules for a reason. If someone want to add new features or fixes for old bugs, there is a time for that. -rc4 isn't it. I am sure reasonable exceptions can be made, but it seems like Linus feels the DRM people are abusing the process and just outright ignoring the schedule, and I don't think that is okay. The whole point of an RC cycle is to test things, and you can't test things properly if they keep changing.