This is great. Thanks! Rolling release is fun, but for real work, when you need a new package now and can't risk downtime short term, it can be a serious and routine annoyance, usually just meaning you can't get the package you want when you want it.

Ok you asked for suggestions. An obvious enhancement is to back-port crticial fixes when possible in a way that rolls as few packages forward as possible... and maybe also non-critical fixes that are very useful but which have little or no impact on dependencies. This essentially creates something like a stable branch and a rolling development branch. This obviously is much more volunteer work though than just providing static repositories, which is already quite useful.

Edit:
Of course I should have read the link first. Now I see you already covered that point. Still, this is nice. Maybe the idea will get mainstreamed!

Yeah backports would be very useful, but as you said they require manpower! Never say never, if the idea is useful and people want to improve the repo with backports or other features, I would be very happy.
The important thing is to *never* introduce issues due to upgrades.