> -----Original Message----- > From: fedora-devel-list-bounces@xxxxxxxxxx > [mailto:fedora-devel-list-bounces@xxxxxxxxxx]On Behalf Of David Hollis > > If you have an important workstation/server, you really shouldn't be > running from Rawhide. Things get out of sync, break, get your cat > pregnant, etc. all the time. You can't expect real stability > until the > few weeks prior to release when everything freezes and the various > glitches are worked out. If there was any mandate to keep Rawhide > stable at all times, it would be the equivalent of production and they > would have to put out Beta/RC releases for Rawhide! Then > we'd never see > anything go anywhere. In a general sense I totally agree and follow this concept. But when it involves familiar components it tends to break the ability to provide the testing and feedback necessary to move the rawhide model forward. Perhaps the output of the build could be made more accessible (and maybe it is and I just don't know about it). We could then either what until the components we need are back in sync, or we could dive into cvs and provide feedback that is more productive than my whining! ;) edge
