Kamil Paral wrote:
> This serves as a nice example why we need to tweak how Rawhide works if we
> want people actually running on it.
And why do we need that? Rawhide is a place to do development, not a rolling
release distro.
> So, we either need:
> a) updates-testing for Rawhide - e.g. with auto-push even with 0 karma
> after 3 days, doesn't matter, it would still allow us to prevent many of
> these issues
> or
> b) decouple building and submitting to Rawhide - because the idea that
> everything and anything built is immediately part of the release seems
> very broken to me.
Those proposals will both slow down development to a crawl and prevent us
from doing our packaging work.
> At least if we want people to use it. If we want just a huge repo of
> frequently broken bleeding edge packages, yes, that's exactly what we
> have.
The latter is exactly what you get when you do actual development. The
former is a totally impractical illusion.
Kevin Kofler
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
