On Tue, Oct 4, 2016, at 09:46 AM, Paul W. Frields wrote: > > I think mattdm would agree we don't want to potentially, > *indefinitely* block a six-month release with a deliverable that can > be fixed and re-released in two weeks. 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. Now, we could discuss alternatives, such as having Atomic Host being able to carry its own overrides temporarily. _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
