Hello Kevin, thank you for responding.
Maybe "Rolling Release" means something different to me than everyone else. To me, it doesn't necessarily mean cutting edge packages, only that there is no OS version number (like version 19, 20, etc). So, my thought to make things as easy to maintain (for spin maintainers) as possible is to simply serve 6 month old packages as long as they haven't had a security update.
I don't know what it would take though. Would this stable RR need hosting for all its own packages, or would it be it simply be enough to have a URL to alias to the current version of Fedora? That way, this RR wouldn't need any extra engineers or qa folks, it would simply piggy-back on the work of the main Fedora folks. For example, instead of including a Fedora version number in the repository URL:
something like this (I'm using a made up word 'suede', which is similar to 'rawhide' in English ):
Now, that second link with suede could easily just point to the current version (and the existing mirrors) of Fedora, which is now 20. That way there would be no need for the end user (for instance, my mother) to bother with FedUp, or other distribution upgrades. The only thing needed would be to run 'yum update' every so often, perhaps even by cron. The contents of /etc/issue would state 'Fedora Suede", and the GRUB screen would state 'Fedora Suede'. (Without Linux kernel # in GRUB, I'd imagine. That way there is less to keep updated).
Do that even make sense? I must be missing something here, as it seems too simplistic.