On Mon, Nov 08, 2010 at 11:41:20 -0800,
"Brian C. Lane" <bcl(a)redhat.com> wrote:
That's not going to happen, everyone is focused on running systems after
Most likely.
the release so they aren't going to pay any attention to things
that
break anaconda.. More likely is to convince the anaconda team to take
selected updates after release and do a new build.
If as a project we thought it was important enough we could make this happen
as part of critpath QA. If a critpath update breaks, say the desktop spin
from being built with updates and working, we could reject the update.
I don't see that being the case (that respins are high priority) today, but
it is an option that could be made to work with some effort.