#118: Deliverables
---------------------+---------------------
Reporter: roshi | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Resolution:
Keywords: meeting |
---------------------+---------------------
Comment (by mattdm):
Replying to [comment:3 hguemar]:
> AMI images are blocking, we consider them as part of Base
I think it would be very useful to list all of the cloud providers for
which having a release-day image available is important.
All that said, in light of https://fedorahosted.org/cloud/ticket/117, it's
worth considering if cloud deliverables should be considered blocking at
all. The Atomic image is intended to be decoupled from the main release
cycle, with two week updates. Since that's to be the primary artifact,
maybe cloud can be completely separated from blocking the release?
If the Cloud Base image isn't ready on go/no-go day, could ''it'' be
delivered out-of-sync? And if so, is that ''okay''?
Based on feedback on the cloud list, I'm inclined to say that for now at
least the Cloud Base image, including availability on EC2, should be
release-blocking for F23 but we should reevaluate for F24.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/118#comment:4>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
