[Fedora-spins] MIA spins

[John Poelstra]

Bruno Wolff III said the following on 06/30/2010 02:21 PM Pacific Time:
> On Wed, Jun 16, 2010 at 16:09:00 -0700,
>    John Poelstra<poelstra at redhat.com>  wrote:
>> Kevin Fenzi said the following on 06/10/2010 05:33 PM Pacific Time:
>>> On Wed, 09 Jun 2010 09:46:26 -0700
>>> John Poelstra<poelstra at redhat.com>   wrote:
>>>
>>>> I would highly recommend considering and adding the following to
>>>> enable a smoother running Fedora 14 spins cycle compared to Fedora 13:
>>>>
>>>> 1) When testing will occur and for how long (through out)?
>>>
>>> Yes. Thoughout.
>>
>> We might get better coverage if we explicitly specify when it it needs
>> to happen vs. "all the time" :)
>
> I'd like to see extra covverage in the one week periods before the alpha,
> beta and final development freezes. You kind of need to keep an eye on
> things the whole time, as changes in other areas of Fedora can break your
> spin in various ways. But the above times are good times to be doing a closer
> look to see if problems have cropped up.
>
>> 1) How long does it take to create the final spins? (releng)
>
> I don't know the answer to this one.
>

Jesse--2 days to be safe?


>> 2) How much time do you need to test them and when should testing start
>> and end? (spins)
>
> This is going to depend on the spin. I am not sure if all of the spins
> owners have fast links. So it would be best to figure at least a day.
> We haven't had mandatory confirmation required in the past. Is this something
> you are thinking we should do for F14?

I thought we should have had it for Fedora 12 :)

It has always bothered me we would ship something without clearly 
confirming and tracking whether the final product was explicitly tested.

In a perfect world I'd say a week to test.  It may not take that long to 
do, but some people might not get to it right away.

John