Rawhide currently ships a pre-2.4.0 mono snapshot. Considering 2.2 was just released a week ago and Fedora 11 Alpha is just around the corner (there is no way F11 will ship anything newer than 2.2) I consider this bug-worthy. Also note that a few modules (Banshee, Tomboy) don't compile even with mono 2.2 atm so fixing this before F11 Alpha should be a priority.
The purpose of rawhide is to include the bleeding edge material. It currently has 2.4svn in there and pre 1 won't be out for a while. The version I import goes through a huge series of tests before I upload, so I'm happy with it's stability (and by huge, there are almost 1200 tests I use, if it fails more than 5% I don't let it out). If Banshee and Tomboy don't build with 2.2 then I would suggest opening a bug here and also upstream as the fault could lie in either camp.
Well generally I agree to have bleeding edge stuff in Rawhide, but won't the next Fedora be "cut" from Rawhide at some point soon? Or will you base F11 packages off F10 when the Alpha is released? Thing is I want Banshee and Tomboy to work in F11 as soon as possible and I know they currently both have problems because I built them myself using jhbuild. But trying to fix stuff is hard with a moving "base technology" target. IMHO resolving this before things breaks for the first "real" users would be a good idea. I know bugzilla is probably a bad place for this kind of discussion... is there a mono-on-fedora mailing list or IRC channel?
http://fedoraproject.org/wiki/SIGs/Mono In particular: https://admin.fedoraproject.org/mailman/listinfo/fedora-mono I'm going to close this bug as backing out mono-2.4 to a mono-2.2 release at this point in the Fedora 11 release schedule is not feasible. Since mono seems to have adopted a fairly aggressive release schedule, this is likely something that needs to be discussed on the list for Fedora 12 as well so I hope to see you bring it up there.