EC2 / F17 Alpha: BROKEN
mspevack at fedoraproject.org
Tue Feb 28 01:40:35 UTC 2012
Full agreement. Do not slip the Alpha for EC2 images, but indicate that
they are a definite blocker for Beta.
On Mon, 27 Feb 2012, Robyn Bergeron wrote:
> On 02/27/2012 11:09 AM, Justin M. Forbes wrote:
>> On Mon, 2012-02-27 at 09:48 -0700, Robyn Bergeron wrote:
>>> Apparently appliance-tools is not working properly. This leads to either:
>>> * Cannot start doing updates for F17 until EC2 images are
>>> * No EC2 for F17 Alpha (because updates will be in, and EC2 F17 alpha
>>> would be different from Other Alphas)
>>> I'm recommending going with the latter option, simply because there is
>>> no criteria at all right now for making EC2 a blocker. Your (very
>>> immediate) thoughts are welcomed. I'm not particularly interested in
>>> slipping all of alpha after it met all of the shipping criteria and was
>>> announced to be shippable.
>>> Dennis, do you have a bug number for this (appliance-tools brokenness)
>>> I'm open to future recommendations, including doing a test
>>> compose/upload of EC2 images so that we know this before we have a
>>> go/no-go meeting, at the bare minimum. Please feel free to pipe in. :D
>> I would agree with option 2, no alpha. However I would like to see some
>> test images available as soon as we can get this fixed so that we are
>> not in this position for beta.
> ditto here.
>> cloud mailing list
>> cloud at lists.fedoraproject.org
> cloud mailing list
> cloud at lists.fedoraproject.org
More information about the cloud