Updated Schedule for F12

John Poelstra poelstra at redhat.com
Fri Jul 10 16:44:55 UTC 2009

James Laska said the following on 07/10/2009 09:40 AM Pacific Time:
> On Fri, 2009-07-10 at 09:14 -0700, John Poelstra wrote:
>> Bill Nottingham said the following on 07/09/2009 05:51 PM Pacific Time:
>>  > John Poelstra (poelstra at redhat.com) said:
>>  >> Based on the feedback from the Release Engineering Meeting on Monday I
>>  >> have made the following tweaks to the schedule:
>>  >>
>>  >> o Added earlier blocker review days (f13)
>>  >> o Changed usage of "Release Candidate"  (f13)
>>  >
>>  > I don't think this is right. You've now moved the RC compose a week
>>  > later from where it was before.
>>  >
>>  > Bill
>> I haven't moved anything, I just changed the names.
>> Please tell me what the correct "compose RC date" is.  Thinking about it 
>> a little more I'm still not clear on our methodology.  We need a few 
>> specific dates that fit to get the time frame correct:
>> 1) Date blocker list must be clear or slip the release
>> 2) Date build RC (same day or day after #1)
>> 3) <input from QA on how many days to test the RC w/ allowance for 
>> finding problems in RC>
>> Note that #3 must be done by Thursday 2009-10-29 to start staging the 
>> content to the mirrors for GA on 2009-11-03.
>> We also need to decide now what our contingency plan and schedule 
>> consequences will be if the blocker list is not clear for #1.
>> When is the meeting between Releng and QA to review the schedule?  I'd 
>> like to be there.
> Jesse got in touch with me on IRC earlier this week.  I've been
> digesting some feedback since.  The changes Jesse and I agreed to during
> the F11 cycle are present in the schedule as it stands now.  These
> include defined compose dates.  In order to increase the likelihood that
> we'll hit those dates ... we've added blocker bug days.  
> These are welcome additions.
> I'd also welcome getting all interested parties in one "virtual room" so
> we can all sign-off and move forward.
> Thanks,
> James

When we meet in said virtual room we will still need input from QA on #3.


More information about the rel-eng mailing list