On Fri, Apr 8, 2016 at 9:47 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Mon, 2016-04-04 at 10:20 -0500, Dennis Gilmore wrote:
Well I believe it's what's used to then install the qemu cloud and docker images so if it fails then all that use it in the creation process would fail which would make it release blocking due to dependency chains wouldn't it?
It is what is used, to make the cloud images. if it by itself is release blocking, I am not sure, but if it does not work we have no cloud images. So it does have to work
Once again, this is an implementation detail that can change. The blocking image list is not a technical list but a policy list. So this alone does not justify the image's inclusion in the blocking image list.
It seems to me like we should ask jkurik to amend the list, because no- one seems to actually consider the image to be blocking in itself.
I can do this. Do we need to get FESCo attention here, as the scope of deliverables is typically part of Change process.
Regards, Jan
-- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org