On Tue, Oct 04, 2016 at 11:13:02AM -0400, Colin Walters wrote: > It's not that simple - this is a messy topic. What I think this > is about isn't delaying or blocking - it's *prioritization*. If > an issue comes up in Anaconda or systemd or whatever > that affects the "next AH", we need those teams to priortize > those fixes the same as they do for Workstation or Server. > > As far as I know the "blocker flag" is the main means > of cutting through all of the red tape. Yeah, I've been talking about this problem for a while — basically, since Release Blocker is the only big attention-forcing hammer we have, we tend to hit too many things with it. We need a different way. > Now, we could discuss alternatives, such as having > Atomic Host being able to carry its own overrides > temporarily. As you know, I'm in favor of this possibility should it come to that. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
