Posted Jul 26, 2012 2:50 UTC (Thu) by brunowolff (guest, #71160)
Parent article: Left by Rawhide
The reason why you see some fixes delayed is that rawhide inherits from the branched repo or if the isn't one current the updates repo of the last release. So if a package hasn't been built for rawhide is broken and has a fix go to updates-testing of branched or the last release, this fixed version will not be inherited into rawhide.
I would prefer that rawhide inherit from updates-testing, though ideally packagers would also be building updates in rawhide as well as the last release. (I believe that is official policy, though I have seen packagers recommend just the opposite to save work.)
I do think the suggestion some people have made, to stay with the branched releases is a good one. Though arguably alpha freeze might be a better time to switch rather than right at branch.
Rawhide seems best for people who are either working on new stuff and should be doing some amount of eating their own dog food and people who are willing to be canaries and save other people grief by catching problems early. I find I have unusual setups and figure problems triggered by that are likely to slip through if I don't catch them early, so I might as well be running prerelease stuff (either rawhide and/or branched) and try to save other people from the grief I'll get either way.