Frankly, "very out of date" when it is version 2.0.32 in debian testing and ubuntu current while the new, one month old version is 2.0.33 is overstated.
What are the features that are not in the debian stable package (2.0.31) or in 2.0.32 but are in the cutting edge 2.0.33 version? None of the bugs reported in the debian bug tracker seem to have been fixed by later versions!
With that said, you can make some but not all packages rolling-release with apt-pinning and using stable and sid or testing which are rolling.
> None of the bugs reported in the debian bug tracker seem to have been fixed by later versions!
Bingo. That is the #1 reason (the only reason?) that a package doesn't get promoted to Testing from Unstable, because it has known bugs and they haven't been fixed. This is Debian policy manual 101.
Fix the bugs, release a new version, if no more bugs are reported on the new version for two weeks, then it gets promoted to Testing (as long as it's not a freeze?) and it will be in next Stable after the freeze is completed.
With that said, you can make some but not all packages rolling-release with apt-pinning and using stable and sid or testing which are rolling.