#118 Deliverables
Closed None Opened 6 years ago by roshi.

Per this fesco ticket: https://fedorahosted.org/fesco/ticket/1427 and the email from Jan [0], we need to discuss and outline our release deliverables.

[0] https://lists.fedoraproject.org/pipermail/cloud/2015-September/005727.html


for F23 I think we have: Base (Blocking), Vagrant (Non), Docker (Non) (and atomic is a spin now, so I don't think we worry about it for F23)

AMI images are blocking, we consider them as part of Base

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.

To clarify these are the Base images I meant (x86_64 only at this point, aiui):
* AMIs are uploaded to Amazon (there are a couple different ones fedimg produces)
* qcow2 images are generated and available for download
* raw.xz images are generated and available for download

I'm not 100% sure of the specifics for Docker and Vagrant - but they're non-blocking, so I'm not too worried about it. I'll add these to the wiki page.

+1

One thing to note is that right now our AMIs aren't uploading so we need to get that fixed soon so we can test for F23.

Login to comment on this ticket.

Metadata