Fedora 17 TC / RATS scheduling

[Adam Williamson]

Hey, folks.

So, for Fedora 16 we experimented with replacing the 'RATS' test points
for Beta and Final with early drops of TC1, and I think that turned out
pretty well.

Given that, I think we should consider doing the same for Fedora 17.

Here are the current, relevant dates from the F17 schedule
(http://rbergero.fedorapeople.org/schedules/f-17/f-17-quality-tasks.html):

Pre-Alpha Rawhide Acceptance Test Plan #1    2012-01-19
Pre-Alpha Rawhide Acceptance Test Plan #2    2012-01-26
Pre-Alpha Rawhide Acceptance Test Plan #3    2012-02-02
Test Alpha 'Test Compose'                    2012-02-07
Fedora 17 Alpha Go/No-Go Meeting             2012-02-22

Pre-Beta Acceptance Test Plan                2012-03-07
Test Beta 'Test Compose'                     2012-03-13
Fedora 17 Beta Go/No-Go Meeting              2012-03-28

Test 'Final' Test Compose (TC)               2012-04-16
Fedora 17 Final Go/No-Go Meeting             2012-05-01

So, I'd say Beta is simple - we simply bump TC to 2012-03-06 or
2012-03-07 (depends if we want to keep the day of the week the same)
replacing the RATS run, as we did for F16. Final, oddly, has no RATS run
scheduled, but TC is still 'late' - there's only 15 days scheduled
between TC and Go/No-Go, as is the case for Alpha and Beta where there
are RATS runs. So we could also bump Final TC1 a week back, to
2012-04-09.

Alpha is a bit more complicated as there is not one RATS run but three
planned, and it may be a bit ambitious to try and build an entire set of
images as early as 01-19; we had trouble enough getting the F16 Alpha
built on the scheduled date. So we might again want to move the Alpha TC
up only one week, and preserve the first two RATS runs, which twu could
for now do following the same procedure as before.

So the modified schedule would be:

Pre-Alpha Rawhide Acceptance Test Plan #1    2012-01-19
Pre-Alpha Rawhide Acceptance Test Plan #2    2012-01-26
Test Alpha 'Test Compose'                    2012-01-31
Fedora 17 Alpha Go/No-Go Meeting             2012-02-22

Test Beta 'Test Compose'                     2012-03-06
Fedora 17 Beta Go/No-Go Meeting              2012-03-28

Test 'Final' Test Compose (TC)               2012-04-09
Fedora 17 Final Go/No-Go Meeting             2012-05-01

Assuming we kept the TC drops always scheduled for Tuesdays. There'd
then be 22 days between first TC drop and Go/No-Go, for each phase.

How does that sound? Anyone want to propose modifications /
alternatives? Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net