On Mon, Aug 30, 2010 at 11:11:06PM +0200, Miloslav Trmač wrote: > A typical developer wants the dependencies of the software they are > working on to be _very_ up to date - probably not the upstream > development version, but the upstream maintenance version with _all_ > current bug fixes. Waiting 6 months for a bug fix does not make sense - > at that point the developer would be tempted to build the new version > locally. [...] > Saying "use rawhide" is not helpful, because rawhide is very often > broken.
I've been running rawhide as my primary desktop OS at work for a couple of years now. During that time, it's only broken so as to cause me as much as a couple of hours work twice. That seems like a small price to pay for being on the extreme leading edge as you describe. And now with the "no frozen rawhide" feature, I expect it to be even more stable. > A "stable" release that breaks a specific component for a few > days is acceptable - if this is not a component one uses for > development, it doesn't matter; if this is such a component, one knows > about it well enough to be able to revert an update or to contribute a > fix. There you go! That's what we have in Rawhide. Maybe the problem here is that we need to market Rawhide better to Fedora developers. -- Matthew Miller <mat...@mattdm.org> Senior Systems Architect -- Instructional & Research Computing Services Harvard School of Engineering & Applied Sciences -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
