Both Fedora and RPMFusion repos have "updates-testing" repos, which are disabled by default. Packages in the "*-updates-testing" repos are not necessarily unstable, but that is generally where newer versions of a package reside for awhile before they are "pushed" into the regular repos. The idea being, users who want to try out the newer package from the testing repo's can provide, well, testing of those packages to see if they are really ready for discimination into the regular repos. Of course, that only really works if users who do try packages from the testing repos file bug reports if and when they do run into issues with it.
You can temporarily enable any specfic updates-testing repo or all
of them at the yum command line. If I wanted to check if there was a newer xbmc package sitting in the rpmfusion-free-updates-testing.repo, I could do:
BASH:~/-> sudo yum --enablerepo=rpmfusion-free-updates-testing list xbmc
Loaded plugins: langpacks, presto
rpmfusion-free-updates-testing | 3.3 kB 00:00
rpmfusion-free-updates-testing/primary_db | 51 kB 00:00
rpmfusion-free-updates-testing/group_gz | 1.6 kB 00:00
xbmc.x86_64 10.1-7.fc16 rpmfusion-free-updates-testing
Ah, sure enough, there is a newer version sitting there, though it is just a minor "release" upgrade. I don't know how that version compares to the latest source code version, I haven't checked.
---------- Post added at 01:52 PM ---------- Previous post was at 01:38 PM ----------
OK, I checked on the xbmc website. 10.1 "Dharma" is current stable, 11.0 "Eden" is beta1.
If you're expecting a xbmc-11.0-beta1.fc16.arch.rpm to be any more "stable" than the source code it would be built from, you're expecting an awful lot. It's called "beta" for a reason. If you want to be a beta tester for xbmc, then file your bug reports.