Maybe here could fit "my" idea of "core" repo. https://www.mageia.org/pipermail/mageia-discuss/20101001/001761.html
In fact, what you need to define is what's the "core" system. Then you could see "core system" will be updated every X month. Example: you decide to update core system every 12 month. So, "core system 2011" will last 12 month. But during those 12 month you provide constantly updates / upgrades for all the rest of the software that isn't part to "core". And of course, for "core system 2011" updates / bug fix / security patches / etc. During those 12 month, you can work in "core system 2012". Here, the "rolling" part is the "non-core" software that is constantly updated. This way "core system" becomes more stable every day during the whole year. But without getting older because in every moment you have the latest GIMP or Thunderbird available. Cheers! Gustavo Giampaoli (aka tavillo1980)
