On Sat, Apr 9, 2016 at 11:08 PM, Dennis Gilmore dennis@ausil.us wrote:
On Friday, April 8, 2016 12:47:37 PM CDT Adam Williamson 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.
his list os incomplete and wrong. we need something taht automatically tracks things as they change
I guess we talk about this page https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fed... May I ask you Dennis to share with me (not necessary on this mailing list) what is wrong and what is missing ? The list on this page is what we have agreed with FESCo for F23 and I am not aware of any Change in the scope of F24 which made any significant changes.
Regards, Jan
Dennis _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org